Skip to content
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.

Sign up for GitHub

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

Jump to bottom

chore: create a single Bazel build file for each external Swift package #82

Merged
merged 8 commits into from
Dec 19, 2022
Merged

chore: create a single Bazel build file for each external Swift package #82

merged 8 commits into from
Dec 19, 2022

Conversation

cgrindel
Copy link
Owner

  • Swift package targets are now generated with label names derived from their path and target name.
  • All declarations for an external Swift package are generated in a single Bazel build file.

Related to #81.

@cgrindel cgrindel self-assigned this Dec 19, 2022
@cgrindel cgrindel enabled auto-merge (squash) December 19, 2022 19:11
@cgrindel cgrindel merged commit d9a404f into main Dec 19, 2022
@cgrindel cgrindel deleted the try_local_swift_package branch December 19, 2022 19:57
@cgrindel cgrindel mentioned this pull request Dec 19, 2022
Closed
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@cgrindel cgrindel

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@cgrindel