Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't set -fobjc-runtime=gnustep-2.0 as a global flag #255

Merged
merged 1 commit into from
Dec 31, 2023

Conversation

qmfrederik
Copy link
Collaborator

Calling:

add_compile_options("$<$<OR:$<COMPILE_LANGUAGE:OBJC>,$<COMPILE_LANGUAGE:OBJCXX>>:-Wno-deprecated-objc-isa-usage;-Wno-objc-root-class;-fobjc-runtime=gnustep-2.0>$<$<COMPILE_LANGUAGE:C>:-Xclang;-fexceptions>")

in CMakeLists.txt will add -fobjc-runtime=gnustep-2.0 as a compile option for all builds. The legacy tests will attempt to target gnustep-1.7 by calling:

addtest_flags("${TEST}_legacy" "-O0 -fobjc-runtime=gnustep-1.7 -UNDEBUG" "${TEST_SOURCE}")

which will result in the same flag being defined twice (-fobjc-runtime=gnustep-2.0 -fobjc-runtime=gnustep-1.7). In my setup, that resulted in clang targeting the 2.0 runtime, making the legacy tests invalid.

@qmfrederik qmfrederik changed the title Don't -fobjc-runtime=gnustep-2.0 as a global flag Don't set -fobjc-runtime=gnustep-2.0 as a global flag Dec 31, 2023
@davidchisnall
Copy link
Member

Interesting. This should be a last-version-wins flag in clang.

@davidchisnall
Copy link
Member

Looks like FreeBSD CI is failing because the versions that we’re testing on are EOL.

@davidchisnall
Copy link
Member

[ Updating the branch to pick up fixes to the CI scripts. ]

The legacy tests will override this flag.
@davidchisnall davidchisnall merged commit 0771ddf into gnustep:master Dec 31, 2023
41 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants