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:
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.
Calling:
in
CMakeLists.txt
will add-fobjc-runtime=gnustep-2.0
as a compile option for all builds. The legacy tests will attempt to targetgnustep-1.7
by calling: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.