Skip to content

Conversation

@criemen
Copy link
Contributor

@criemen criemen commented Jan 19, 2026

Fixes #3089.

AI-generated, I still need to understand this better and test it more before putting it up for review.

…d#3089)

This test reproduces the bug where crate_universe fails when a Cargo
workspace member has a path dependency pointing outside the Cargo
workspace root (but still inside the Bazel workspace).

The test is expected to fail until the bug is fixed.
When a Cargo workspace member has a path dependency pointing outside the
Cargo workspace root (but still inside the Bazel workspace), crate_universe
now correctly symlinks the external crate to the appropriate location in
the temporary splicing directory.

The fix:
1. Added symlink_external_path_deps() function in splicer.rs that extracts
   path dependencies from manifests and symlinks external ones
2. Call this function from splice_workspace and splice_package
3. Also call it from cargo_tree_resolver's
   copy_project_with_explicit_deps_on_all_transitive_proc_macros to handle
   the tree resolver's temp directory
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.

External relative path dependencies not working

1 participant