[osg-users] probs running OSG on non-dev system?

Olaf Flebbe fgfs at oflebbe.de
Sat Sep 15 11:52:11 PDT 2007


Hi,

The official location for this vcredist_x86.exe is
http://www.microsoft.com/downloads/details.aspx?FamilyID=200B2FD9-AE1A-4A14-984D-389C36F85647&displaylang=en

This is the updated SP1 redistributable, works for plain MSVC8 too.

Cheers
   Olaf


Thrall, Bryan schrieb:
> Paul at Tcl3D wrote on Friday, September 14, 2007 3:12 PM:
>> Hi Mike,
>>
>> My bells rang: Include a manifest.
>>
>> For DLL's:
>> mt -manifest test.dll.manifest -outputresource:"test.dll;2"
>>
>> For EXE's:
>> mt -manifest test.exe.manifest -outputresource:"test.exe;1"
> 
> Also, the MSVCRT used by VS8 is not typically installed on WinXP, so
> this link might help:
> 
> http://msdn2.microsoft.com/en-us/library/ms235299(VS.80).aspx
> 
> Basically, Visual Studio 8 includes a file (on my PC its in C:\Program
> Files\Microsoft Visual Studio
> 8\SDK\v2.0\BootStrapper\Packages\vcredist_x86) vcredist_x86.exe that
> will install the updated MSVCRT for you and allow the app to run.
> 
>> Mike Weiblen wrote:
>>> Pardon the sparse details, had a problem in wee hours this morn...
>>>
>>> Built a 2.1.10-ish OSG on one system w/ winxppro/vs8, tried to run
>>> the resulting osgviewer on a different system w/ winxphome but no VS8
>>> installed.  I got entirely unhelpful errormsgs/dialogs along the
>>> lines of "that application cant be run" or "trying reinstalling the
>>> app".  The VS8 runtime libs were present on the non-VS8 system
>>>
>>> Does this ring any bells?  Could the VS8 or Cmake ocnfigs be
>>> triggering some OS or binary dependency? 




More information about the osg-users mailing list