"porting" mods from cygwin to win32?

rvosa has asked for the wisdom of the Perl Monks concerning the following question:

Dear monks,

is there any possibility of moving the compiled *.dll XS (or inline c...) extensions from a cygwin environment to a win32 environment? Most of the time stuff builds just fine on cygwin, but getting anything other than pure perl to build on win32 is a tricky proposition (for me). Is there a possibility of somehow moving the binaries over to a lib/ folder for, say, ActivePerl?

Normal cygwin executables move just fine if you include cygwin1.dll, so perhaps something similar is possible... okay, clutching at straws, but you never know...

Thanks!

Comment on "porting" mods from cygwin to win32?

Replies are listed 'Best First'.
Re: "porting" mods from cygwin to win32? by fglock (Vicar) on Jun 18, 2005 at 23:16 UTC
You can call cygwin's Perl from a Windows session: `D:\> e:\cygwin\bin\perl -v This is perl, v5.8.5 built for cygwin-thread-multi-64int` [download] Normal cygwin executables move just fine if you include cygwin1.dll This works with cygwin's Perl too (you may have to include a few other dlls).	[reply] [d/l]
Re: "porting" mods from cygwin to win32? by BUU (Prior) on Jun 18, 2005 at 17:29 UTC
Not really, no, since your compiled modules are going to be linked against Cygwin's perl.so thingy. Why don't you just get a freeware compile for win32 and compile your own perl?	[reply]
Re^2: "porting" mods from cygwin to win32? by polettix (Vicar) on Jun 18, 2005 at 20:18 UTC
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.	[reply]
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


good chemistry is complicated, and a little bit messy -LW
	PerlMonks