Hi Hartmut,
it will have bindings to two different C
runtimes. Intermediate manifests are forcibly linked into your binaries.
What? I thought the runtime version issues only affected the C++
runtime, not the C runtime? At least with VC++ 2005, pure-C libraries
had no issues with runtime versions...
We have not moved to VC++ 2008 yet, but this development might make us
consider waiting to see if the situation will be better in the next
version and just skipping this one...
So I resorted finally to the solution Christian was suggesting earlier -
shipping the VisualStudio 2008 SP1 redistributable (adding ~4MByte to an
normally 5MByte installer) with my application. Its the only way to get
all redirected manifests to point to the one and true VC runtime. Oh,
and if you do so don't put the redist manifests and DLLs in the binary
directory as they will break everything again. So finally Microsoft
managed to let us C++ developer feel like C# or Java developers - don't
forget that runtime of yours.
Or just include a note in the documentation that the runtime must be
installed, or make a check to make sure it has already been installed
before... Why bundle the runtime in each version when it just needs to
be installed once (or upgraded when a new SP comes out)? And it's
possible that the user has had to install it before for another application.
I'm not saying this is not a problem, but there are solutions that don't
force you to bloat your installer.
J-S
--
______________________________________________________
Jean-Sebastien Guay jean-sebastien.g...@cm-labs.com
http://www.cm-labs.com/
http://whitestar02.webhop.org/
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
