Skip to content

SDK imports metadata #75

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

Merged
merged 3 commits into from
Feb 7, 2025
Merged

SDK imports metadata #75

merged 3 commits into from
Feb 7, 2025

Conversation

neonichu
Copy link
Collaborator

@neonichu neonichu commented Feb 3, 2025

This provides new metadata during builds:

  • Use the new -sdk_imports linker option when appropriate and provide a post-processed version of it as a resource in each bundle.
  • For each codeless bundle, "stamp" its Info.plist with any clients, this allows finding the library associated with a particular codeless bundle.

Both behaviors are enabled by the ENABLE_SDK_IMPORTS build setting which defaults to the inverse of ASSETCATALOG_COMPILER_SKIP_APP_STORE_DEPLOYMENT.

@neonichu
Copy link
Collaborator Author

neonichu commented Feb 3, 2025

@swift-ci test

@neonichu
Copy link
Collaborator Author

neonichu commented Feb 4, 2025

@swift-ci test macOS

1 similar comment
@jakepetroules
Copy link
Collaborator

@swift-ci test macOS

@neonichu
Copy link
Collaborator Author

neonichu commented Feb 4, 2025

The optionality of -sdk_imports is fully there right now, I'll have to update this PR.

@neonichu neonichu force-pushed the bbuegling/sdk-imports branch from 7b6ee62 to 5ef221c Compare February 5, 2025 23:44
@neonichu neonichu requested a review from mhrawdon as a code owner February 5, 2025 23:44
@neonichu
Copy link
Collaborator Author

neonichu commented Feb 5, 2025

@swift-ci test macOS

neonichu and others added 3 commits February 7, 2025 11:35
This provides new metadata during builds:
- Use the new `-sdk_imports` linker option when appropriate and provide a post-processed version of it as a resource in each bundle.
- For each codeless bundle, "stamp" its Info.plist with any clients, this allows finding the library associated with a particular codeless bundle.

Both behaviors are enabled by the `ENABLE_SDK_IMPORTS` build setting which defaults to the inverse of `ASSETCATALOG_COMPILER_SKIP_APP_STORE_DEPLOYMENT`.
This provides new metadata during builds:
- Use the new `-sdk_imports` linker option when appropriate and provide a post-processed version of it as a resource in each bundle.
- For each codeless bundle, "stamp" its Info.plist with any clients, this allows finding the library associated with a particular codeless bundle.

Both behaviors are enabled by the `ENABLE_SDK_IMPORTS` build setting which defaults to the inverse of `ASSETCATALOG_COMPILER_SKIP_APP_STORE_DEPLOYMENT`.
@neonichu neonichu force-pushed the bbuegling/sdk-imports branch from 5ef221c to 165e265 Compare February 7, 2025 19:35
@neonichu
Copy link
Collaborator Author

neonichu commented Feb 7, 2025

Refactored things a little bit so that we can also check whether the linker supports the SDK imports feature in tests.

@neonichu
Copy link
Collaborator Author

neonichu commented Feb 7, 2025

@swift-ci test macOS

@neonichu neonichu merged commit da67fc7 into main Feb 7, 2025
1 check passed
@neonichu neonichu deleted the bbuegling/sdk-imports branch February 7, 2025 22:26
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