Silvio Traversaro
Silvio Traversaro
Linux logs: https://github.com/conda-forge/staged-recipes/runs/2913069235 macOS logs: https://github.com/conda-forge/staged-recipes/runs/2913069047 Windows logs: https://github.com/conda-forge/staged-recipes/runs/2913069121
> Anyway, I don't know if the part of code that was just removing the git repository and cloning it again was removed in this change, we should check that......
Anyhow, before switching to upstream ExternalProject we need: * Finish to switch to FetchContent-based bootstram and document how to do that * Depend on CMake 3.18 (not strictly necessary, but...
> * Finish to switch to FetchContent-based bootstram and document how to do that Done in https://github.com/robotology/ycm-cmake-modules/pull/403 .
For reference, the patch at the time of last import was https://github.com/robotology/ycm-cmake-modules/commit/582b5bca17c31ab511d6cba7b9a8111fc91e0e55 (that was imported on top of https://gitlab.kitware.com/cmake/cmake/-/commit/e67e4dbaadf3583d665fb5409b425e1a238d9748). GitLabCMake Nightly Date Stamp (e67e4dba) · Commits · CMake / CMake...
Hello @aminya, thanks for the feedback! > I have noticed that ycm fails to install `IMPORTED` targets. This is the case, and I think it is actually due to CMake...
Sorry: the package is not built.
The following one is actually a bug, and a quite annoying one: ## The install target of the subprojects is not executed when launching the `ALL_BUILD` target of the superbuild...
Exactly. Perhaps we should use `find_or_build_package(Foo REQUIRED)` ? I never considered doing that.
## After one successful execution of the superbuild, if one tries to re-configure and re-generate the superbuild the superbuild find its own subprojects In particular it finds the subprojects in...