in reply to Re: a tale of the windows runtime libs
in thread a tale of the windows runtime libs

ActiveState Perl is built using a compiler that uses the run-time library that's used by the Windows internal stuff and many supplied apps, so that's easier

Both ActiveState Perl and Strawberry Perl use the same C runtime. Wrt to cfreeman's specific issues, neither has any advantage over the other.

cfreeman have you considered using the MinGW compiler (that ships with Strawberry Perl, and is also freely available elsewhere) to build the dll's - instead of using the incompatible VC9 ? That would be the best solution, imo - there would then be no problem using those dll's with either ActivePerl or Strawberry Perl.

Cheers,
Rob
  • Comment on Re^2: a tale of the windows runtime libs

Replies are listed 'Best First'.
Re^3: a tale of the windows runtime libs
by John M. Dlugosz (Monsignor) on Jun 05, 2009 at 14:44 UTC
    It would still have the malloc/free problem with ActiveState.

    If the XS doesn't use the rtl's malloc and free (see the other reply from Anonymous), I agree the MinGW's code is easier to distribute.