George Liu
2006-09-15 23:22:46 UTC
-----Original Message-----
Sent: Thursday, September 14, 2006 2:34 PM
Subject: Re: [omniORB] Unable to locate msvcr80.dll while
compilingomniorb3.0.4 with VC8(Visual Studio 2005)
2005)Sent: Thursday, September 14, 2006 2:34 PM
Subject: Re: [omniORB] Unable to locate msvcr80.dll while
compilingomniorb3.0.4 with VC8(Visual Studio 2005)
Date: Wed, 13 Sep 2006 16:28:21 -0700
Subject: [omniORB] Unable to locate msvcr80.dll while compiling
omniorb3.0.4 with VC8(Visual Studio 2005)
Content-Type: text/plain; charset="us-ascii"
I'm trying to compile omniORB 3.0.4 on XP with VC8 (Visual Studio
Subject: [omniORB] Unable to locate msvcr80.dll while compiling
omniorb3.0.4 with VC8(Visual Studio 2005)
Content-Type: text/plain; charset="us-ascii"
I'm trying to compile omniORB 3.0.4 on XP with VC8 (Visual Studio
I downloaded source file, and followed instructions in the README
Installed gnu-win32-lite and omnipython-x86_win32.
Omniidl.exe: Unable to locate component
The application has failed to start because of MSVCR80.dll was not
found. Re-installing the application may fix this problem.
Locate omniidl.exe.manifest in your build directory (and likewise forOmniidl.exe: Unable to locate component
The application has failed to start because of MSVCR80.dll was not
found. Re-installing the application may fix this problem.
all the DLLs).
You could either copy the manifest files to remain beside the exe and
DLL files at their final exported location.
Thanks for answering my question. I really appreciated your help. I
located all the four manifest files and copied them to bin\x86_win32
directory, and I'm a step forward.
Now the msvcr80.dll error went away, but a new one appeared when
Makefile is running
Omniidl -bcxx -Wbh=.hh -Wbs=SDK.cc -Wba -p..\..\..\src\lib\omniORB2
-ComniORB3 ..\..\..\idl\Naming.idl
An unhandled win32 exception occurred in omniidl.exe [3108]
Launching debugger doesn't help much. It just
Unhandled exception at 0x.... in omniidl.exe 0x....: Access violation
writing location 0x....
More hint?
Thanks
George
Alternatively, MSVC8
provides a tool called mt, which will let you compile the manifest
intomt -manifest msvc8.manifest -outputresource:omnithread32_rt.dll\;1
and likewise for all other DLLs/EXEs (where msvc8.manifest is a copy
ofand likewise for all other DLLs/EXEs (where msvc8.manifest is a copy
one of the generated manifests, which should all be the same). Note
thatthe slash before the ; is a shell escape, so if you are not using a
Cygwin/MSYS shell, you might not need it.
Presumably it would be worth fixing the build system to do this
automatically at some point, but I am not familiar enough with the
omniORB makefiles to offer a patch right now.
fixCygwin/MSYS shell, you might not need it.
Presumably it would be worth fixing the build system to do this
automatically at some point, but I am not familiar enough with the
omniORB makefiles to offer a patch right now.
I used the exact same step, except compiling with VC6, everything
worked. But I need to use VC8.
Googling shows that the problem is related to manifest. How should I
worked. But I need to use VC8.
Googling shows that the problem is related to manifest. How should I
it?
Thanks in advance.
George
_______________________________________________Thanks in advance.
George
omniORB-list mailing list
http://www.omniorb-support.com/mailman/listinfo/omniorb-list