When you download the nmake15.exe, you must run it: it will create three other files (nmake.exe, nmake.err and a third unimportant read-me type file). Put nmake.exe and nmake.err somewhere in your path.

Then you must edit the config.pm file in perl/lib/CPAN so that the Config-hash has something like 'make' => q[C:\WINDOWS\system32\nmake.exe], (of course you would edit that to show where your nmake.exe is). I'm not entirely sure, but I think that when you put the full path to nmake.exe in the hash, nmake.exe does not have to be in your path. If you like to live dangerously, you can just put 'make' => q[nmake.exe], in the Config-hash.

CountZero

"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

In reply to Re: Module Problems by CountZero
in thread Module Problems by waiterm

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.