delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com> |
List-Archive: | <http://sourceware.cygnus.com/ml/cygwin-developers/> |
List-Post: | <mailto:cygwin-developers AT sourceware DOT cygnus DOT com> |
List-Help: | <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs> |
Sender: | cygwin-developers-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin-developers AT sourceware DOT cygnus DOT com |
From: | "Espen Harlinn" <espen DOT harlinn AT seamos DOT no> |
To: | <cygwin-developers AT sourceware DOT cygnus DOT com> |
Subject: | RE: /cygdrive/windows ? |
Date: | Wed, 3 May 2000 12:06:47 +0200 |
Message-ID: | <NCBBIMLDAJGCPAFLLELBAEAKCHAA.espen.harlinn@seamos.no> |
MIME-Version: | 1.0 |
X-Priority: | 3 (Normal) |
X-MSMail-Priority: | Normal |
X-Mailer: | Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) |
X-Mimeole: | Produced By Microsoft MimeOLE V5.00.2919.6600 |
In-Reply-To: | <20000503005341.B6109@cygnus.com> |
Importance: | Normal |
> On Tue, May 02, 2000 at 10:50:06PM -0400, DJ Delorie wrote: > > > >`cygpath --windir` > > > >The only time we'd need something like this visible outside a compiled > >application is a script, and a script can use cygpath to get the > >directory path and store it. Any compiled program can just call > >GetWindowsDirectory() itself. > > Actually, I was thinking that it would be nice to have this in a tar file: > > /cygdrive/system/some.dll . > > This would always extract some.dll to the windows/system directory. IMHO: Putting things in windows\system[32] is not a very bright idea, keeping the complete cygwin installation in a separate directory is how I like it. At various times it has been usefull to have several different cygwin installations installed into different directories. If some.dll goes into windows\system[32] the requirement for backwards binary compability becomes more stringent when changes are made to some.dll. There is also the slight problem that some.dll may allready exist on the target system and it might just be something quite different from your some.dll i.e. a name clash. Espen
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |