Jean-Sébastien Guay wrote:
This seems to come up quite often for the Windows users. Would
linking against a static version of dependencies like png, jpeg,
zlib, etc be a helpful solution?
Not sure how the executable size would increase in that case... But
yeah, they're pretty much required dependencies if you want to do
anything useful, so I'd agree that it could be helpful.
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).
Though I think when developing on Windows you need to be able to
diagnose and fix DLL search path and dependency problems, because
they'll bite you sooner or later.
Absolutely! (I'm glad I only work with Linux these days ;-))
I'm not trying to imply that OSG should be a teaching aid in Windows
programming and troubleshooting, but we should consider how much time
we spend on making things easier for newbies which they'll have to
learn anyways.
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
I doubt that category 4 will have these DLL problems. But I'm curious
about the spread over the other 3 categories..
Paul
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
