Hello Geoff, If you don't mind having multiple DLLs instead of just one that contains those of OSG, then I can help! I work on a small engine that can be distributed as a DLL, and I experienced the Microsoft's specific problem: side-by-side assemblies (The thing that will cause your work to even not load on Vista and that can cause crashes on XP). To deploy my engine I have to: - Give my engine's DLL (that's ok!) on the PATH or in the execution directory. - Give all dependent DLLs (OSG, ODE, openAL, some boost libs, adn so on). - And also give Visual's redistribuable DLLs. Look at this small memo I wrote: http://pvle.svn.sourceforge.net/viewvc/pvle/trunk/Doc/Guides/Deploying%20a%20VisualC%2B%2B%20application.txt?view=markup This is about the The Visual's DLLs. It says which DLL's you need, and where to place them.
You also can have a look to the project sources, or ask me more specific things. Hope it helps. Sukender PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/ > Ok, I am having a problem creating a stand alone DLL that wraps some > functionality of OpenSceneGraph so that I can use it via COM in my > CodeGear C++ Builder app. > > I have created the dll, and have been successful in using it on my > development machine, but only in debug mode and only on that machine. > > My question is, is there a proper way to create a DLL in Visual Studio > 2005, using C++, and encapsulating it so that it can be deployed onto > other machines? Any help would be greatly appretiated as I have > exhausted my knowledge and the deadline is fast approaching. > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
