This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Nov 30 07:43, James E. King III wrote: > On Fri, Nov 30, 2018 at 7:23 AM Corinna Vinschen > <corinna-cygwin@cygwin.com> wrote: > > > > On Nov 29 17:38, James E. King III wrote: > > > On Thu, Nov 29, 2018 at 5:18 AM Corinna Vinschen > > > > I created a patch and uploaded new developer snapshots to > > > > https://cygwin.com/snapshots/ Please give them a try. > > > > > > This fixed the issue for me. What's the best way to detect cygwin > > > with this support? > > > > This will show up in version 2.12.0(*) so checking the release field > > from uname(2) should do the trick. > > Is there a programmatic way to check this without having to parse a > bunch of char[20] from utsname.h? How would you do this on Linux? Corinna -- Corinna Vinschen Cygwin Maintainer
Attachment:
signature.asc
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |