compiling modules for activeperl

Mathieu Longtin wrote:
> I'm trying to compile and debug DBD::SQLite using
Activeperl on
> windows.
>
> What compiler should I be using to generate compatible
DLLs?

DBD::SQLite is actually already bundled with the last couple
of
releases of ActivePerl (because it is being used by PPM4).

If you want to compile XS modules yourself for ActivePerl,
then
the following compilers are recommended:

  Microsoft Visual C++ 6.0 (Visual Studio 98)
  MinGW GCC with dmake

Both compilers will work out-of-the-box with newer
ActivePerl
versions.  ActivePerl will try to use VC++, but if it fails
to
locate it on the PATH, it will fall back to using GCC.

You can use VC++ 7 (VS.NET) or VC++ 7.1 (VS.2003), but
you'll
pick up an additional runtime dependency on MSVCR70.DLL or
MSVCR71.DLL.

Cheers,
-Jan

_______________________________________________
ActivePerl mailing list
ActivePerllistserv.ActiveState.com
To unsubscribe: http:/
/listserv.ActiveState.com/mailman/mysubs

Hi Jan,

I have seen that the older versions of nmake cannot be use
to compile some 
perl modules, so I need to use the nmake version from VS.net
2005.
If I have VS 6 and VS.net 2005, can I use VS6 and the nmake
from VS.net 
2005?
Does this create those dependencies?

Thanks.


Octavian

----- Original Message ----- 
From: "Jan Dubois" <jandactivestate.com>
To: "'Mathieu Longtin'" <mathieuclosetwork.org>; 
<activeperllistserv.ActiveState.com>
Sent: Tuesday, April 03, 2007 1:35 AM
Subject: RE: compiling modules for activeperl


> Mathieu Longtin wrote:
>> I'm trying to compile and debug DBD::SQLite using
Activeperl on
>> windows.
>>
>> What compiler should I be using to generate
compatible DLLs?
>
> DBD::SQLite is actually already bundled with the last
couple of
> releases of ActivePerl (because it is being used by
PPM4).
>
> If you want to compile XS modules yourself for
ActivePerl, then
> the following compilers are recommended:
>
>  Microsoft Visual C++ 6.0 (Visual Studio 98)
>  MinGW GCC with dmake
>
> Both compilers will work out-of-the-box with newer
ActivePerl
> versions.  ActivePerl will try to use VC++, but if it
fails to
> locate it on the PATH, it will fall back to using GCC.
>
> You can use VC++ 7 (VS.NET) or VC++ 7.1 (VS.2003), but
you'll
> pick up an additional runtime dependency on MSVCR70.DLL
or
> MSVCR71.DLL.
>
> Cheers,
> -Jan
>
> _______________________________________________
> ActivePerl mailing list
> ActivePerllistserv.ActiveState.com
> To unsubscribe: http:/
/listserv.ActiveState.com/mailman/mysubs 

_______________________________________________
ActivePerl mailing list
ActivePerllistserv.ActiveState.com
To unsubscribe: http:/
/listserv.ActiveState.com/mailman/mysubs

On Mon, 02 Apr 2007, Octavian Rasnita wrote:

Hi Octavian,

> I have seen that the older versions of nmake cannot be
use to compile
> some perl modules, so I need to use the nmake version
from VS.net
> 2005. If I have VS 6 and VS.net 2005, can I use VS6 and
the nmake from
> VS.net 2005? Does this create those dependencies?

No, the dependencies on msvcr7X.dll arise from using the VC7
compiler;
the version of nmake.exe is immaterial for this.

However, I'm curious which modules will require a newer
version of
nmake.exe.  The Makefile is normally generated by
ExtUtils::MakeMaker,
which should generate a file compatible with nmake.exe from
VC6.

Cheers,
-Jan

_______________________________________________
ActivePerl mailing list
ActivePerllistserv.ActiveState.com
To unsubscribe: http:/
/listserv.ActiveState.com/mailman/mysubs

Hi Jan,

I have seen that some modules, like Catalyst if I remember
well, generate a 
very long list of tests, and the older version of nmake
cannot handle a very 
long line, and that's why a newer version of nmake is
required.

If using the cpan shell, it uses nmake automaticly to run
the tests, and it 
crashes.

Of course, it works if I use force install, but then I don't
know if there 
were errors or not.

Octavian

----- Original Message ----- 
From: "Jan Dubois" <jandactivestate.com>
To: "'Octavian Rasnita'" <orasnitagmail.com>; "'Mathieu Longtin'" 
<mathieuclosetwork.org>; <activeperllistserv.ActiveState.com>
Sent: Tuesday, April 03, 2007 9:28 AM
Subject: RE: compiling modules for activeperl


> On Mon, 02 Apr 2007, Octavian Rasnita wrote:
>
> Hi Octavian,
>
>> I have seen that the older versions of nmake cannot
be use to compile
>> some perl modules, so I need to use the nmake
version from VS.net
>> 2005. If I have VS 6 and VS.net 2005, can I use VS6
and the nmake from
>> VS.net 2005? Does this create those dependencies?
>
> No, the dependencies on msvcr7X.dll arise from using
the VC7 compiler;
> the version of nmake.exe is immaterial for this.
>
> However, I'm curious which modules will require a newer
version of
> nmake.exe.  The Makefile is normally generated by
ExtUtils::MakeMaker,
> which should generate a file compatible with nmake.exe
from VC6.
>
> Cheers,
> -Jan
> 

_______________________________________________
ActivePerl mailing list
ActivePerllistserv.ActiveState.com
To unsubscribe: http:/
/listserv.ActiveState.com/mailman/mysubs