On 11/11/2012 16:42, Pau Garcia i Quiles wrote: > On Sun, Nov 11, 2012 at 9:26 AM, JonY <[email protected]> wrote: > >> Sounds like they are reinventing autotools. > > As Ruben says, it's not the case. > > The main problem with autotools is they do not support Windows. Even > with CoApp, autotools support is far from *acceptable* on Windows. >
Here I am using autotools to drive MSVC tools. > > Sorry but you got it wrong. The idea is exactly the opposite. Have you > ever tried CMake for cross-compiling? Here's a good starting point: > > http://www.cmake.org/Wiki/CMake_Cross_Compiling > > I wrote a tutorial for newbies a few years ago, it's a bit outdated > but still relevant: > > http://www.elpauer.org/stuff/learning_cmake.pdf > > (it's what people at my company use to teach new developers) > > You call writing and coding for every possible combination forwards? > > To make it clear, user = the guy trying to compile CMake, not the end-user. > > What's the problem with developers having CMake? In fact, if the whole > build system is replaced with a CMake build system, developers no > longer need to fiddle with MSYS and/or any other sh-under-Windows > trouble. > I think you confused the two. The developers building the toolchain from source ARE the users of mingw-w64, some of them may happen to release toolchains to downstream consumers. Like I said in another email, cmake was too rigid, so autotools is here to stay, for better or worst.
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
