One possibility might be to make sure that use Win32::Api is included in the script somewhere. If your module is making calls to that module then you probably need both in order for it to work, right?

Otherwise, try adding a line like #perl2exe_include somemodule.pm at the start of the script.

Also, try perl2exe with the -tiny option and make sure that the dlls are being created (look for yourmodname.dll), or when running the compiled script check c:\temp for the dlls.

If we could get the actual error message and maybe a log of what p2exe is doing when you compile it that may be helpful.

In reply to Re: Perl2exe and non-autoloaded DLLs? by the_slycer
in thread Perl2exe and non-autoloaded DLLs? by Guildenstern

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.