Prepare Preview dependencies without selected products - #3365
Draft
karim-alweheshy wants to merge 2 commits into
Draft
karim-alweheshy wants to merge 2 commits into
karim-alweheshy wants to merge 2 commits into
Conversation
added 2 commits
September 23, 2026 20:58
Add explicit framework/import and link-input output groups for ordinary and mixed target IDs. Make metadata generation independent of expensive link artifacts and omit the selected product when preparing native Preview dependencies. Test archived frameworks and lazy output-group reachability. Signed-off-by: Karim Alweheshy <karim.alweheshy@reddit.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why
Preparing native compiler/linker dependencies must not require rebuilding the selected Bazel product.
Scope
Add dedicated framework/import and link-input output groups for ordinary and mixed-language targets. Test lazy materialization and archived frameworks.
Dependency and landing boundary
Depends on
preview-review-06-swift-imports. Review only the diff against that base. Land the prerequisite first, then retarget/reconcile ontomainand rerun validation; do not merge this PR into the feature branch.Validation
Validated head
56416da0d924665cdbbd336c710e2eb92506afc4against base6e5981874fc082457d78ab96180d1d08f4ce07ebon macOS 26.7, Xcode 27.0 (27A266a), Bazel 9.2.0.DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer USE_BAZEL_VERSION=9.2.0 bazel --bazelrc=bazel_9.bazelrc --nosystem_rc --nohome_rc test --jobs=4 --test_summary=terse //... //docs:diff_test DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer USE_BAZEL_VERSION=9.2.0 bazel --bazelrc=bazel_9.bazelrc --nosystem_rc --nohome_rc run //:buildifier.checkTesting and limitations
Regression tests accompany the changed behavior. Rerun the commands above on the stated base. These results validate this exact split, not arbitrary cherry-picks or a fresh Xcode Canvas render. Hosted CI is pending at publication. This PR alone is not a claim of complete native Preview support; end-to-end Canvas validation belongs to the assembled activation branch.