From: Wolf Geldmacher <wolf.geldmacher@abacus.ch>
To: cygwin@cygwin.com
Subject: Re: How to handle length limit of PATH environment variable
Date: Thu, 05 Apr 2018 10:06:00 -0000 [thread overview]
Message-ID: <08077aa1-2da3-d381-8592-20c39acf063d@abacus.ch> (raw)
In-Reply-To: <ebd804f3-8e24-d96f-7ef4-0e1279afd929@gmail.com>
On 05.04.2018 11:19, Peter Bauer wrote:
> hi,
>
> i was bitten by the length limit of the PATH variable of 4095
> characters (see [1]) and could not find a way around it. This means i
> have a lot of software packages in different directories and each of
> them adds itself to the PATH so one can run the executables and have
> the shared libs available. Under Windows there is the "short path
> workaround" but what to do under Cygwin?
> Creating links with shorter names to the directories is not feasible
> since there may be different users and different directories per user.
>
> Any ideas?
On Unix (though not on cygwin) I've previously solved such issues by
writing a script that collects symlinks to the contents of some list of
directories in a few (system and/or user specific) directories. These
few directories then take the place of the list.
The script will need to be re-run whenever there are changes to the
directories on the list, but that can usually be automated.
Cheers,
Wolf
> thx,
> Peter
>
>
> [1]
> https://software.intel.com/en-us/articles/limitation-to-the-length-of-the-system-path-variable
>
> --
> Problem reports:Â Â Â Â Â Â http://cygwin.com/problems.html
> FAQ:Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â http://cygwin.com/faq/
> Documentation:Â Â Â Â Â Â Â Â http://cygwin.com/docs.html
> Unsubscribe info:Â Â Â Â Â http://cygwin.com/ml/#unsubscribe-simple
>
--
"Il semble que la perfection soit atteinte non quand il n'y a plus rien à ajouter, mais quand il n'y a plus rien à retrancher."
- Antoine de Saint-Exupéry, Terre des Hommes
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-04-05 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 9:19 Peter Bauer
2018-04-05 10:06 ` Wolf Geldmacher [this message]
2018-04-05 16:26 ` Brian Inglis
2018-04-05 11:50 ` Steven Penny
2018-04-05 17:50 ` Andrey Repin
2018-04-05 18:48 ` Achim Gratz
2018-04-06 0:35 ` Andrey Repin
2018-04-11 13:43 ` Peter Bauer
2018-04-06 0:31 ` Hans-Bernhard Bröker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=08077aa1-2da3-d381-8592-20c39acf063d@abacus.ch \
--to=wolf.geldmacher@abacus.ch \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).