-Original Message-
From: bulk88
Sent: Friday, January 09, 2015 4:16 PM
To: module-authors@perl.org ; perl5-port...@perl.org
Subject: name for a Module to build XS with Visual C on a core Mingw GCC
Perl
ActivePerl in 5.16 and before had code to build XS modules with
dmake/mingw/gcc
-Original Message-
From: bulk88
Sent: Friday, January 09, 2015 9:40 PM
To: sisyph...@optusnet.com.au
Cc: module-authors@perl.org ; Perl 5 Porters
Subject: Re: name for a Module to build XS with Visual C on a core Mingw GCC
Perl
From memory, Win32::SharedFileOpen was unusable if the
On 9 January 2015 at 10:40, bulk88 wrote:
> sisyph...@optusnet.com.au wrote:
>> If different runtimes are used (as might happen with your other-way-about
>> configuration) then you can run into problems - eg when a handle that has
>> been created by one runtime gets passed to the other runtime (wh
sisyph...@optusnet.com.au wrote:
-Original Message- From: bulk88
Sent: Friday, January 09, 2015 4:16 PM
To: module-authors@perl.org ; perl5-port...@perl.org
Subject: name for a Module to build XS with Visual C on a core Mingw GCC
Perl
ActivePerl in 5.16 and before had code to build XS
ActivePerl in 5.16 and before had code to build XS modules with
dmake/mingw/gcc, while the perl core was compiled with Visual C. Going
the other way, Visual C extensions with a GCC core has never been done.
I've managed to get 1 XS module to compile and run with a VC XS DLL and
a GCC Perl inter
