Hello Brian,
2010/3/23 Prof Brian Ripley <[email protected]>:
> The R project (http://www.r-project.org) has been building under
> MinGW-w64 since mid-January. We have ca 2500 extension packages, ca
> 800 of which contain DLLs in C/C++/Fortran/more-than-one-of-those.
>
> In those couple of months the snapshots (at least the i686-mingw ones)
> have gone from dynamic loading of libgfortran/libstdc++ to static
> loading and back again. Was this intentional? We can cope with
> either (but prefer static) but with several hundred DLLs to check and
> an automated build process we could use some consistency -- we have
> already tens and soon to be hundreds of developers who will download a
> snapshot and work on their own extension package.
This switching in behavior is most likely reasoned by seeing the v1.0
builds and our automated 4.5 gcc builds as the same. Shared libstdc++
(and gfortran) are new features of 4.5 gcc, and v1.0 based builds are
using 4.4.x gcc version.
To prevent using shared version you can specify option '-static'.
> We do realize MinGW-w64 is a 'work in progress' project based on
> unreleased versions of GCC. But as we are about to commit to
> production use on a quite large scale, it would be helpful at least to
> know the plans so we can write future-proof documentation for the
> would-be users (where 'future' means 6 months until the next
> documentation release).
Our intention is to support for toolchain the latest three versions.
That means, current head version (bleeding edge), and the latest
releases of the two prior gcc version. We use in general binutils head
for all of our builds.
We have at the moment two branches. The v1.0 branch, which is our
release branch, and trunk/.
At the moment we plan to switch to MS-ABI in name decoration, which is
a long outstanding - but very necessary - step to provide some
inter-operability to VC generated static libraries.
Additional we plan to replace complex math part of crt by our own
version (we are using at the moment the implementation mingw.org
originated by Danny Smith), which has some problems in respect to
ISO-C99 expected results reasoned signness.
Regards,
Kai Tietz
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
