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.

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

CI Cleanup #400

Closed
wants to merge 71 commits into from
Closed

CI Cleanup #400

wants to merge 71 commits into from

Conversation

bifurcation
Copy link
Contributor

@bifurcation bifurcation commented Oct 27, 2023

Bunch of small fixes to make CI more rational / elegant:

  • Make CMAKE_TOOLCHAIN_FILE an environment variable
  • Make OpenSSL 1.1 parallel to other crypto libraries
  • Simplify out the vcpkg-dir variables

Depends on #398

VCPKG_REPO: ${{ github.workspace }}/vcpkg
CACHE_VERSION: v01
CACHE_NAME: vcpkg

OPENSSL_11_VCPKG: alternatives/openssl_1.1
OPENSSL_3_VCPKG: alternatives/openssl_3
BORINGSSL_VCPKG: alternatives/boringssl
Copy link
Contributor

Choose a reason for hiding this comment

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

I find myself getting confused about which vcpkg attribute we might be talking about. I would recommend renaming this to *_VCPKG_MANIFEST to match the cmake option.

@@ -196,7 +215,7 @@ jobs:
runs-on: macos-latest

env:
CMAKE_BUILD_DIR: ${{ github.workspace }}/build
BUILD_DIR: ${{ github.workspace }}/build
VCPKG_BINARY_SOURCES: files,${{ github.workspace }}/build/cache,readwrite
Copy link
Contributor

Choose a reason for hiding this comment

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

I know you did not change anything, but this is redundant. It should be at the top.

Copy link
Contributor

@glhewett glhewett left a comment

Choose a reason for hiding this comment

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

I think it would be wise to have a default vcpkg.json in the root of the project. Not because it is useful but because it what people expect.

Alternatively, when we add the build directions, we can request the user to copy or symlink the file. We might want to add it to the .gitignore if that is the case.... just a brainstorm

@bifurcation
Copy link
Contributor Author

bifurcation commented Nov 2, 2023

Closed in favor of #406

@bifurcation bifurcation closed this Nov 2, 2023
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