CI Failure April 2024

[traversaro]

Message failure:

CMake Warning at /home/runner/work/matio-cpp/matio-cpp/install/lib/cmake/matioCpp/matioCppConfig.cmake:24 (find_package):
  By not providing "FindMATIO.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "MATIO", but
  CMake did not find one.

  Could not find a package configuration file provided by "MATIO" with any of
  the following names:

    MATIOConfig.cmake
    matio-config.cmake

  Add the installation prefix of "MATIO" to CMAKE_PREFIX_PATH or set
  "MATIO_DIR" to a directory containing one of the above files.  If "MATIO"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  CMakeLists.txt:4 (find_package)


-- Configuring done (0.2s)
CMake Error at /home/runner/work/matio-cpp/matio-cpp/install/lib/cmake/matioCpp/matioCppTargets.cmake:61 (set_target_properties):
-- Generating done (0.0s)
  The link interface of target "matioCpp::matioCpp" contains:

    MATIO::MATIO

  but the target was not found.  Possible reasons include:

    * There is a typo in the target name.
    * A find_package call is missing for an IMPORTED target.
    * An ALIAS target is missing.

Call Stack (most recent call first):
  /home/runner/work/matio-cpp/matio-cpp/install/lib/cmake/matioCpp/matioCppConfig.cmake:33 (include)
  CMakeLists.txt:4 (find_package)


CMake Generate step failed.  Build files cannot be regenerated correctly.

see #77 .

Originally found by @Nicogene .

[traversaro]

I guess we can start porting the changes in ami-iit/bipedal-locomotion-framework#827 here, as anyhow they are needed to avoid similar bugs.

[traversaro]

This is not fixed by #79 .

[traversaro]

It seems that this is some kind of regression related to https://gitlab.kitware.com/cmake/cmake/-/merge_requests/9390, that got release in cmake 3.29.1 . In conda CI the workaround is to pin cmake 3.29.0, in apt GitHub Actions builds probably we need to remove the custom cmake installed by GitHub Actions images to use the one from apt (or just use docker images).

[traversaro]

It seems that this is some kind of regression related to https://gitlab.kitware.com/cmake/cmake/-/merge_requests/9390, that got release in cmake 3.29.1 . In conda CI the workaround is to pin cmake 3.29.0, in apt GitHub Actions builds probably we need to remove the custom cmake installed by GitHub Actions images to use the one from apt (or just use docker images).

Actually the problem was in the InstallBasicPackageFiles module, in particular the variant with the OVERRIDE_MODULE_PATH option used here and in BLF, that used some CMake functionality that was an implementation detail. This was fixed in #79 and released in https://github.com/ami-iit/matio-cpp/releases/tag/v0.2.4 .