Opened 2 years ago
Last modified 21 months ago
#65983 assigned defect
yabai @5.0.1: error: property 'safeAreaInsets' not found on object of type 'NSScreen *'
Reported by: | secsaba (Csaba Endre Simon) | Owned by: | macports@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.2 |
Keywords: | monterey | Cc: | |
Port: | yabai |
Description
The "sudo port build" fails for the latest yabai port. However a "cd work/yabai-5.0.1; sudo make" will work.
I compared the commands executed by "port build" and "make". The difference is that "port build" will add "-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk" to the clang argument that will results in the following error:
In file included from src/manifest.m:71: src/workspace.m:109:31: error: property 'safeAreaInsets' not found on object of type 'NSScreen *' return screen.safeAreaInsets.top; ^ 1 error generated.
Without the "-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk" argument to clang the program compiles fine.
In what step of "port build" is this injected and how can be fixed?
Change History (3)
comment:1 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 21 months ago by ryandesign (Ryan Carsten Schmidt)
Cc: | macports@… removed |
---|---|
Owner: | set to macports@… |
Status: | new → assigned |
Summary: | yabai @ 5.0.1 Build failure → yabai @5.0.1: error: property 'safeAreaInsets' not found on object of type 'NSScreen *' |
Do you still see this problem with 5.0.3?
comment:3 Changed 21 months ago by secsaba (Csaba Endre Simon)
No idea. I am not using anymore macports.
Note: See
TracTickets for help on using
tickets.
It doesn't happen in a port step. MacPorts base automatically adds SDK paths to the appropriate environment variables when it is required so to do (on OS/Xcode versions that do not have /usr/include).