You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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:
The text was updated successfully, but these errors were encountered: