When ActivePerl detects that you have MinGW and don't have Microsoft's Visual C, it'll monkeypatch Config into using it for building modules instead. For XP, Microsoft's nmake works fine, but alternatively you can use dmake too, allegedly. You also need a make utility, which you already need when building plain utilities with CPAN. It'll download and install the packages you need. Go to the download page, and download the installer, the first link. You can use MinGW (gcc for Windows) to install XS modules for ActivePerl, with CPAN. As far as I understood - it's much easier with Strawberry Perl. I did not find a pre-built PPM package for ActivePerl. My only quarrel with Strawberry Perl is it doesn't ship with Win32::* which when changing machines and installing Perl as much as I do can be frustrating as I regularly need it. I've never tried it, but it seems logical, Hope it helps.Īs I'm sure know there are three distributions of Win32 Perl UPDATE: These paths for example only see syphilis post for best answer. You could try installing them in different locations if it's possible and use the full path to it. Re: "Strawberry Perl" - can it live together with ActivePerl 5.10.0 Build 1003 (on WinXP)?Īs far as I know when I've had both installed I couldn't used ActivePerl due to Strawberry Perl already being first installed. Or call it from autoexec.bat, and reboot :) But it's much simpler to just enter ap1003 and have ap1003.bat "set" the environment as you want. You'd have to use set every time you open a new terminalĮffectively, yes. Re^3: "Strawberry Perl" - can it live together with ActivePerl 5.10.0 Build 1003 (on WinXP)? Unless you use setx from windows toolkit. You'd have to use set every time you open a new terminal. Re^2: "Strawberry Perl" - can it live together with ActivePerl 5.10.0 Build 1003 (on WinXP)? You can, of course, always call a specific perl executable by quoting the full path to it - eg C:\strawberry\perl\bin\perl will always run C:\strawberry\perl\bin\perl.exe no matter which "perl" (if any) comes first in the path environment variable. Any time "perl" is invoked, it will be the first "perl" executable to be found that will be run. I don't think so (if I understand the question correctly). For example, if I want to use ActivePerl build I just run ap822.bat which sets the path (and any other environment variables I might want set) appropriately for me.Ĭan I define for a script which Perl to use? If you have questions or comments, please let me know.Rather than remembering where all of these different perls are installed, it's easier to put those commands in separate batch files, and then just run the appropriate batch file for whichever perl you want. The script was tested with this version of Perl (Windows 2003/Windows 2008): UPDATE: An additional batch will be created, which alows to modify existing libaries and devices. ActiveState Perl) is required (as the Data Protector Perl modules are written in 32Bit) see the download link for the Perl version below. The Perl script will be distributed as source, to run the script a 32Bit Perl (i.e. UPDATE: Version 1.02 fixes a problem with too short or too long device names, it now can run on Windows 2003, Windows 2008 and Windows 2008 R2. The files are generated in a subfolder of the log folder of Data Protector. In addition a batch is generated which allows the import of the libraries and devices into Data Protector. I wrote a small tool to save the configuration of your libraries and devices to text files. In article Recover Cell Server I already informed about obrindex.dat. For a Disaster Recovery of you cell server it is recommended to save information about your libraries and devices.
0 Comments
Leave a Reply. |