Hi all, A quick heads up on OSG 2.0 binaries built w/ VS8. I have built a brand-new (VMware) machine with WinXP SP2 and VS8.0 SP1 specifically for this task.
For safety and completeness, I'm creating a new package of 3rdParty dependencies, built using VS8 from the latest sources. This is to head off known security issues w/ some of the versions in the existing binaries. I am also leaning toward DLLs when the upstream package provides it, but I do not intend to fork/redesign other project's build systems. The only thing I try to modify is ensure the binaries are built using "multithreaded dll" (ie /MD and /MDd) code generation. An implication is that I may need to tweak the Cmake files for updated 3rdParty filenames. As the verbatim source has historically been included in the installer, I don't see that as a huge consistency issue, and of course I'll roll any changes back to Robert. As policy I try to refrain from changing the names of generated binaries, but I recall threads on this list re inconvenience w/ some names in the Cmake environ. If there are specific issues w/ the current 3rdParty package (in either then binaries or the include filesystem) that require more extensive modification, pls let me know so they can get resolved in this pass. Also I haven't heard feedback regarding the OSG 2.0 VS7.1 installer; assuming no news is good news :-). If there are any issues w/ the current installer, do let me know. Cheers -- mew Mike Weiblen -- Zebra Imaging -- Austin Texas USA -- http://www.zebraimaging.com/ _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
