comment on

Running win32 perl under wine with win32 PAR? I do not think he wants to go there. First off, wine doesn't work half the time, second off...this is a fairly hackish solution.

Basically what the question-poster needs to know is that *NIX developers really have no interest in making cross compilers that target their arch-nemesis of an operating system. You can do cool things like cross-compile for AMD64 or IA64 on IA32, but you can't target foreign OS's (usually). Similarly, I don't think there are any win32 compilers that create Linux apps. The closest 'foreign' cross compiler I can think of is Watcom/OpenWatcom, which targets OS/2, Netware, DOS, and Win32 when running from Win32. Does this help with Perl? No. Are all of these OS's above really odd? Yes.

The only workable answer I can think of -- There may be ways to do this with VMware. VMWare would not be free, but it would allow you to install Windows on a Linux box and make it "believe".

My suggestion -- find the cheapest computer you can find, and get it to run Windows for you.

In reply to Re: Re: Making Perl EXE's on a *NIX machine by flyingmoose
in thread Making Perl EXE's on a *NIX machine by batkins

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.


laziness, impatience, and hubris
	PerlMonks