Xcode 26.6 errors

ImJimmi · September 9, 2026, 8:28pm

After upgrading to the latest Xcode I’m suddenly seeing warnings from 3rd party modules (and with -Werror these fail the build). This seems to be due to this “re-exporting” that means the targets lose their SYSTEM flag:

github.com/juce-framework/JUCE

extras/Build/CMake/JUCEUtils.cmake

72782788c


      
                  add_executable(${target_name} MACOSX_BUNDLE)

              endif()

          else()

              add_library(${target_name} MODULE)

          endif()

          

          if((CMAKE_SYSTEM_NAME STREQUAL "Linux") OR (CMAKE_SYSTEM_NAME MATCHES ".*BSD"))

              target_link_options(${target_name} PRIVATE "-Wl,--no-undefined")

          endif()

          

          # We re-export the shared code's private include dirs, because the wrapper targets need to

          # see the module headers. We don't just link publicly, because that would introduce

          # conflicting macro definitions.

          target_include_directories(${target_name} PRIVATE

              $<TARGET_PROPERTY:${shared_code_target},INCLUDE_DIRECTORIES>)

          

          if("${kind};${CMAKE_SYSTEM_NAME}" STREQUAL "AUv3;Darwin")

              target_include_directories(${target_name}_Framework PRIVATE

                  $<TARGET_PROPERTY:${shared_code_target},INCLUDE_DIRECTORIES>)

          

              target_link_libraries(${target_name}_Framework PRIVATE

Explicitly adding the -isystem flag back to the third-party modules after calling juce_add_plugin() fixes the issue.

attila · September 10, 2026, 3:25pm

I can’t reproduce an issue here that’s relevant to Xcode 26.6 or the JUCEUtils.cmake section you linked.

I tried to come up with a simple project that links against a placeholder module with deliberate warnings, and then marked it as a SYSTEM dependency.

juce_add_module(modules/my_placeholder_module)
set_target_properties(my_placeholder_module PROPERTIES SYSTEM TRUE)

This compiles for me with both Xcode 26.6 (17F113) and an earlier version, or fails with both when omitting the SYSTEM property.

Is that how you’re using your dependency?

Also, I don’t understand how the wrapper target comes to depend on a 3rd party module, so that the above re-exporting is relevant. Can you provide a minimal project repro?

Topic		Replies	Views
XCode Modules Linking Issues MacOSX and iOS	1	375	November 29, 2021
Problem create repertory General JUCE discussion	6	494	December 1, 2023
How to make a xcode project without projucer? General JUCE discussion	2	1581	November 9, 2016
Xcode 10 vs JUCE MacOSX and iOS	5	1613	December 10, 2018
Warnings in Juce's Objective C under XCode 4? General JUCE discussion	5	530	August 26, 2013

Xcode 26.6 errors

Related topics