Akos Balazs wrote: > Hi all, > > we would like to build a couple cross-platform OpenSG apps on Windows, and > for this we'd like to use the 1.8 dailybuild. So far it worked well by > just modifying the included .dsp file for the 01hello tutorial. However, > as using VS (in our case VS2005) directly for project (solution :) > management is kinda contraproductive for cross-platform development, we'd > like to use cmake for building our apps. The questions are therefore: > > a) is it enough to just add all the relevant properties from the project > settings into the cmakefile (e.g. compiler/linker switches, include dirs, > etc.) or is there some hidden magic? :) The problem here of course, is it > may change between different OpenSG versions and it may have to be redone > (manually) every time. How is it handled for the .dsp file generation? We > couldn't find any scripts in the source distribution that would generate > the .dsp files, did we miss something? Any recommendations for doing it > automatically instead of copying all values manually? > The most supported method to build OpenSG is scons. The VS proj files aren't always updated (only with major release points), so the best way would probably be to launch opensg's scons from cmake, which ought to be quite simple, no? (scons is included in OpenSG's svn-tree so you need not worry about a separate installation).
OTOH, there aren't that many options needed to compile OpenSG either (at least not on windows). If you run scons, it will print the compiler/linker options used for each file, so you could use that. Also, I don't know if scons supports cross-compiling, at all or as well as cmake. (We might only need some configuration in OpenSG's scons-scripts to support it.) > b) would there be interest if we come up with a cmakefile to include it in > the distribution to ease further crossplatform development? It would help > a lot since there's no such thing as ``osg-config'' for windows platforms > AFAWK. > I don't see why not, assuming it will get some continuing support from someone who knows cmake. Dirk & Co (the core-devs) will have to make the final judgement, but there are actually two advantages: 1. cross compile support (unless supported by scons already. Investigate that first.) 2. automagic IDE project files (Visual Studio, xx, yy, zz, etc.) (whatever the IDEs for Mac or *nix are called. I believe cmake supports a lot of them) Number 2 could actually be generated nightly or in the post-commit script, so that they would always be up-to-date for anyone not wanting to use scons. :) But still, scons works pretty well, so if you could use that to build, it would simplify things for everyone, I think. Scons should support a lot of platforms/compilers as well, so you might not need cmake to generate native buildfiles for OpenSG at all. Cheers, /Marcus ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
