Hi, On Wed, 2005-03-09 at 10:48 +0100, Marcus Lindblom wrote: > Gerrit Voss wrote: > > >>These are my defines: > >> > >>_DEBUG;WIN32;_WINDOWS;WINVER=0x0400;_WIN32_WINDOWS=0x0410;_WIN32_WINNT=0x0400;_OSG_HAVE_CONFIGURED_H_;OSG_WITH_GIF;OSG_WITH_TIF;OSG_WITH_JPG, > >> > >>OSG_BUILD_DLL, OSG_NEW_DLLS > > > > what seems to be missing is the OSG_BUILDXXXLIB define telling the > > system which library you are currently building and thus being able > > to decide on the import/export aspect of building windows dlls. > > Depending on the current lib the defines are : > > > > OSG_COMPILEBASELIB > > OSG_COMPILESYSTEMLIB > > OSG_COMPILEWINDOWGLUTLIB > > OSG_COMPILEWINDOWWIN32LIB > > > > only one define must be active at a time, the one for the lib you are > > currently building. > > Sorry for not being clear. I'm building my own dll which uses the > OSG-dlls, not the OSG-dlls themselves.
hmm I haven't seen these before (or missed them) while building OpenSG, as the example you gave is from the baselib the warning should occur while building the remaining libs. I remember seeing something about reexporting stl containers from dlls but I have to dig a little bit to find it again. Let me see if they occur inside OpenSG to, short question, which compiler are you using ?. As the warning you send relates to a private member I would tend to say it should be ok to ignore them for now as the member won't be touch outside the class. regards, gerrit ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
