This is effectively a follow-up to the issue I raised in Re^4: Missing bufferoverflowU.lib.

Later versions of MSVC compiler suites require an additional step in the build process to attach a 'manifest' resource to executable binaries (.exes & .dlls). The manifest files themselves are produced by the linker automatically. All that is required is to attach those files to the binaries (also produced by the linker) using mt.exe

(Quite why the linker can't do this for us automatically is moot question!).

Without this step being invoked, any attempt to load the dlls results in runtime error:

R6034: An application has made an attempt to load the C runtime librar +y incorrectly.

The problem is, that existing EU::MM (and similar) produced makefiles have a 'manifest' target and the command to invoke mt.exe to perform the attachment, but that target does not have any dependancies and so is never invoked.

Whilst I can hack my way past the problem for individual makefiles--by modifying the makefile before using it--that is not a good solution when attempting to install complex packages with many dependancies. Using CPAN for example.

Presumably, as the 'manifest' target is being produced by (most?) makefile.pls, the correct place to fix this is somewhere inside the EU::MM stuff. Does anyone have any cluebats as to how to go about this?


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to A permanent fix for the Windows 'manifest' issue? by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.