Re^2: "porting" mods from cygwin to win32?

I recently compiled perl using MinGW, but it produces its own perl-something.dll. I successfully compiled a perl-embedding program with static linking, but even with this setting I am still forced to use the perl-something.dll library.

What I infer from these (admittedly few) facts is that you probably have to use the same compiler as ActiveState if you want to move modules/libraries like the OP wants, so getting a freeware compiler won't probably help.

Flavio (perl -e 'print(scalar(reverse("\nti.xittelop\@oivalf")))')

Don't fool yourself.

Comment on Re^2: "porting" mods from cygwin to win32?

Replies are listed 'Best First'.
Re^3: "porting" mods from cygwin to win32? by jordanh (Chaplain) on Jun 18, 2005 at 21:31 UTC
What I infer from these (admittedly few) facts is that you probably have to use the same compiler as ActiveState if you want to move modules/libraries like the OP wants, so getting a freeware compiler won't probably help. I believe whatever compiler ActiveState uses, it would be compatible with the Free-to-use command-line version of MSC that Microsoft distributes. I would caution that I've never tried this, however, so there might well be some aspect of using this compiler to integrate XS modules into ActiveState that I'm not considering. If this didn't work directly, I suspect that one could download the ActiveState code and rebuild it with this free compiler and then do XS/dll development with the resulting system.	[reply]
Re^4: "porting" mods from cygwin to win32? by BUU (Prior) on Jun 18, 2005 at 22:33 UTC
Last time I looked, activestate used msvc6 to compile their perl, which I don't believe is compatible with the free one. However, since you have a free compiler, make your own perl, then you can compile anything you want!	[reply]