This is most definitely not a transparent change. It is not backwards compatible with application projects designed to build against an OSG source/build tree. -Paul
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of James Killian > Sent: Tuesday, June 24, 2008 10:18 PM > To: OpenSceneGraph Users > Subject: Re: [osg-users] [osg-submissions] API configurations > in aseparateConfig include file > > What was suppose to happen is that all of the changes were to > be transparent in such a way where he need not write > additional info. The problem of course is that when the code > was checked in it was not tested for the windows platform, > and now that I finally understand how it is suppose to work > there are two known issues: > > 1. On my setup using 2.4.8 and VS 7.1 platform the cmake > fails to identify that I can use interlocked and threaded > environment, and so the config files written are for single > threaded, and some of my bounding variables were defined as float. > > 2. I suspect that cmake scripts included the *build* include > for only OpenThreads and OSG (and these could build fine)... > problem is that all projects dependent on either of these > will also need to add the build path to search, and this > triggered the "why can't my application find the Config > header?" issues. > > It should be easy to fix #2 if in fact that is the intended > direction (and to the best of my knowledge) it was. > > If these things are working properly, it should be a > transparent workflow. > I will certainly test this and provide feedback once the > windows.h issues are resolved. > > > James Killian > ----- Original Message ----- > From: "Paul Martz" <[EMAIL PROTECTED]> > To: "'OpenSceneGraph Submissions'" > <[EMAIL PROTECTED]> > Cc: "'OpenSceneGraph Users'" <[email protected]> > Sent: Tuesday, June 24, 2008 4:56 PM > Subject: Re: [osg-users] [osg-submissions] API configurations > in a separateConfig include file > > > >I was surprised to see a change with such widespread ramifications > >discussed > > only on osg-submissions, so I'm cross-posting. > > > > I think I've now waded through enough of the posts in this thread to > > understand why this was done, and how to cope with the fact that OSG > > header > > files are now in the build directory. > > > > Mathias, could you take the time to enter a FAQ on the wiki > regarding > > this? > > I foresee many posts when people upgrade to the latest OSG > of the form: > > "why > > can't my application find the Config header?". Users will > need to know the > > following: > > > > * OSG now generates headers in the build tree. If your app > links with OSG > > from a source/build tree, your app will now need to look > for headers in > > multiple locations. > > > > * You can get around this by installing OSG. You can > customize the install > > location with an OSG cmake variable. > > > > * Any other info you think is relevant. > > > > A FAQ on the wiki would be better than having people search the > > osg-submissions archives. > > > > Thanks, > > -Paul > > > > _______________________________________________ > > osg-users mailing list > > [email protected] > > > http://lists.openscenegraph.org/listinfo.cgi/osg-users-opensce negraph.org > > > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-opensce negraph.org _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
