Hi all Windows users (and others too, I'm not doing discrimination ;) ), Under Linux (& co), packages can have dependencies. Under Windows, we're far to have such an easy system. Question is: how could we redistribute efficiently the OSG binaries (I mean when not linking statically) alongside our apps?
Here are my suggestions, please share your thoughts. 1. Manually copy the DLLs in the app's dir. That becomes a pain if you select each DLL by hand, and you may have multiple copies for each app. 2. Say to the user (s)he must download the OSG binaires. Not very user firendly, IMO. 3. Create a nice installer that contains the OSG packages. Thus the installer become obese since we don't need all the DLLs... 4. Create a nice installer that contains partial packages. Not very "clean" to begin splitting packages I think. 5. Create a nice installer that will download packages on the web. Nice, but what about installing on a machine that has no connection? Should we provide both "online" and "offline" installers? And about installers... Should we copy the DLLs to the system dir? What about Vista and its strange policies about having access to system dirs (I simply stayed under XP :D )? Thank you! PS: It seems I'm going to have an installer (or such) ten times bigger than my app... (sigh) Sukender PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/ _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
