Build for windows with cygwin - manifest error

Question

4.00/5 (1 vote)

See more:

Hi,

I am building ACE + TAO 6.0.1 for windows using cygwin and the ACE makefiles with visual studio 2008 compiler.

Everything is fine and dandy except for the debug versions - first the linker couldn't find msvcr90d so I added is to the path, but now the error is that is can't find the manifest files for tao_idl.exe and gperf

error R6304:
An application has made an attempt to load the C runtime library without using a manifest. This is an unsupported way to load Visual C++ DLLs. You need to modify your application to build with a manifest. For more information, see the "Visual C++ Libraries as Shared Side-by-Side Assemblies" topic in the product documentation.
so the question is - how do I set an environment variable is cygwin to point to the manifest file or where should I put them (I tried with msvc90d and with the exe files)

Thank you,
Eran

Posted 16-May-11 21:12pm

Member 7919447

Updated 16-May-11 21:13pm

walterhevedeich

v2

Add a Solution

Comments

walterhevedeich 17-May-11 3:14am

removed pre tags

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard MacCutchan · Answer 1 · 2011-05-16T22:37:00

Solution 1

I think you need a file similar to the following with the same name as your project and the extension .manifest:

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestversion="1.0">
  <assemblyidentity>
    type="win32"
    name="your project name"
    processorArchitecture="x86"
    version="1.0.0.0"
    />
  <description>your description here.</description>
</assemblyidentity>
</assembly>

Posted 16-May-11 22:37pm

Richard MacCutchan

Updated 16-May-11 22:38pm

v2

Comments

Albert Holguin 17-May-11 10:04am

See OP's new comment (posted as solution)

Member 7919447 17-May-11 10:13am

Hi,
yeah, I know.
I have it.
problem is the linker or whoever, can't find it.
I am trying to embed the manifest using "mt -manifest bla.manifest -outputresource:bla.exe" but that doesn't seem to work either.

Richard MacCutchan 17-May-11 10:51am

I think you need some extra option on your link command; take a look at the manifest section on MSDN at http://msdn.microsoft.com/en-us/library/f2c0w594(VS.80).aspx. I have not tried to do this manually as it is always managed by my Visual Studio system, and I have not used cygwin for a number of years.