Re: wx-3.3.3 cross-compilation error

Vadim Zeitlin <[email protected]> Thu, 9 Jul 2026 20:43:43 +0200
Newsgroups gmane.comp.lib.wxwindows.general
Message-ID <[email protected]>
--8323329-2044897763-1783622623=:1435922
Content-Type: TEXT/PLAIN; CHARSET=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Disposition: INLINE

On Thu, 9 Jul 2026 10:17:47 -0700 (PDT) =D0=A1=D0=B5=D1=80=D0=B3=D0=B5=D0=
=B9 =D0=9A=D0=BE=D0=BD=D1=8B=D0=B3=D0=B8=D0=BD wrote:

=D0=A1=D0=9A> Everything works fine when compiling for Windows using 32-bit=
 MinGW. A=20
=D0=A1=D0=9A> compilation error occurs when using the cross-compiler (insta=
lled on Debian=20
=D0=A1=D0=9A> 12.6). I am configuring wxWidgets using the following lines

 What is the version of your cross-compiler and the SDK being used? It
looks like they are somehow not compatible with each other...

=D0=A1=D0=9A> Here is a list of errors.  What am I doing wrong?=20
[...unrelated warnings snipped...]
=D0=A1=D0=9A> /usr/share/mingw-w64/include/uiautomationcoreapi.h:69:128: er=
ror: expected=20
=D0=A1=D0=9A> =E2=80=98,=E2=80=99 or =E2=80=98...=E2=80=99 before =E2=80=98=
new=E2=80=99
=D0=A1=D0=9A>    69 | HRESULT WINAPI=20
=D0=A1=D0=9A> UiaRaiseAutomationPropertyChangedEvent(IRawElementProviderSim=
ple *provider,=20
=D0=A1=D0=9A> PROPERTYID id, VARIANT old, VARIANT new);

 This looks like an error in the SDK, "new" is a keyword in C++ and
shouldn't be used as identifier name. I don't have this in my (Debian 13)
version, so it has been already fixed, but we possibly could work around
this by the usual #define-new-as-something-else-before-including-the-header
(and #undef it after) trick. Could you try doing it?

=D0=A1=D0=9A> ../src/msw/taskdlg.cpp:121:25: error: =E2=80=98IUIAutomationE=
lement=E2=80=99 was not=20
=D0=A1=D0=9A> declared in this scope; did you mean =E2=80=98LIBID_UIAutomat=
ionClient=E2=80=99?

 However if your /usr/share/mingw-w64/include/uiautomationclient.h really
doesn't declare IUIAutomationElement (i.e. it's not some weird consequence
of the error above), there is no chance that this code will compile
anyhow... We're going to need a configure/CMake test and an option to
disable it in this case, please open an issue if this is indeed the case so
that we fix it in 3.3.4/3.4.0.

 Thanks,
VZ

--=20
TT-Solutions: wxWidgets consultancy and technical support
               https://www.tt-solutions.com/

--8323329-2044897763-1783622623=:1435922
Content-Type: APPLICATION/PGP-SIGNATURE

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQQx+vLQdOwioQqkxtoG6kHeT2wehgUCak/r3wAKCRAG6kHeT2we
htMDAKCkk8sjxrOcvM1RKIz3/Ytc84pnggCfWOB1mF0cmego4ds3zvMd0azrJm8=
=7g7Q
-----END PGP SIGNATURE-----

--8323329-2044897763-1783622623=:1435922--