On 02/13/2011 10:35 PM, Michael Stratmann wrote: > Hello Klaas, > > I just made some progress: > Calling cmake-gui from dos box works fine, even for visual studio (as you > insisted). The problem appears to be the configure.lua script.
That script might not be foolproof yet. > By default > cachefilestr=cachefilestr.."CMAKE_GENERATOR:INTERNAL=NMake Makefiles\n" > is active. > To get the project files, I switched to > cachefilestr=cachefilestr.."CMAKE_GENERATOR:INTERNAL=Visual Studio.*\n" But using -g on the command line, cmake-gui will be used, and you can choose using cmake-gui, which toolset you want to use, is it not? But for sure the lua comment is misleading. No matter what, the script is only for nmake usage, function make() shows that. If we could call visual studio automatically, and compile what is needed, and next continue with the next cmake step etc. That would be better. But i think that is not feasible. In the end "make" is still the tool to do everything :-( To prevent to have a make and nmake file etc. on the top level, i started the configure.lua to be used on all platforms. If we could just have one make and scripting language on all OS's that would make thing much simpler. What i need is: generate project/make files, next make, next generate more project files and make etc. Cmake is not very good at this as an overall language. > However, there is no such compiler. When I made a line > cachefilestr=cachefilestr.."CMAKE_GENERATOR:INTERNAL=Visual Studio > 9 2008\n" > the problem (forced to delete CMakeCache) was gone. :-) Looks like > CMAKE_GENERATOR must be set with exactly the VS version which gets detected. That is right. I use the script because when testing, i need to compile again and again. But for fool proof usage more checking is needed. Also i don't want to rewrite cmake using lua. Was there not a warning from Cmake? If i needed to redo the make system i would go for the lua based premake, like Cmake, but a decent scripting language. But premake is not at the level of Cmake yet. Klaas ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Wxart2d-users_dev mailing list Wxart2d-users_dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxart2d-users_dev
