From: Tony Kelman <tony@kelman.net>
To: JonY <10walls@gmail.com>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-1 (x86/x86_64) (Testing)
Date: Sun, 07 Aug 2016 15:31:00 -0000 [thread overview]
Message-ID: <DM2PR0201MB0799F1E51CA574784C3D5CECA71A0@DM2PR0201MB0799.namprd02.prod.outlook.com> (raw)
In-Reply-To: <57A67CEE.9020809@gmail.com>
> Does Julia depend on C++11 features? I'm not familiar with it. How big
> is it compared to say, QT?
Yes, it does depend on C++11, but mostly by way of linking to LLVM.
Julia by itself is not huge, but it depends on a bunch of external
library dependencies that are. The most time-consuming of those are
LLVM and OpenBLAS, which I believe we have mingw-w64 cross-compiled
versions of available in Cygwin, so it might be possible to link
against those to save some time, I haven't tried. I suspect those
packaged libraries haven't been rebuilt against this test gcc build
yet though. And in the default `git clone ...; make` build of Julia
we apply some patches to fix various bugs depending on what versions
of the dependency libraries we're using, so a USE_SYSTEM_LLVM build
might have test failures that aren't due to the GCC version being used.
On my 4 x (2 HT) core i7-6700 HQ laptop with an SSD, the from-scratch
source build of Julia without linking to any pre-existing dependency
libraries took about an hour. Not sure how that compares to QT.
-Tony
--
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-08-07 5:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 2:02 JonY
2016-08-06 13:19 ` Tony Kelman
2016-08-07 5:34 ` JonY
2016-08-07 15:31 ` Tony Kelman [this message]
2016-08-08 4:47 ` Yaakov Selkowitz
2016-08-08 13:52 ` JonY
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=DM2PR0201MB0799F1E51CA574784C3D5CECA71A0@DM2PR0201MB0799.namprd02.prod.outlook.com \
--to=tony@kelman.net \
--cc=10walls@gmail.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).