comment on

If your users demand a "proper" Windows installer, you can use, for example, 7-zip or NSIS, to create a Windows installer.

My tip: Don't freak out trying to understand NSIS ("A lovely coding experience with elements of PHP and assembly" - the worst parts of PHP and assembler, on the edge of Brainfuck), just use Inno Setup. Trivial for the most common cases, everything else can be scripted in plain Pascal.

See also Re: How do you distribute your Perl application to your customers? and Re^3: How do you distribute your Perl application to your customers?, using the same trick with an ancient version of ActivePerl.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

In reply to Re^2: dll not embedded in PAR::Packer's output by afoken
in thread dll not embedded in PAR::Packer's output by jowe

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks