-
Notifications
You must be signed in to change notification settings - Fork 14
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
Provide instructions for using Subspace in a CMake-based project #226
Comments
I'll try to write down some steps for the case where you |
Cool :) Very appreciated! |
This might take a bit longer then expected. Github wouldn't let me update my fork, so I deleted it, and now it won't let me fork the subspace repo. I just get an |
Weird 😕 |
Is Github still giving problems? |
This CL adds some documentation on integrating subspace with CMake. In order to make the integration simpler the test files have been moved inside a `SUBSPACE_BUILD_TESTS` cmake option. This allows disabling the subspace tests when integrating. Issue chromium#226
This CL adds some documentation on integrating subspace with CMake. In order to make the integration simpler the test files have been moved inside a `SUBSPACE_BUILD_TESTS` cmake option. This allows disabling the subspace tests when integrating. Issue #226
We have some instructions for checking out and building Subspace, but no integration instructions.
Presumably this is easy for CMake pros, but some steps would be good, that include disabling CIR/Subdoc. And that include enabling the clang-tidy! Once it's merged.
Possibly we should consider vcpkg or something?
@dj2 From your past submissions it seems like you were optimizing this path, do you have any opinions or help you could lend?
The text was updated successfully, but these errors were encountered: