[omniORB] Unable to locate msvcr80.dll while compiling omniorb3.0.4 with VC8(Visual Studio 2005)

[Andrew Miller]

> Date: Wed, 13 Sep 2006 16:28:21 -0700
> From: "George Liu" <george.liu at ussj.ricoh.com>
> Subject: [omniORB] Unable to locate msvcr80.dll while compiling
> 	omniorb3.0.4	with VC8(Visual Studio 2005)
> To: <omniorb-list at omniorb-support.com>
> Message-ID:
> 	<8B8709E6C8B8784583FA9C7C013CB4512C7316 at etd1.etd.ussj.ricoh.com>
> Content-Type: text/plain; charset="us-ascii"
>
> I'm trying to compile omniORB 3.0.4 on XP with VC8 (Visual Studio 2005)
>
>  
>
> I downloaded source file, and followed instructions in the README file. 
>
> Installed gnu-win32-lite and omnipython-x86_win32. 
>
> While "make export", windows gives the following error:
>
>                                         
>
> 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 for 
all the DLLs).

You could either copy the manifest files to remain beside the exe and 
DLL files at their final exported location. Alternatively, MSVC8 
provides a tool called mt, which will let you compile the manifest into 
the binaries, so it doesn't need to be a separate file:

The correct invocation is:
mt -manifest msvc8.manifest -outputresource:omnithread32_rt.dll\;1

and likewise for all other DLLs/EXEs (where msvc8.manifest is a copy of 
one of the generated manifests, which should all be the same). Note that 
the 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.
>  
>
> 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 fix
> it?
>
>  
>
> Thanks in advance.
>
> George
>