On Fri, Apr 29, 2011 at 10:22 PM, Ruben Van Boxem <vanboxem.ruben@gmail.com> wrote:

Instead of hijacking Ozkan's "thread", I will start a new one!

Some strange things in the autobuilds:
1. Stripping all exe's (including the ones in the libexec subdirectories) in the autobuild reduces total package size with a factor of 1/2... Seems like upload/download time and bandwith usage for everyone could be reduced significantly very easily. I have said this before.
2. There is a x86_64-w64-mingw32/lib32 directory full of 32-bit mingw-w64 crt libraries, but the gcc itself is configured with "--disable-multilib", making these completely useless. Either GCC should be buillt with multilib support (which would be the best), or the lib32 part shouldn't be built, shaves another five minutes off the build time. Is the multilib dll install fiasco still unsolved? (I must remember to keep following Clang and see if it works all right with mingw-w64!)
3. /include is empty? Why are the C++ headers in the x86_64-w64-mingw32 directory? Is this something new in GCC 4.7 or a bug in the build/install process?

i remarked that there are some differences between some packages:


do not have the same headers. I don't know the differences between them, but it seems that the first one has some improvements compared to the second one (declaration of functions that are only available on Vista and above for example).

Vincent Torri

Mind you: I appreciate all the work put into these things, I just feel the quality can be *easily* improved, making mingw-w64 *a lot* better.



WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today.  Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
Mingw-w64-public mailing list