From: Eli Zaretskii <eliz@gnu.org>
To: "Germán Diago" <germandiago@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: Interest in windows native port, interpreters for other languages and C++ binding API.
Date: Wed, 01 Feb 2017 14:56:06 +0200 [thread overview]
Message-ID: <83a8a6vzmh.fsf@gnu.org> (raw)
In-Reply-To: <CAALp5N4fJ6=GbaTmpoi_x5f+e+521p_w0amLRx+S4awaJuBqUw@mail.gmail.com> (message from Germán Diago on Wed, 1 Feb 2017 12:18:28 +0700)
> From: Germán Diago <germandiago@gmail.com>
> Date: Wed, 1 Feb 2017 12:18:28 +0700
> Cc: guile-devel@gnu.org
>
> Well, provided that you are tied to msys and you can never ever compile guile with a microsoft compiler, that
> is ok. You are talking only about your use case. The reality is quite different: if you want windows adoption, you
> need to use the native toolchain to compile.
MSYS is used only to run Bash, m4, perl, etc. -- programs that are
invoked during the configure stage and by shell script fragments in
the Makefile. The compiler is MinGW, not MSYS. MinGW produces native
executables that are completely compatible with MSVC compiled
programs. So I don't see a problem here, or any need to use non-free compilers.
> I can say with confidence that keeping autotools and taking windows seriously at the
> same time is just impossible.
That's definitely not my experience.
> So my view here is that to have a decent windows port we would need native
> windows threads and compile with microsoft compiler
MinGW supports native Windows threads, and in fact the ported pthreads
are just a very thin wrapper around native threads.
next prev parent reply other threads:[~2017-02-01 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 4:28 Interest in windows native port, interpreters for other languages and C++ binding API Germán Diago
2017-01-31 15:29 ` Eli Zaretskii
2017-02-01 5:18 ` Germán Diago
2017-02-01 12:56 ` Eli Zaretskii [this message]
2017-02-01 15:09 ` Germán Diago
2017-02-01 13:39 ` David Kastrup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a8a6vzmh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=germandiago@gmail.com \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).