X-Spam-Check-By:	sourceware.org
From:	Richard Foulk <richard AT skydive1 DOT com>
Message-Id:	<200612122106.kBCL68Hc001649@sd.skydive1.com>
Date:	Tue, 12 Dec 2006 11:06:08 -1000
To:	cygwin AT cygwin DOT com
Subject:	library paths
References:	<1165944511 DOT 12358 DOT ezmlm AT cygwin DOT com>
In-Reply-To:	<1165944511.12358.ezmlm@cygwin.com>
User-Agent:	nail 11.20 1/13/05
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Running cygwin on a number of diverse machines, accessability of
cygwin1.dll and others can be a problem.

We use perl a lot and are looking into building a standard routine for
the beginning of each script that will add to the path where necessary.
And perhaps even remove from the path if two or more instances of the
key libraries are found.

Has anyone done something like this?  Any suggestions?


Thanks

Richard


--
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/

- Raw text -