Am Montag, 7. März 2016 21:02:39 UTC+1 schrieb Ehsan Akhgari:
> On 2016-02-11 2:38 AM, w...@gmx.net wrote:
> > Am Sonntag, 7. Februar 2016 00:25:25 UTC+1 schrieb Ehsan Akhgari:
> >> On 2016-02-05 1:30 PM, a...@gmx.net wrote:
> >>> Am Donnerstag, 4. Februar 2016 16:35:58 UTC+1 schrieb wolf....@gmx.net:
> >>>> I try to do a cross compile on linux centos 64bit for windows 64 bit. I
> >>>> tried as written here
> >>>> "https://developer.mozilla.org/en-US/docs/Cross_Compile_Mozilla_for_Mingw32";.
> >>>>
> >>>>
> >>>> but I get always this error and don`t know how to fix it.
> >>>>
> >>>> configure: error: You are targeting Windows version 0x06030000, but
> >>>> your SDK only supports up to version # 1 "conftest.h"0000. Install and
> >>>> use an updated SDK, or target a lower version using
> >>>> --with-windows-version. Alternatively, try running the Windows SDK
> >>>> Configuration Tool and selecting a newer SDK. See
> >>>> https://developer.mozilla.org/En/Windows_SDK_versions for more details
> >>>> on fixing this.
> >>>
> >>> I`ve installed the mingw out of the mingw git repository, I use the cross
> >>> compile tutorial. Mingw should be the latest available.
> >>> How can I check this? Which version is the recommended one?
> >>>
> >>> this is the header file:
> >>>
> >>> /**
> >>> * This file is part of the mingw-w64 runtime package.
> >>> * No warranty is given; refer to the file DISCLAIMER within this package.
> >>> */
> >>>
> >>> #ifndef _INC_WINSDKVER
> >>> #define _INC_WINSDKVER
> >>>
> >>> #include <winapifamily.h>
> >>>
> >>> #if WINAPI_FAMILY_PARTITION(WINAPI_PARTITION_DESKTOP)
> >>>
> >>> #define _WIN32_MAXVER 0x0A00
> >>> #define _WIN32_WINDOWS_MAXVER 0x0A00
> >>> #define NTDDI_MAXVER 0x0A00
> >>> #define _WIN32_IE_MAXVER 0x0A00
> >>> #define _WIN32_WINNT_MAXVER 0x0A00
> >>> #define WINVER_MAXVER 0x0A00
> >>>
> >>> #endif
> >>> #endif
> >>
> >> That file looks to be correct.
> >>
> >> What do you get if you run:
> >>
> >> echo '#include <winsdkver.h>' > test.c
> >> echo 'WINVER_MAXVER' >> test.c
> >> mingw-cpp test.c
> >>
> >> where mingw-cpp is the cpp program in mingw.
> >
> >
> > I`m getting the following result:
> >
> > [root@ tmp]# i686-w64-mingw32-cpp test.c -I
> > /usr/local/i686-w64-mingw32/include/
> > # 1 "test.c"
> > # 1 "<built-in>"
> > # 1 "<command-line>"
> > # 1 "test.c"
> > # 1 "/usr/local/i686-w64-mingw32/include/winsdkver.h" 1
> > # 9 "/usr/local/i686-w64-mingw32/include/winsdkver.h"
> > # 1 "/usr/local/i686-w64-mingw32/include/winapifamily.h" 1
> > # 10 "/usr/local/i686-w64-mingw32/include/winsdkver.h" 2
> > # 2 "test.c" 2
> > 0x0A00
>
> OK, that is what I would expect, but our build system doesn't pass in
> that -I flag that you're using. What happens if you remove that?
[root@ tmp]# i686-w64-mingw32-cpp test.c
# 1 "test.c"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "test.c"
test.c:1:23: fatal error: winsdkver.h: No such file or directory
#include <winsdkver.h>
^
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds
