Meta: See "Question" vs "Doubt"
Different operating systems have formats of executables, an executable built for one system won't work on another (incompatable) system.
You might be able to get something useful by running the generated executable under something like WINE on Linux.
| [reply] |
Different operating systems have formats of executables, an executable built for one system won't work on another (incompatable) system.
Well, let's say, it won't work without performing tricks. I have used heavily (in house) modified Pascal (!) compilers that generated binaries that ran on both SCO and VMS. It's dirty, it's tricky, but it worked. It can be done. But normally, you really, really don't want to.
| [reply] |
PAR's pp command can build executables for (some?) unixes and windows.
On the whole, you're probably better off just distrubuting the perl code on unix, since practically all unixes have a working perl environment.
| [reply] |
But one of the best things about Perl is the portability. Would it be acceptable to you to distribute your application without generating a binary executable? If so, and especially if you use pure Perl modules, you have many other distribution options. | [reply] |
According to a friend of mine who works at ActiveState, the PDK does not (yet) support cross-compilation.
If you make an executable on linux using the PDK for linux you will be able to run that on linux systems - we use that in production systems here, I believe. | [reply] |
| [reply] |
If you want to run Win32 .exe files on linux then have a look at wine. | [reply] |
