X-Spam-Check-By: sourceware.org Message-ID: <85a409ca0607091238n27d1851dn3beedd4a9660064f@mail.gmail.com> Date: Mon, 10 Jul 2006 07:38:13 +1200 From: "Paul Dorman" To: cygwin AT cygwin DOT com Subject: Re: In scripts suddenly must use perl.exe rather than perl In-Reply-To: <002f01c6a378$332d7d20$0a10a8c0@holgerdanske.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <002f01c6a378$332d7d20$0a10a8c0 AT holgerdanske DOT local> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 7/10/06, David Christensen wrote: > zzapper wrote: > > c:/usr/local/bin/perl sdbk.pl $* (hard path to activestate perl) > > It was my experience that mixing Cygwin and ActiveState Perl was a > recipe for frustration. Why can't you just use Cygwin Perl? > > > David I was recently working in an environment where ActivePerl is the default (not all systems have Cygwin), and Cygwin Perl is left for built-in Cygwin utilities to use. To accomplish this we simply put ActivePerl first on the %PATH%. Most Unix-style scripts use a shebang of #!/usr/bin/perl, so they would be unaffected by the change. You just have to remember to use /usr/bin/perl on the command line when you want the Cygwin implementation, and this usually only makes sense when running the Cygwin environment. We did try the link method (renaming all the Cygwin Perl programs and creating links to the ActivePerl, but his breaks things that need things like STDIN and STDOUT (like ReadKey). Regards, Paul -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/