in reply to Re: Re: Win32::Printer loadable object module?
in thread Win32::Printer loadable object module?

I have run the make file but I was under the impression that these makes files were only for *nix platforms which I am not trying to install it on.
Nope, it's not just for nix. That is the standard way to install perl modules (especially ones on CPAN).

I simply copied over the module because this is all that is generally needed for most modules.
In theory for pure-perl modules maybe, but by doing so you always miss out on the important work a module author does (making sure you have all the prerequisites, making sure the module will work(tests) ...).

If a module has specific requirements for install there should be an INSTALL.txt or a README or something.
Normally I'd agree with you, but seing how you got the distribution from CPAN, and it is a standard CPAN distribution despite the lacking README/INSTALL file, the installation instructions are the same as that of any standard cpan distribution (perlmodinstall - Installing CPAN Modules).

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

  • Comment on Re: Re: Re: Win32::Printer loadable object module?

Replies are listed 'Best First'.
Re: Re: Re: Re: Win32::Printer loadable object module?
by Elijah (Hermit) on Jan 08, 2004 at 16:06 UTC
    This comes straight from the link you gave on CPAN.

    If you're running ActivePerl (Win95/98/2K/NT/XP, Linux, Solaris) First, type ppm from a shell and see whether ActiveState's PPM repository has your module. If so, you can install it with ppm and you won't have to bother with any of the other steps here. You might be able to use the CPAN instructions from the "Unix or Linux" section above as well; give it a try. Otherwise, you'll have to follow the steps below. A. DECOMPRESS You can use the shareware Winzip ( http://www.winzip.com ) to decompress and unpack modules. B. UNPACK If you used WinZip, this was already done for you. C. BUILD Does the module require compilation (i.e. does it have files that end in .xs, .c, .h, .y, .cc, .cxx, or .C)? If it doesn't, go to INSTALL. If it does, life is now officially tough for you, because you have to compile the module yourself -- no easy feat on Windows. You'll need the nmake utility, available at ftp://ftp.microsoft.com/Softlib/MSLFILES/nmake15.exe D. INSTALL Copy the module into your Perl's lib directory. That'll be one of the directories you see when you type perl -e 'print "@INC"'
    It appears once you have the module unzipped and built (if neccessary) CPAN tells you to simply copy the module to your library also. This has always been the way I have done it. I don't understand, are you pointing out I was doing it right or pointing out I was doing it wrong with refrences from CPAN saying I was doing it right?

    Edit:

    Or maybe saying I missed .xs file and therefore missed the build step?

[reply]
      This comes straight from the link you gave on CPAN...
      *mutter* Weel, then that tutorial needs updating then (a thousand cpan authours don't write tests and Makefile.PL's for nothing -- that's why I pointed to A guide to installing modules initially, it's a better tutorial).
      Or maybe saying I missed .xs file and therefore missed the build step?
      I thought this was obvious (you did miss the .xs file).

      MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
      I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
      ** The third rule of perl club is a statement of fact: pod is sexy.

[reply]

In Section Seekers of Perl Wisdom