Debug cmake-issues triggered by SCIP 9.2.0

[discopt]

This is not intended for merging but for debugging cmake issues.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition. I do have some suggestions for making it better though...

For recipe/meta.yaml:

• It looks like the 'papilo' output doesn't have any tests.
• The boost-cpp output has been superseded by libboost-devel (as of 1.82), which now comes with a run-export (on libboost) as well. In case you only needed the boost headers, you should use libboost-headers.
• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

[scip-ci]

@DominikKamp says that he can reproduce this issue on his machine, using a cmake build of the scip optsuite.

@DominikKamp, maybe you can run cmake with --trace and attach the output.

[DominikKamp]

I can avoid the error when I dump

set(CMAKE_MODULE_PATH "/usr/local/lib/cmake/papilo")

in front of

find_dependency(GMP)

in papilo-config.cmake since otherwise the variable is just empty.

cmake.log

[discopt]

I can avoid the error when I dump

set(CMAKE_MODULE_PATH "/usr/local/lib/cmake/papilo")

in front of

find_dependency(GMP)

in papilo-config.cmake since otherwise the variable is just empty.

But this will probably not fix it under Windows because that directory is just not there! I created a PAPILO-internal issue and a merge request to address this properly.

[DominikKamp]

Of course, this should only indicate that papilo-config.cmake is not aware of the location of the corresponding cmake module (although it already lives there).

[scip-ci]

77 has a working solution, using a patch authored by @discopt.