HI Brent, On Fri, Jun 5, 2009 at 3:46 PM, Brent Gulanowski<[email protected]> wrote: > I see. However, it seems counter-intuitive to me to use an automated tool to > generate project files meant primarily to be read and processed by Xcode, for > human users. Why not just generate build file formats themselves designed for > automated processing? Xcode is a user tool.
Um.... you are a little short of grasping just how powerful CMake is... CMake generates project files for many different tools, it allows you to use one set of build scripts for all platforms, so you can move from VS 7 to VS 8 to Cygin to Linux with Makefiles, to Linux with KDevelop, to OSX with Makefile, OSX with XCode etc. CMake also can query all your dependencies and switch the build on/off of various components. This is critical for projects like the OSG that has hundreds of separate components libs/examples. Do stuff just in XCode and all you do is a that fixed subset that you've configured by hand, and if the XCode project format change you have to port to this new version of XCode and then you loose the ability to port back to older version of XCode if you have too... >If you're going to use Xcode to do OSG development, then it only makes sense >to manage the project by hand. If, alternatively, you aren't going to use >Xcode, it doesn't make much sense to me to generate Xcode project files by any >means, by hand or using an automated system. We you can make any decision for your own code as you can limit who builds against it and you can limit just how complicated your build is. The OSG pushes build systems because of it's extreme portability and number of components and wide range dependencies, for the OSG project CMake is a god send. >> One thing I am aware of is that XCode isn't forwards/backwards >> compatible w.r.t it's own project file format, so if you aren't using >> the same version that Stephan is using then there is good chance that >> you'll see problems. Perhaps Stephan will spot this thread and fill >> in more details. > > While this is true, it does not lead to problems of the sort I'm > experiencing. All Xcode 3.x version are able to read and write Xcode 2 and > later formats. The project file in the distribution is set to Xcode 3, and > I'm using the iPhone Dev Kit v3, which uses Xcode 3.1.3. It does still sound like your experiencing problems with hand built XCode project being too inflexible. Try CMake, it's XCode support isn't perfect but it may well be better than the hand built ones. Also consider building the OSG using Makefiles. It's far easier to automate builds using Makefiles. You'll be primarily and end user of the OSG rather than a developer of the OSG, so all you mostly should need form the OSG is the binaries/libraries and headers. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
