Skip to content

Conversation

@etcwilde
Copy link
Member

@etcwilde etcwilde commented Oct 9, 2025

We should only be pulling in the modulemap file from the source directory when compiling against the build directory, not the installed location. The module-map-file override should only be applied as part of the build interface, not install interface. In cases where the sources are checked out and we are compiling a project against the install interface, we will run into a situation where the compiler sees the modulemap from both the installed location and the source directory and will complain.

We should only be pulling in the modulemap file from the source
directory when compiling against the build directory, not the installed
location. The module-map-file override should only be applied as part of
the build interface, not install interface. In cases where the sources
are checked out and we are compiling a project against the install
interface, we will run into a situation where the compiler sees the
modulemap from both the installed location and the source directory and
will complain.
@etcwilde etcwilde merged commit 122f088 into swiftlang:main Oct 9, 2025
23 checks passed
@etcwilde etcwilde deleted the ewilde/override-modulemap-in-build-dir branch October 9, 2025 22:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants