Re: [Mingw-w64-public] ironCrate

2012-12-01 Thread Jon
> > However, if you choose to use autotools, to better support the > > build-for-windows-on-windows scenario I ask that you also maintain a > > mingw32-make compatible Makefile. IIRC, this was Ozkan's suggestion near > > the very beginning of the discussion. > > Do you mean by this "not msys" ?

Re: [Mingw-w64-public] ironCrate

2012-12-01 Thread NightStrike
On Sat, Dec 1, 2012 at 5:47 PM, Jon wrote: > However, if you choose to use autotools, to better support the > build-for-windows-on-windows scenario I ask that you also maintain a > mingw32-make compatible Makefile. IIRC, this was Ozkan's suggestion near the > very beginning of the discussion.

Re: [Mingw-w64-public] ironCrate

2012-12-01 Thread Jon
> As for your concerns about CMake being available or not: it's > available from all Linux and BSD variants I know because more and more > projects are moving to CMake because more and more projects are > concerned about cross-platform, including MSVC. It's not something >

Re: [Mingw-w64-public] ironCrate

2012-12-01 Thread JonY
On 12/2/2012 06:27, Jon wrote: As for your concerns about CMake being available or not: it's available from all Linux and BSD variants I know because more and more projects are moving to CMake because more and more projects are concerned about cross-platform, including MSVC. It'

Re: [Mingw-w64-public] ironCrate

2012-12-01 Thread Jon
> >> As for your concerns about CMake being available or not: it's > >> available from all Linux and BSD variants I know because more and more > >> projects are moving to CMake because more and more projects are > >> concerned about cross-platform, including MSVC. It's not something > >> esoteric.

Re: [Mingw-w64-public] ironCrate

2012-12-01 Thread Earnie Boyd
On Sat, Dec 1, 2012 at 1:47 AM, Vincent Torri wrote: > On Sat, Dec 1, 2012 at 6:49 AM, NightStrike wrote: >> >> >> Really, I haven't seen any build system that I think is wonderful. >> autotools works for us, but it's not great. I've used a lot... even >> scons. > > just for curiosity : what do yo

Re: [Mingw-w64-public] Zero-overhead exceptions

2012-12-01 Thread Kai Tietz
2012/12/1 Ulf Magnusson : > On Sat, Dec 1, 2012 at 4:33 PM, NightStrike wrote: >> On Sat, Dec 1, 2012 at 3:37 AM, Ulf Magnusson wrote: >>> Hi, >>> >>> If I've understood things correctly, MinGW-w64 uses the SJLJ >>> (longjmp-based) exceptions implementation for both win32 and win64, >>> because D

Re: [Mingw-w64-public] Zero-overhead exceptions

2012-12-01 Thread Ulf Magnusson
On Sat, Dec 1, 2012 at 4:33 PM, NightStrike wrote: > On Sat, Dec 1, 2012 at 3:37 AM, Ulf Magnusson wrote: >> Hi, >> >> If I've understood things correctly, MinGW-w64 uses the SJLJ >> (longjmp-based) exceptions implementation for both win32 and win64, >> because DW2 (speedy, table-based) can't pas

Re: [Mingw-w64-public] Zero-overhead exceptions

2012-12-01 Thread NightStrike
On Sat, Dec 1, 2012 at 3:37 AM, Ulf Magnusson wrote: > Hi, > > If I've understood things correctly, MinGW-w64 uses the SJLJ > (longjmp-based) exceptions implementation for both win32 and win64, > because DW2 (speedy, table-based) can't pass exceptions through > foreign stack frames (e.g., throwing

[Mingw-w64-public] Zero-overhead exceptions

2012-12-01 Thread Ulf Magnusson
Hi, If I've understood things correctly, MinGW-w64 uses the SJLJ (longjmp-based) exceptions implementation for both win32 and win64, because DW2 (speedy, table-based) can't pass exceptions through foreign stack frames (e.g., throwing an exception from within a callback and catching it at the point

Re: [Mingw-w64-public] ironCrate

2012-12-01 Thread deneme.true
>This is intriguing. Can you give some detail on how it works for >cross compiling? xml file definition regarding libraries and executables exists in *.bkl files(similar to ant), bakefile will generate the makefiles from *.bkl files for specific make tools. It works perfectly in wxWidgets. Rega