Ensuring build setting consistency across macOS versions using .xcconfig

To establish a repeatable development environment in Xcode, teams often move environment-specific variables out of the .xcodeproj file and into .xcconfig files. This approach aims to decouple the project configuration from the local machine state.

While Swift Package Manager (SPM) handles dependency resolution consistently, there is uncertainty regarding how Xcode manages derived data paths and cached build artifacts when a project is migrated between different macOS versions or runtime images, such as those used in Xcode Cloud.

Which mechanisms are available to ensure that .xcconfig definitions remain portable and do not inadvertently inherit machine-specific absolute paths during the build process? Does Xcode provide a native way to standardize the derived data location across disparate macOS environments to prevent cache inconsistencies?