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

Migrate project to use FetchContent and custom CMake files #10

Closed
traversaro opened this issue Apr 30, 2019 · 1 comment
Closed

Migrate project to use FetchContent and custom CMake files #10

traversaro opened this issue Apr 30, 2019 · 1 comment

Comments

@traversaro
Copy link
Contributor

As the probability of the improvements in the CMake being merged upstream is really low, I think it would improve maintainability to strictly separate the raw files coming from the qpOASES tarball, and our own CMake files. In this way, updating to a new qpOASES should be simpler. One possibility is event to fetch the source code during the configuration phase using CMake's FetchContent module.
I think this projects would be a good example:

@traversaro
Copy link
Contributor Author

As we have submitted upstream the changes that we need as described in #1, I think we hopefully can switch to use the upstream directly at some point in the future, so there is no need to setup this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant