-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transitive framework import causes release build fail #569
Comments
I have a fix in mind and will validate it and submit a PR. |
I guess we should re-open this give #715? Or should we track in a diff issue instead? |
I'm adding a proper test to catch this regression via #713. |
Thanks for adding the tests. I'll take a look at this again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If we have an
apple_framework
transitively depends onframework_import
, the build will fail with--compilation_mode=opt
. In the following code, Module2 is not able to build. The same error will occur with--features=swift.cacheable_swiftmodules
.With either
--compilation_mode=opt
or--features=swift.cacheable_swiftmodules
, swift_library will stop passing-serialize-debugging-options
to swiftc. Unfortunately, it seems we are relying on the search paths embedded in .swiftmodule for transitive framework imports. We should explicitly provide those search paths to the compiler.I have sample repro code and steps here.
The text was updated successfully, but these errors were encountered: