Hi, On Tuesday 24 June 2008 03:25, Jean-Sébastien Guay wrote: > 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.
That config header just makes sure, that defines that change the api of some classes or that change the class layout in memory are consistent for one build. This was no problem for osg as such. But when you use osg, you need to make sure that all files that include some osg header have the same defines in your project like you had when compiling osg. Otherwise you might get unresolved symbols in the good case or mysterious crashes in the bad case. 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. You do not need to make sure that you apply the same defines that you used when compiling osg. You just get that for free. IMO this is an advantage. Greetings Mathias -- Dr. Mathias Fröhlich, science + computing ag, Software Solutions Hagellocher Weg 71-75, D-72070 Tuebingen, Germany Phone: +49 7071 9457-268, Fax: +49 7071 9457-511 -- Vorstand/Board of Management: Dr. Bernd Finkbeiner, Dr. Florian Geyer, Dr. Roland Niemeier, Dr. Arno Steitz, Dr. Ingrid Zech Vorsitzender des Aufsichtsrats/ Chairman of the Supervisory Board: Prof. Dr. Hanns Ruder Sitz/Registered Office: Tuebingen Registergericht/Registration Court: Stuttgart Registernummer/Commercial Register No.: HRB 382196 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
