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's not something >>>> esoteric. >>> >>> As far as I know, there are still a lot of project against the ideas >>> of using CMake to replace the autotools. >> >> The main reason why we do not use cmake is that it makes things much >> more complicated for the end-user, while adding additional maintenance >> requirements that we should get for free from the build system. >> >> Here's what I mean. >> >> In the autotools world, there is a very defined and extremely enforced >> concept that above all, our goal is to make it *TRIVIAL* for the end >> user to compile your software. Now let's clarify this. The end user >> is the guy who knows nothing about development, nor of your project, >> nor of autotools, nor of anything else. But he needs your project for >> some reason. We want that guy to be able to do this: >> >> cd /tmp; /path/configure && make > > What do you expect to be the breakdown of how you (as committers) will > build/debug/test ironCrate? For example, are these the right categories and > reasonable estimates? > > 75% - Build on Linux for Linux (Wine) [1] > 22% - Cross-build on Linux for Windows > 2.8% - Build on Windows for Windows (all MinGW flavors) > 0.2% - Build on Windows for Windows (VC++) > > Now turn it around. What do you expect to be the build breakdown for devs > trying to use ironCrate? >
I would expect the Wine case to be merged with cross for Windows, I don't think ironcrate would make much sense as part of Wine. What would likely happen however is to cross build for Windows and test it under Wine. Personally, I never do MinGW->MinGW straight compiles, there is always a cross somewhere, normally from Cygwin or Linux in a VM. For ironcrate downstream users, I expect: 30% - Cross from Linux or other systems 65% or more - Straight mingw* builds 5% or less - VC++ builds As it stands right now, I don't think there is much utility in users using it in MSVC other than as a curiosity since ironcrate has not reach a point where it can cover msvcr*. Figures will change as features are added. I put a high estimate for straight mingw-mingw builds mainly because there is a weird fixation among some Windows devs to make everything static. Likewise, figures will change as ironcrate matures.
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: DESIGN Expert tips on starting your parallel project right. http://goparallel.sourceforge.net/
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
