From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: How to query the value of %SystemDrive% in an empty environment?
Date: Wed, 07 Aug 2019 02:33:00 -0000 [thread overview]
Message-ID: <0f9d219c-a9ae-237a-afcf-9dcc5a13bc01@SystematicSw.ab.ca> (raw)
In-Reply-To: <089bb243-1dbb-048a-39aa-f54048a39e26@ssi-schaefer.com>
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:
$ /usr/bin/env -i SYSTEMDRIVE="$SYSTEMDRIVE" /usr/bin/env
SYSTEMDRIVE=C:
SYSTEMROOT=C:\WINDOWS
WINDIR=C:\WINDOWS
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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:[~2019-08-07 2:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 15:20 Michael Haubenwallner
2019-08-06 15:41 ` Corinna Vinschen
2019-08-06 15:47 ` Bill Stewart
2019-08-06 15:53 ` Corinna Vinschen
2019-08-06 16:10 ` Bill Stewart
2019-08-06 16:25 ` Corinna Vinschen
2019-08-06 17:08 ` Bill Stewart
2019-08-07 2:33 ` Brian Inglis [this message]
2019-08-07 11:09 ` Michael Haubenwallner
2019-08-07 11:19 ` Corinna Vinschen
2019-08-07 12:41 ` Michael Haubenwallner
2019-08-07 14:31 ` Corinna Vinschen
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=0f9d219c-a9ae-237a-afcf-9dcc5a13bc01@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).