From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: w32api.h
Date: Tue, 14 Dec 2021 19:15:30 +0100 [thread overview]
Message-ID: <b2b8afab-310c-ce4b-f13b-b8012a2cde33@gmail.com> (raw)
In-Reply-To: <023001d7f112$6bfb0fc0$43f12f40$@gmx.com>
On 14.12.2021 18:45, robhickey@gmx.com wrote:
> Hi Cygwin,
>
>
>
> I'm compiling a non Cygwin code using ./config, make, make install.
>
>
>
> The make output says /include/w32api file or directory not found.
probably you can at configure stage set the
prefix of include directory as "/usr"
> I'm guessing /include is not a standard directory, so I copied the
> /usr/include/w32api to /include/w32api/, the warning goes way.
a simple link was also probably enough
mkdir /include
ln -s /usr/include/w32api to /include/w32api
but checking the prefix is better.
> I also notice that w32api.h defines every version of windows but stops at
> windows8.
>
> #define WindowsVista 0x0600
>
> #define Windows7 0x0601
>
> #define Windows8 0x0602
>
>
> Is it permissible to add
>
> #define windows10 0X0603
what is your scope ?
If the original headers are not using that definition
adding it make no difference
By the way
https://docs.microsoft.com/en-us/cpp/porting/modifying-winver-and-win32-winnt?view=msvc-170
reports a different value:
----------------------------------------------------------
#define _WIN32_WINNT_WIN7 0x0601 // Windows 7
#define _WIN32_WINNT_WIN8 0x0602 // Windows 8
#define _WIN32_WINNT_WINBLUE 0x0603 // Windows 8.1
#define _WIN32_WINNT_WINTHRESHOLD 0x0A00 // Windows 10
#define _WIN32_WINNT_WIN10 0x0A00 // Windows 10
----------------------------------------------------------
Regards
Marco
next prev parent reply other threads:[~2021-12-14 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 17:45 w32api.h robhickey
2021-12-14 18:15 ` Marco Atzeri [this message]
2021-12-14 21:36 ` w32api.h Hans-Bernhard Bröker
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=b2b8afab-310c-ce4b-f13b-b8012a2cde33@gmail.com \
--to=marco.atzeri@gmail.com \
--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).