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

[George Liu]

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.



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



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20060913/d6245e5a/attachment.htm

[Andrew Miller]

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 2005)
I downloaded source file, and followed instructions in the README file.
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 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

[Duncan Grisby]

Post by George Liu
I'm trying to compile omniORB 3.0.4 on XP with VC8 (Visual Studio 2005)

Is there a good reason that you're trying to compile such an old omniORB
version with such a new version of Visual Studio? omniORB 4.0.7 and
4.1.0 both work fine with VS 8.

To make the build of 3.0.4 work, you might be able to compare all the
make files between the 3.0.4 and 4.0.7 releases to see what's changed,
but it will be quite painful, I expect. It will almost certainly be
better for you to use a newer omniORB release.

Cheers,

Duncan.

[George Liu]

-----Original Message-----
Sent: Sunday, September 17, 2006 12:53 PM
To: George Liu
Subject: Re: [omniORB] Unable to locate msvcr80.dll while compiling
omniorb3.0.4 with VC8(Visual Studio 2005)

Post by George Liu
I'm trying to compile omniORB 3.0.4 on XP with VC8 (Visual Studio

2005)

Is there a good reason that you're trying to compile such an old

omniORB

version with such a new version of Visual Studio? omniORB 4.0.7 and
4.1.0 both work fine with VS 8.

[George Liu]
I know it's somewhat weird that anyone would use an ancient version of
open source software.
My situation is I'm building customization for a software pack which
includes omni ORB3.0.4. I cannot change the "core" software, but only
build additional features / UIs for it. That's why I'm using VC8 and
3.0.4.

To make the build of 3.0.4 work, you might be able to compare all the
make files between the 3.0.4 and 4.0.7 releases to see what's changed,
but it will be quite painful, I expect. It will almost certainly be
better for you to use a newer omniORB release.
Cheers,
Duncan.
--
-- Duncan Grisby --
-- http://www.grisby.org --