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

build: add a CMake based build for swift-benchmarks #22

Merged
merged 1 commit into from
May 14, 2020

Conversation

compnerd
Copy link
Contributor

This adds a CMake based build system for swift-benchmark, enabling
support on Windows. This support includes optionally building the
example programs and covers the test suite. The exports file also
is generated for ease in using in other projects.

The test suite is best run in an automated fashion using
cmake --build /BinaryCache/current/swift-benchmark --target test (aka
ninja test).

This adds a CMake based build system for swift-benchmark, enabling
support on Windows.  This support includes optionally building the
example programs and covers the test suite.  The exports file also
is generated for ease in using in other projects.

The test suite is best run in an automated fashion using
`cmake --build /BinaryCache/current/swift-benchmark --target test` (aka
`ninja test`).
@shabalind
Copy link
Collaborator

Hi @compnerd, the addition of cmake sounds like a fantastic addition!

I was wondering how hard would it be to include cmake in the github actions CI to make sure we don't break the build in the future?

@compnerd
Copy link
Contributor Author

That shouldn’t be too difficult. It does involve some work to install ninja on each run as the request to install ninja on the image’s was denied.

@shabalind
Copy link
Collaborator

LGTM! 👍

@shabalind shabalind merged commit 4c8bab0 into google:master May 14, 2020
@compnerd compnerd deleted the cmake branch May 14, 2020 19:25
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.

None yet

2 participants