[#bundle support] Generate internal bundle access class for mergeable libraries #599
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mergeable libraries use a re-exported library in Debug mode and merge into the client in Release builds.
In both cases, we cannot simply rely on the
#dsohandle
for bundle lookup as#bundle
does by default.Instead,
dyld
includes special bundle loading hooks that allowsBundleForClass
to return the current resource bundle at runtime.In this PR, we have mergeable libraries codegen a simple
__BundleLookupHelper
class and define theSWIFT_BUNDLE_LOOKUP_HELPER_AVAILABLE
compilation condition.The implementation of
#bundle
in Foundation will then lookupBundle(for: __BundleLookupHelper.self)
under this condition.This solution intentional avoids the need for generated code to
import Foundation
.This should allow
#bundle
to work correctly for mergeable libraries.