Skip to content

Add an "upward" link library type for BuildDependencyInfo #456

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 1 commit into from
May 1, 2025

Conversation

bob-wilson
Copy link
Contributor

Upward linking is used when there would otherwise by a cyclic dependency so it is important to know that in the dependency information.

rdar://143493388

@owenv
Copy link
Collaborator

owenv commented Apr 29, 2025

@swift-ci test

Copy link
Collaborator

@jakepetroules jakepetroules left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Test is failing:

✘ Test buildSettingsInputs() recorded an issue at BuildDependencyInfoTests.swift:407:25: Expectation failed: (input.libraryType → .dynamic) == .upward
↳ input.libraryType: SWBBuildService.BuildDependencyInfo.TargetDependencyInfo.Input.LibraryType → .dynamic
↳ .upward: SWBBuildService.BuildDependencyInfo.TargetDependencyInfo.Input.LibraryType → .upward
✘ Test buildSettingsInputs() failed after 36.319 seconds with 1 issue.

Upward linking is used when there would otherwise by a cyclic dependency
so it is important to know that in the dependency information.

rdar://143493388
@bob-wilson
Copy link
Contributor Author

@swift-ci test

@bob-wilson bob-wilson merged commit 8dbfeac into main May 1, 2025
22 checks passed
@bob-wilson bob-wilson deleted the upward-link-deps branch May 1, 2025 16:06
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