public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Csaba Raduly <rcsaba@gmail.com>
To: Paul Moore <p.f.moore@gmail.com>
Cc: cygwin list <cygwin@cygwin.com>
Subject: Re: Can I find where cygwin is installed (for automation purposes)
Date: Wed, 15 Apr 2020 12:51:53 +0200	[thread overview]
Message-ID: <CAEhDDbBUcV3HmoCwraH7pY5c19Sj=mRZ6ofCOZL3T9qx_4qq6w@mail.gmail.com> (raw)
In-Reply-To: <CACac1F9BvE0nqGru8=NxA7pc=6VPF_sokUPS94Wr1NfRQeLN5w@mail.gmail.com>

Hi Paul,

On Wed, Apr 15, 2020 at 12:30 PM Paul Moore via Cygwin <cygwin@cygwin.com>
wrote:

> I'm trying to write an automation script that works on a number of
> machines. I know that on all machines Cygwin will be installed, but I
> cannot guarantee that (1) it will be in the same location on each PC,
> or (2) that it will be in PATH.
>
> There's HKCU\Software\Cygwin\Installations, but that seems to use \??
> prefixes on the PATH, which I'm not sure how to interpret
>
On my machine, I have a

HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup

key, which contains a string value named "rootdir" with the date
"C:\cygwin64".

Csaba

-- 
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformant
way
to get the wrong information: this is what you want. - Scott Meyers
(C++TDaWYK)

  reply	other threads:[~2020-04-15 10:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15 10:29 Paul Moore
2020-04-15 10:51 ` Csaba Raduly [this message]
2020-04-15 12:42   ` Thomas Wolff
2020-04-15 13:30     ` Paul Moore
2020-04-15 10:53 ` Csaba Ráduly
2020-04-15 13:29   ` Paul Moore
2020-04-15 15:53     ` Marco Atzeri
2020-04-15 18:10       ` Paul Moore
2020-04-15 18:30         ` René Berber
2020-04-15 18:39           ` Paul Moore
2020-04-15 20:49             ` René Berber

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='CAEhDDbBUcV3HmoCwraH7pY5c19Sj=mRZ6ofCOZL3T9qx_4qq6w@mail.gmail.com' \
    --to=rcsaba@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=p.f.moore@gmail.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).