Hi Ken!
On Mon, Feb 11, 2013 at 1:12 PM, Ken Goldman wrote:
> I downloaded mingw from mingw.org. The documentation says:
>
> "The project's name changed from mingw32 to MinGW is to prevent the
> implication that MinGW will only works on 32 bit systems (as 64 and
> higher bit machines become more
2013/2/11 Ken Goldman:
> What exactly does that mean? Has it evolved yet? Can I compile for 64
> bits? Do I need some other package? A flag? Or is mingw not ready yet?
Read this:
http://sourceforge.net/apps/trac/mingw-w64/wiki/GeneralUsageInstructions
--
Regards,
niXman
__
I downloaded mingw from mingw.org. The documentation says:
"The project's name changed from mingw32 to MinGW is to prevent the
implication that MinGW will only works on 32 bit systems (as 64 and
higher bit machines become more common, MinGW will evolve to work with
them)."
What exactly does t
Fwd to the list:
Original Message
Subject:Re: [Mingw-cross-env-list] Boost.Python extension (cmake)
Date: Mon, 11 Feb 2013 15:32:10 +0100
From: h...@robin-jadoul.ciki.me
To: Václav Šmilauer
I actually managed to use 7zip to extract python from the downloadable
I think I took it as an opportunity to learn a tiny bit of automake
having avoided it so far!
Ho hum... an update is in progress.
On Mon, Feb 11, 2013 at 10:58 AM, Jacek Caban wrote:
> Hi Ray,
>
> Sorry for my response time too... Why don't you put the warning in
> configure.ac instead of Makefi
Hello,
Third party compression utilities(upx) can be used to decrease the
dlls and executables sizes. But extraction and usage of dlls and
executables in memory will be longer than before.
Regards
--
Free Next-Gen Firewa
Hi Ray,
Sorry for my response time too... Why don't you put the warning in
configure.ac instead of Makefile? Also the warning could say something
like "--with-widl used in out of the tree compilation. Existing
generated files won't be modified."
Cheers,
Jacek
On 02/03/13 19:44, Ray Donnelly wrot
