Skip to content

Conversation

xedin
Copy link
Contributor

@xedin xedin commented Aug 17, 2024

Motivation:

Now that we have all the tools to compute destinations for dependencies of a product,
we no longer need buildTriple here and dynamic/static library results could be represented
by build descriptions as a bonus.

Modifications:

  • BuildPlan.computeDependencies(of:) has been updated to take a ProductBuildDescription and use depth first scan that computes destination;
  • Further, dynamic and static library dependencies are now presented by build descriptions which means that we no longer need to look stuff up while planning.

Result:

One more use of buildTriple is gone.

…f:)`

Now that we have all the tools to compute destinations for dependencies
of a product, we no longer need `buildTriple` here and dynamic/static
library results could be represented by build descriptions as a
bonus.
@xedin
Copy link
Contributor Author

xedin commented Aug 17, 2024

@swift-ci please test

@xedin xedin merged commit 520d11a into swiftlang:main Aug 19, 2024
5 checks passed
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.

2 participants