X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=bHm0MEdJykdFU6N3
	K+GpdqaZn4p/t1gAGJSmpECE6OWTGK4xLeHaJspBxXnikAeMhlKUJ2DH6XkMCrze
	nxIOnyODAXuwJsPeRdJ9M0NumOPcgln9vxTnJvbjGkuexdCj8Jz8PTuPXUuNkLPt
	t45yTA5hsx5kIbEPrufnqS7uBuY=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=/0X9l5ZGR/ehKJ5iC0Je+w
	VBW3k=; b=eRvKH1609h1IQdCeqf/LbiHNABy6vLxnfJrX9WyvziT/nciagDk8E2
	OkSRTeGQ7ONDdpR4plN1h1dlZ08N9q8OA/dJvatV7PUUw2QMuXNHWh/iaobputpB
	P31RnsDsDUh+IJuAGKhD0OJZdCLPmDw0IDt+aEE2dJ3ep8nD3S4yA=
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
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-5.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=
X-HELO:	atfriesa01.ssi-schaefer.com
Subject:	Re: How to query the value of %SystemDrive% in an empty environment?
To:	cygwin AT cygwin DOT com
References:	<089bb243-1dbb-048a-39aa-f54048a39e26 AT ssi-schaefer DOT com> <0f9d219c-a9ae-237a-afcf-9dcc5a13bc01 AT SystematicSw DOT ab DOT ca> <ebba0d18-d4d1-dd3c-bd52-b91489106cbf AT ssi-schaefer DOT com> <20190807111943 DOT GC11632 AT calimero DOT vinschen DOT de>
From:	Michael Haubenwallner <michael DOT haubenwallner AT ssi-schaefer DOT com>
Openpgp:	preference=signencrypt
Message-ID:	<fa465b72-8a91-fa7a-8a9e-2dd2cc5e1ee0@ssi-schaefer.com>
Date:	Wed, 7 Aug 2019 14:41:02 +0200
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version:	1.0
In-Reply-To:	<20190807111943.GC11632@calimero.vinschen.de>

On 8/7/19 1:19 PM, Corinna Vinschen wrote:
> On Aug  7 13:08, Michael Haubenwallner wrote:
>> On 8/7/19 4:33 AM, Brian Inglis wrote:
>>> On 2019-08-06 09:20, Michael Haubenwallner wrote:
>>>> using 'env -i' to create an empty environment, the SYSTEMROOT and WINDIR
>>>> environment variables are preserved (or recreated):
>>>>  $ /usr/bin/env -i /usr/bin/env
>>>>  SYSTEMROOT=C:\Windows
>>>>  WINDIR=C:\Windows
>>>> And with cygpath, there is the -A, -D, -H, -O, -P, -S, -W and even -F flags
>>>> to query the values for various directories.
>>>> Now what I've failed to find is how to query the value for the "SystemDrive"
>>>> environment variable.
>>>> The problem behind is that I'm using "vswhere.exe" to locate some Visual Studio
>>>> environment from within some scripts run via 'env -i', causing vswhere.exe to
>>>> create a directory named "%SystemDrive%" in the current working directory:
>>>> So I better ensure the SystemDrive environment variable is set for vswhere.exe.
>>>> Any ideas?
>>>
>>> There is a reg entry:
>>>
>>> $ head
>>> /proc/registry/HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/SystemBootDevice;
>>> echo
>>> multi(0)disk(0)rdisk(1)partition(3)
>>>
>>> but how do you convert that to a device letter?
>>>
>>> SYSTEMDRIVE is a dynamic env var created at startup pointing to the boot drive
>>> letter. It is not instantiated anywhere else as far I could find. A number of
>>> low level reg entries use that env var. Only option is to pass it through:
>>
>> Heck, even CreateEnvironmentBlock() relies on SYSTEMROOT env var being set,
>> otherwise returning things like ProgramData="%SystemDrive%\ProgramData".
> 
> So, what does this have to do with Cygwin in case you clean out the
> environment?  This is nothing you want to do if you plan to start
> a non-Cygwin executable.

I do prefer to have full control over the environment, recreating the needed
vars from the registry or similar, because I did have too much troubles with
polluted environment already.  This also applies to setting up some wrapper
around the MSVC toolchain, that provide the vswhere.exe helper these days.

Actually I would have been fine it was obvious enough to locate SYSTEMDRIVE,
much like SYSTEMROOT and WINDIR are available via cygpath, or reading other
specific environment variable values from /proc/registry/.

As SYSTEMROOT and WINDIR are preserved already, even if they are available
via cygpath as well, also preserving SYSTEMDRIVE simply feels suitable here.
And even more since I found this commit, which seems to intent the same:
https://cygwin.com/git/gitweb.cgi?p=newlib-cygwin.git;a=commitdiff;h=1f99dd3ecf3252517363ec8f0fec4b0a95706f31

Anyway: If it is possible to map above SystemBootDevice registry value to
SYSTEMDRIVE, I would be fine as well.

Thanks!
/haubi/

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

- Raw text -