Hello Mathias,
I actually followed the e-mails related to this and *still* don't
understand why a Config header is required! ;)
Well that is somehow orthogonal to the windows.h include.
Yes of course, but since both (the Atomic header and the Config header)
came in because of the same change (atomic ref counting) they're still
related.
This Config header includes those defines that change the api and by defining
them in a file that is included at built and installed with the binaries
ensure that you get the same defines when you just include osg headers from
that build/install directory where you take the libs.
OK, that clears that up. Ignore my question about CMake adding
"/D<something>" to the build command line. You're right, in that case we
would need to make sure every client app had the same define, which
would be a chore. A Config header is better, I agree.
Thanks for explaining.
J-S
--
______________________________________________________
Jean-Sebastien Guay [EMAIL PROTECTED]
http://www.cm-labs.com/
http://whitestar02.webhop.org/
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
