XCode 16 Explicitly Built Modules Not Affecting SPM Package

Hi all,

XCode 16 introduced a new build system that seeks to improve build times and reliability. Following the WWDC 24 talk “Demystify Explicitly Built Modules”, I installed XCode 16 Beta 1 and opted in to the new build system for my project by enabling the Explicitly Built Modules build setting for all targets (just to be sure).

However, when inspecting the build logs, it seems that the new system is not taking effect as, for example, there are no Scanning Dependency tasks.

I have already tried cleaning the build folder and derived data, restarting XCode, and restarting my computer.

For reference, my app’s code is wrapped in an SPM package, very similar to the set-up used in the isowords project. I was expecting that the new build system would explicitly build the modules within the package.

Could anyone clarify if what I’m observing is the expected behaviour, i.e the new build system does not apply to modules in an SPM package? Otherwise, are there any steps I can take to get the new build system to take effect?

Thank you!

I have the same question. We used local SPM packages for modulation.

XCode 16 Explicitly Built Modules Not Affecting SPM Package
 
 
Q