Re: wxUSE_ACCESSIBILITY and clang-cl
Gisle Vanem <[email protected]>
| Newsgroups | gmane.comp.lib.wxwindows.general |
|---|---|
| Message-ID | <CAOKnH6O+MFvJvGs5+rzdn4kbsD_GRjaWrv7seTEn0wFe5zgDHQ@mail.gmail.com> |
> But how exactly do you use it? Do you still use nmake? No. For the FreeDV-GUI project, I use a hacked-up GNU-makefile with the same wxFLAGS for MSVC and clang-cl. > I suspect you're actually using configure now and this option has somehow > ended up being as 0 in the setup.h I did not use configure for wxWidgets (or anything else, loathe it). > but you may retry by passing --enable-accessibility What does this flag translate to in NMake terms? I suspect there's no such flag since 'wxUSE_ACCESSIBILITY' default to '1' for MSW. But I fail to see what MSW (or is it wxMSW?) is for clang-cl? I do not see a "#define wxMSW 1" anywhere. Caste to explain? tir. 12. des. 2023 kl. 15:37 skrev Vadim Zeitlin <[email protected]>: > On Tue, 12 Dec 2023 05:45:52 -0800 (PST) Gisle Vanem wrote: > > GV> Hi list, my 1st post here. > > Hi and welcome to the list! > > GV> So I'm forced to use clang-cl. > > But how exactly do you use it? Do you still use nmake? > > GV> This works for all files in this project. > GV> Except that these files: > GV> > https://github.com/drowe67/freedv-gui/blob/master/src/gui/util/LabelOverrideAccessible.cpp > GV> > https://github.com/drowe67/freedv-gui/blob/master/src/gui/util/NameOverrideAccessible.cpp > GV> > GV> pre-processes to almost nothing! Studying the preprocessed output > GV> (with clang-cl -E -C -d1PP), I see that it contains: > GV> > GV> // Recommended setting (at present): 1 (MSW-only) > GV> #define wxUSE_ACCESSIBILITY 0 > GV> > GV> Why and how could I prevent that? > > I suspect you're actually using configure now and this option has somehow > ended up being as 0 in the setup.h file generated by configure. It's not > clear to me why/how this happened (please check your config.log to try to > find more details), but you may retry by passing --enable-accessibility > option explicitly to configure and check if it helps (it actually should > _not_, because accessibility support should be enabled by default when > using wxMSW, but it doesn't cost much to try). > > If this doesn't answer your question, you really need to provide more > details about what you're doing, i.e. at the very least > > - Your wxWidgets version. > - How exactly do you build it. > > Regards, > VZ > > -- > TT-Solutions: wxWidgets consultancy and technical support > https://www.tt-solutions.com/ > -- Please read https://www.wxwidgets.org/support/mlhowto.htm before posting. --- You received this message because you are subscribed to the Google Groups "wx-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/wx-users/CAOKnH6O%2BMFvJvGs5%2Brzdn4kbsD_GRjaWrv7seTEn0wFe5zgDHQ%40mail.gmail.com.