[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lmi] [lmi-commits] master aee9f4d 10/11: For cygwin, add msw system
From: |
Greg Chicares |
Subject: |
Re: [lmi] [lmi-commits] master aee9f4d 10/11: For cygwin, add msw system directory to minimal path |
Date: |
Wed, 8 May 2019 19:43:16 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 |
On 2019-05-08 19:02, Vadim Zeitlin wrote:
> On Wed, 8 May 2019 13:23:25 -0400 (EDT) Greg Chicares <address@hidden> wrote:
[...]
> GC> +case "$lmi_build_type" in
> GC> + (*-*-cygwin*)
> GC> + minimal_path="$minimal_path:/cygdrive/c/Windows/system32"
> GC> + ;;
> GC> +esac
>
> This is probably never going to be a concern in practice,
Until we move to 64-bit cygwin and demons fly out our noses.
> but the above
> doesn't work on my machine as the path c:\Windows\system32 doesn't exist
> here (the OS is installed on a different drive, mostly in order to detect
> broken programs that hardcode c: as the OS drive).
>
> Using `cygpath -u "$WINDIR\\system32"` (or the same thing with
> $SYSTEMROOT) should work anywhere and wouldn't require much more work
> however.
I no longer know this msw stuff; I was thinking
cygpath -u "%windir%\SysWOW64;%windir%\System32"
or something like that, but that's just a shot in the dark, and I
don't know whether 'cygpath' handles multiple semicolon-separated
directories correctly ('winepath' definitely does not), or "%...%"
names at all (I guess $WINDIR is better because cygwin presumably
puts that in the environment).
If you would give me the magic string to insert here:
- minimal_path="$minimal_path:/cygdrive/c/Windows/system32"
+ minimal_path="$minimal_path:...just add magic..."
then I'd be glad to apply it.