This is the mail archive of the
mailing list for the Cygwin project.
Re: Wish Setup would accept my Perl
At work, we develop using both Cygwin's perl and AS's perl (we
distribute our app to people without Cygwin but with ActivePerl). The
reason for using two different perls is to be able to test for
regressions between them. If a regression is found, it means that
we've made some incorrect assumption or that we found some
implementation specific behavior that we need to watch out for. We've
written the perl scripts in a manner that should make them portable
--- we manage paths by checking $^O and using `cygpath` accordingly.
To handle launching either perl, our team has made a symlink from the
AS `perl` to `perl-as` that is in our PATH. Thus, we can invoke either
`perl` to get Cygwin's perl or `perl-as` to get AS's perl. This is
also necessary because we utilize SWIG and it needs to know what perl
to link against when building. When an end user invokes our program,
it will fire up using `perl` which is probably AS perl but it could be
Cygwin's perl. Either one works fine (we have some DynaLoader magic to
load the appropriate SWIG binary modules) and everyone is happy.
On Dec 6, 2007 7:48 PM, Warren Young <email@example.com> wrote:
> Michael Kairys wrote:
> > I want to type "perl foo.pl" at the Bash prompt
> > I suppose I could rewrite my Bash aliases so "foo" equals "/c/Perl/bin/perl
> > foo.pl"
> The solution is to break your habit of saying "perl foo.pl".
> If the first line of a text file begins with "#!" and a valid path name
> to an executable follows it, Cygwin -- like any *ix -- will consider the
> executable to be the interpreter for that file, and pass the script as
> the first argument to the interpreter. So, if you put:
> at the top and run it with the command "foo.pl" from a Cygwin Bash
> prompt, you get Cygwin perl. No need to reference perl explicitly.
> If you find that you still need ActiveState Perl, you can use Windows
> Explorer to associate .pl with it. Then if you run foo.pl from a Run
> box, an Explorer window, or a cmd.exe prompt, you get AS Perl.
> None of this helps if you want to use AS Perl from Cygwin or vice versa,
> of course.
> 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/
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html