Re: Problem using wx headers in XCode

Hi Tim

Two thoughts,

1)

I’m using xcconfig Files from the Xcode projects in wx directly, it is important to define WXROOT to the folder containing the wx installatiion, then these should work, the toplevel files are


  *   wxdebug.xcconfig or wxrelease.xcconfig
  *   wxcocoa.xcconfig

then there are the wxcocoa_xxxx.xcconfig files for other use cases, they include wxcocoa.xcconfig first and then define some additional elements

2)

in the samples  we are not using angle bracket includes, so it would not be SYSTEM_HEADER_SEARCH_PATHS, but USER_HEADER_SEARCH_PATHS

HTH,

Stefan

Von: <[email protected]> im Auftrag von Tim Burgess <[email protected]>
Antworten an: "[email protected]" <[email protected]>
Datum: Mittwoch, 14. Januar 2026 um 13:26
An: wx-users <[email protected]>
Betreff: Re: Problem using wx headers in XCode

OK, thanks.

I’ve now included a recursive path that *should* find setup.h, but still no joy.

I’ve just found an article that describes similar issues, though some time ago, that suggests that I define a custom build parameter, USE_HEADERMAP, with a value of NO, so now I have to try and figure out where I can set this without having to tackle the Xcode UI (sigh).

Thanks for the assist.

Tim



On 14 Jan 2026, at 11:38, Maarten Bent <[email protected]> wrote:

Hi Tim,

I can't help with Xcode specific variables, but wxWidgets needs two include paths. One for the headers, and one for setup.h.
If wx.h and other headers are found the headers seem to be included correctly.
setup.h is in the lib folder, and you already include $(HOME)/lib/wx/include/osx_cocoa-unicode-3.1
This is folder for wxWidgets 3.1. Are you using this version? The latest versions on vcpkg are 3.3 and 3.2 stable. Maybe you need to update this path to have the correct version?
And I'm not sure about this one, but you might need to include the path with setup.h before including the general wx headers.

Greetings,
Maarten


On 14 Jan 2026 12:16, Tim Burgess wrote:
Hi,

I’m revisiting this topic, as I still haven’t achieved a resolution.

I have wxWidgets installed and built via VCPKG on my Mac Taho computer, with the headers resident in:

~/vcpkg/installed/x64-osx/include

I have other libraries, such as Boost installed using the same path and triplet.

I am blind and Xcode’s Build Settings UI is horrendous to use with a screen reader, so I’ve been modifying my project’s settings (Base.xcconfig) file in a text editor. My header path is defined as:

SYSTEM_HEADER_SEARCH_PATHS = "$(HOME)/vcpkg/installed/x64-osx/include/**"
// HEADER_SEARCH_PATHS = "$(WXROOT)/src/tiff/libtiff"
// USER_HEADER_SEARCH_PATHS = "$(WXROOT)/include" "$(WXROOT)/build/osx/setup/$(WXTOOLKIT)/include" "$(WXROOT)/src/jpeg" "$(WXROOT)/src/png" "$(WXROOT)/src/regex" "$(WXROOT)/src/expat/lib" "$(WXROOT)/src/tiff/libtiff" "$(WXROOT)/src/stc/scintilla/src" "$(WXROOT)/src/stc/scintilla/include"
HEADER_SEARCH_PATHS = "$(HOME)/vcpkg/installed/x64-osx/include/**" $(HOME)/include $(HOME)/include/wx-$(DYLIB_COMPATIBILITY_VERSION) $(HOME)/lib/wx/include/osx_cocoa-unicode-3.1 /usr/include/libxml2
ALWAYS_SEARCH_USER_PATHS = NO

I have tried using the path with and without the quotes – the path contains no spaces, so they shouldn’t be necessary. My understanding is that adding ./** to the end of the path indicates that the path should be scanned recursively, which is what I want.

If I don’t specify the path pointing to my VCPKG installation, my build fails to find wx.h, which is what I expect. Adding this path reports no errors relating to wx.h, so I’m assuming that the file is now being found. However, the build fails with too many errors relating to WX types and methods not being defined, so I’m assuming that other headers are still not being found. Making these changes in the Base.xcconfig and getting differing results gives me confidence that I’m editing the correct settings file.

Can anybody offer me any advice, please?

Best wishes.

Tim


--
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]<mailto:[email protected]>.
To view this discussion visit https://groups.google.com/d/msgid/wx-users/000a01dc8547%243d4c1200%24b7e43600%24%40raisedbar.net<https://groups.google.com/d/msgid/wx-users/000a01dc8547%243d4c1200%24b7e43600%24%40raisedbar.net?utm_medium=email&utm_source=footer>.


--
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]<mailto:[email protected]>.
To view this discussion visit https://groups.google.com/d/msgid/wx-users/3fa955e2-099c-43af-a1a5-08ab1ad91ac6%40gmail.com<https://groups.google.com/d/msgid/wx-users/3fa955e2-099c-43af-a1a5-08ab1ad91ac6%40gmail.com?utm_medium=email&utm_source=footer>.

--
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]<mailto:[email protected]>.
To view this discussion visit https://groups.google.com/d/msgid/wx-users/0DFA6E68-AD46-44AA-8B89-A5380170512C%40gmail.com<https://groups.google.com/d/msgid/wx-users/0DFA6E68-AD46-44AA-8B89-A5380170512C%40gmail.com?utm_medium=email&utm_source=footer>.

-- 
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 visit https://groups.google.com/d/msgid/wx-users/51BAED57-9A96-42AE-9960-AC60573F641C%40advancedconcepts.ch.