On Mon, 12 Nov 2012 07:14:42 +0800 JonY <[email protected]> wrote:
> On 11/12/2012 03:36, Pau Garcia i Quiles wrote: > > On Sun, Nov 11, 2012 at 7:05 PM, Jon wrote: > > > >> So here's the question. > >> > >> Can the method I use when cross-compiling, namely, use cmake's > >> `ExternalProject` module (causes cmake to run itself and generate > >> artifacts in a different dir) to pre-build an environment on the build > >> system that's used by the cross build > >> > >> https://github.com/mruby/mruby/blob/master/mrblib/CMakeLists.txt#L7-14 > >> > >> address JonY's need to be able to build multiple flavors of cmake object > >> libraries, carry them around, and inject them into their respective static > >> libraries? > >> > >> I don't know as I haven't investigated. > > > > I have never been in that case. So far CMake script has been enough > > for me for this kind of cases (e. g. Wt filetostring). But take a look > > at this thread or ask in the CMake mailing list ( > > http://www.cmake.org/mailman/listinfo/cmake ) > > > > http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/29310 > > > > From what I gather, I'll need to: > > 1. Write an external tool/driver to do this. > 2. Split into subprojects. > 3. Have cmake call itself recursively. > > Sounds complex, now that I've thought through this a bit. > > My chief concern is that we may end up with accepting a cmake-only > subproject, requiring users to have shell interpreters for the other > code AND cmake to complete the build. This kind of adds dependency with > questionable benefits for the amount of work done just to satisfy > Windows users. > > My further concern with going all-cmake only is that some code cannot be > built with MSVC, so it very much limits the perceived value to Windows > users, in addition to rustling Linux users who don't have cmake > installed previously. At this point in the discussion, I'm hoping Ruben is still scratching his ironCrate itch by building a cmake prototype so those interested can play cd build cmake -G Ninja .. && ninja all test cmake -G "MSYS Makefiles" .. && make all test cmake -G "NMake Makefiles" .. && nmake all test cmake .. && make all test cmake -G "Visual Studio 10" .. && msbuild ALL_BUILD.vcxproj /t:Build ... while he's keeping 10% of an eyeball on this thread for answers to his original non-cmake question. And if it works nicely...hmm, better seatbelt in for the next round of threads on managing complexity ;) Jon --- Fail fast. Fail often. Fail publicly. Learn. Adapt. Repeat. http://thecodeshop.github.com | http://jonforums.github.com/ twitter: @jonforums ------------------------------------------------------------------------------ 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
