On 11/10/12, Ruben Van Boxem <[email protected]> wrote: > 2012/11/10 Ozkan Sezer <[email protected]> > >> On 11/10/12, Luis Lavena <[email protected]> wrote: >> > On Sat, Nov 10, 2012 at 10:54 AM, Ruben Van Boxem >> > <[email protected]> wrote: >> >> Hi, >> >> >> >> I have the crazy idea to help with ironCrate. >> >> >> >> I have written a small CMakeLists.txt file to get automated >> >> compilation >> >> working (I know you guys favor autotools, I don't). I am running into >> >> some >> >> issues building the source from the get-go. >> >> >> > >> > I think CMake is already the proposed solution: >> > >> > >> http://sourceforge.net/apps/trac/mingw-w64/wiki/devel%20crt%20licensing,%20Coding-style,%20and%20more >> > >> > As CMake provides the generation of MinGW/MSYS makefiles and Visual >> > Studio project files, which is the goal of ironCrate (be compatible >> > with both compilers) >> > >> >> It still amazed why we are not using plain old makefiles. >> oh well.. >> >> > Probably because you'd have to write three sets of makefiles: nmake, msys > make, and mingw32-make, which really is kinda silly...
I don't think that composing different makefiles for mingw- and msys- versions of make would be necessary but yes one would be necessary for nmake. Two, or even three different makefiles I consider as fair price against dealing with complexities and/or extra dependencies of cmake or autotools. > > Ruben -- O.S. ------------------------------------------------------------------------------ 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
