Re[2]: wxUSE_ACCESSIBILITY and clang-cl

On Tue, 12 Dec 2023 15:54:26 +0100 Gisle Vanem wrote:

GV> >   But how exactly do you use it? Do you still use nmake?
GV> 
GV> No. For the FreeDV-GUI project, I use a hacked-up GNU-makefile with the
GV> same wxFLAGS for MSVC and clang-cl.

 Oh. I'm afraid you're really on your own then because I have no idea which
setup.h are you generating/using then.

GV> I did not use configure for wxWidgets (or anything else, loathe it).

 Far from me to tell people what to do, but the fact is that we already
have too many _supported_ build methods (nmake, configure, CMake, project
files for MSVS). If you're using something else, it's up to you to look at
how the existing ones work and mimic them. Notably you need to predefine
the expected preprocessor constants.

GV> > but you may retry by passing --enable-accessibility
GV> 
GV> What does this flag translate to in NMake terms?

 There is no such flag at make level, it's a preprocessor flag which should
be defined in setup.h.

GV> I do not see a "#define wxMSW 1" anywhere. Caste to explain?

 You should predefine __WXMSW__ when building under Windows. It's not the
only symbol you need, please refer to the building instructions in the
manual if you really, really don't want to use any of the supported build
methods.

 Good luck,
VZ

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

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

iF0EABECAB0WIQQx+vLQdOwioQqkxtoG6kHeT2wehgUCZXh1OwAKCRAG6kHeT2we
hpC5AJ4spzSRweMW7C2sGFJTvjba54gMmgCfXs30mVScOmh/qrjT5AYHOGkQCWQ=
=ChcN
-----END PGP SIGNATURE-----