http://qs321.pair.com?node_id=1034072


in reply to Citrus Perl: problems trying to load additional modules

Remove Citrus Perl from the path and use bin/citrusterm.bat to open a terminal.

Yes, 'Having several Perl installations is perfectly "legal"', but you have to keep their environment separated. Can't mix DWIM Perl with Citrus Perl.

I have Citrus Perl 5.14 and 5.16 on my box and a shortcut on the desktop from each bin/citrusterm.bat script for opening a terminal and installing modules.

I use this script, inspired from citrusterm.bat, for the application shortcut (for the 5.14):

@echo off call C:\dev\Tpda3FpimmPerl\bin\citrusvars.bat Title Tpda3 ( CitrusPerl 5.14.2.1 x86 ) tpda3.bat %*

And Tpda3FpimmPerl is a custom Citrus Perl distribution with all my app modules installed.

Regards, Stefan

Replies are listed 'Best First'.
Re^2: Citrus Perl: problems trying to load additional modules
by Anonymous Monk on May 18, 2013 at 08:42 UTC

    Remove Citrus Perl from the path and use bin/citrusterm.bat to open a terminal.

    Um, no :) start+run+pathtocitrusterm.bat ought to work just fine

      For Citrus Perl, but won't interfere with DWIM Perl?

        For Citrus Perl, but won't interfere with DWIM Perl?

        Why would it do that?

        You said Remove Citrus Perl from the path and use bin/citrusterm.bat to open a terminal.

        Citrusterm doesn't interfere with citrusperl :)

        dwimperl, which is just a build of strawberryperl, adds strawberry perl to path

        citrusterm opens up cmd.exe, and calls citrusvars, which adds citrus FIRST in path

        strawberryperl should no longer interfere

        Although I always patch and rereun pl2bat for safety, see Fix_pl2bat