This patch with using 0xA00 for IE is ok for me, too.
Thanks,
Kai
2015-10-06 17:39 GMT+02:00 Jean-Baptiste Kempf :
> On 06 Oct, Jacek Caban wrote :
>> We support building for win10 and we even already have some of its new
>> API declarations. Also, Mozilla needs it for its configure to work prope
On 06 Oct, Jacek Caban wrote :
> We support building for win10 and we even already have some of its new
> API declarations. Also, Mozilla needs it for its configure to work properly.
OK for me.
With my kindest regards,
--
Jean-Baptiste Kempf
http://www.jbkempf.com/ - +33 672 704 734
Sent from my
TBH, I was wandering about the same thing. Maybe it would be good idea
to change it to A00 for PSDK compatibility. AFAIK there are no plans for
more IEs from Microsoft...
Thanks for review,
Jacek
On 10/06/15 17:42, David Grayson wrote:
> The lines you changed look good to me. However, I don't un
The lines you changed look good to me. However, I don't understand
why _WIN32_IE_MAXVER is defined as 0xb00 instead of 0xA00, but it has
been that way since you added the file.
--David
On Tue, Oct 6, 2015 at 8:30 AM, Jacek Caban wrote:
> We support building for win10 and we even already have so
We support building for win10 and we even already have some of its new
API declarations. Also, Mozilla needs it for its configure to work properly.
Please review.
---
mingw-w64-headers/include/winsdkver.h | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/mingw-w64-h
