Skip to content

build: distribute CCryptoBoringSSL #71

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
Feb 6, 2021
Merged

Conversation

compnerd
Copy link
Contributor

@compnerd compnerd commented Feb 6, 2021

Ensure that we distribute CCryptoBoringSSL for users as it is used
directly by SPM.

[One line description of your change]

Checklist

  • I've run tests to see all new and existing tests pass
  • I've followed the code style of the rest of the project
  • I've read the Contribution Guidelines
  • I've updated the documentation if necessary

If you've made changes to gyb files

  • I've run .script/generate_boilerplate_files_with_gyb and included updated generated files in a commit of this pull request

Motivation:

[Explain here the context, and why you're making that change. What is the problem you're trying to solve.]

Modifications:

[Describe the modifications you've done.]

Result:

[After your change, what will change.]

The `include` directory is required for the interface include
directories for using `CCryptoBoringSSL` as a module from an external
package (i.e. SPM).  This allows SPM to include `CCryptoBoringSSL`
and find the module map.
@yim-lee
Copy link
Member

yim-lee commented Feb 6, 2021

Verified locally that this fixes the build for swiftlang/swift-package-manager#3238

Thanks so much @compnerd!

@yim-lee
Copy link
Member

yim-lee commented Feb 6, 2021

Merging so we can test with SwiftPM CI

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