From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Assorted MinGW-w64 toolchain libraries and tools
Date: Thu, 11 Feb 2016 00:58:00 -0000 [thread overview]
Message-ID: <56BBDCBE.2050208@cygwin.com> (raw)
In-Reply-To: <loom.20160210T212108-245@post.gmane.org>
On 2016-02-10 14:27, Tony Kelman wrote:
> Yaakov Selkowitz writes:
>> These packages provide libraries and tools for cross-compiling a wide
>> variety of projects for native Windows with the MinGW-w64 toolchains.
>
> Ooh. I will totally be using these, this is great to see. So does
> this mean it's open season for ITP's on mingw-w64 library and
> application packages?
Not MinGW applications, unless they are Cygwin-hosted tools used for
cross-compiling (which I think we have pretty well covered).
> (Also a newer clang+llvm would be useful, they've made a lot of
> improvements since 3.5.)
LLVM/Clang version bumps are time-consuming to get right. I actually
looked at 3.6, but MCJIT did not work OOTB with PE/COFF targets. I'll
have to see what the story is with 3.7.
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-02-11 0:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 17:51 Yaakov Selkowitz
2016-02-10 20:35 ` Tony Kelman
2016-02-11 0:58 ` Yaakov Selkowitz [this message]
2016-02-11 3:24 ` Tony Kelman
2016-02-11 3:25 ` Tony Kelman
2016-02-14 20:02 ` Tony Kelman
2016-02-14 21:43 ` Yaakov Selkowitz
2016-02-15 5:54 ` Ismail Donmez
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56BBDCBE.2050208@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.com \
/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).