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. >> A "toolchain" file is just a file that says "for platform X the C >> compiler is arm-gcc-4.2, the C++ compiler is arm-g++-4.2, the make >> tool is...", etc. CMake includes support for many platforms (compilers >> and operating systems) out of the box. You only need to create your >> own toolchain file when adding support for a new >> compiler/language/platform. In practice, this usually means you only >> need to create a toolchain file for cross-compiling for embedded >> platforms. >> > > That effectively says to the user "you MUST have the same setup as my > developer machine to compile this". Good lucky sorting out > arm-vendor-abi-gcc vs armv5tel-unkown-abi2-gcc vs dozens of > configurations out there. I'll reconsider my opinion on cross compiler > support once cmake understands build/host/target triplets. 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) >> As an additional bonus, there are the "superbuilds": you can easily >> combine provide a CMake-based meta-build system for CMake and >> non-CMake-based projects. This way, it would be possible to use the >> very same CMake build system to build mingw-w64 on Windows, Linux, >> BSD, etc. Even for cross-compiling. It'd be more or less what I am >> doing in winstng to build Wt: >> > > Sure, a top level cmake is fine, but please don't shoehorn it into any > of part mingw-w64 or it's subprojects, it already has an existing build > system. > > The last thing we need is to tell the user "in addition to a shell > interpreter, you need cmake/jam/waf/ant/msbuild too for this subproject". 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. -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) ------------------------------------------------------------------------------ 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
