> -----Original Message-----
> From: Fabio Quintao [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 04, 2000 3:24 AM
> To: [EMAIL PROTECTED]
> Subject: help me with perl TK!!
> 
> 
> Hi all!!
> 
>   i have some questions that is very easy for most of you 
> people on the
> list....well i'm trying to install the TK mod but i don't know why i
> have so many problems.
>   i'm using activestate, perl last version, and win 98.
>   my questions are:
> 
> should i have a c compiler in my computer?

You would only require a C compiler if installing/building a module/package
from C source. Usually if installing a package from CPAN, I find that I only
need a "make" program - and for win32, "nmake" is freely available for
download from Microsoft. Since most people don't have compilers on their
Win32 machines, packages can be prepared by those who do have access to a
compiler and distributed in a form suitable for use by the Perl Package
Manager (PPM). PPM comes with ActiveState Perl and it will be described in
your Perl documentation (ActiveState Perl installs a shortcut to its HTML
documentation in your start menu).

If I wanted to install the Tk package on Win32 ActiveState Perl, I would
connect to the internet, open a dos box, type "PPM install tk" (PPM is in
your PATH if ASPerl is installed with the default settings). PPM retieves
the package from ActiveState and installs it for you with documentation etc.

> after a decompress the mod from cpan....where should i put all the
> folders and file?
> should i use makefile.pl.....well i dowloaded the extension tar.gz.
> 
> please can someone answer my questions..
> thanks in advance
> Fabio

when using packages from CPAN, I generally unzip them to a temp directory
and follow the instructions inthe README file which is usually...

perl makefile.pl
make
make install
make test

...for Win32, replace make with nmake.

_______________________________________________
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users

Reply via email to