Hi Paul,
Yes, the increase in size would be a downside. But disk space and memory
are fairly cheap these days. I suspect only a small number of plugins
would increase (jpg, png, tiff, jp2).
I think we need to quantify it. Then we can evaluate if it's significant
or not.
If I have 16 OSG apps which all include (for example, I didn't try it)
5MB of dependencies statically linked each, that's 80MB instead of 5
(for the DLLs which could be shared). However, if I need to link to a
specific version of OSG+deps, I'd need my application to include the
specific DLLs in its directory anyways, so no savings there...
Perhaps linking to static dependencies could be an option in the CMake
generation process, with the deps binary packages including static libs,
and the default being static. Then if others want to compile and link to
DLLs, they can switch the option in OSG's CMake config.
Here I am suggesting ideas which I don't have time to implement... Shame
on me.
It would be interesting to know which users specifically are having
problems:
1. using prebuilt OSG + dependencies (either Mike's deps or perhaps from
the gnuwin32 project), not compiling their own app, are merely trying
out the OSG
2. using prebuilt OSG + dependencies, are compiling their own app
3. using prebuilt dependencies, compiling OSG from source, compiling
their own apps
4. compiling everything from source
Are you suggesting a poll? Doing this on the mailing list would be a bit
hard to keep track of... (Incidentally, I'm mostly in 3, though I'll
have to move to 4 for 64 bit soon)
Does the wiki have a poll functionality? Or perhaps we could use
Gordon's forum for that?
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
