YAML_CPP_INCLUDE_DIR

[quasiquote1]

I updated to the latest sparta and started getting this error when running cmake on sparta:

CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
YAML_CPP_INCLUDE_DIR

I was able to fix this by modifying cmake/sparta-config.cmake:

+get_property(YAML_CPP_INCLUDE_DIR TARGET yaml-cpp PROPERTY INTERFACE_INCLUDE_DIRECTORIES)

I am not sure why this error is popping up - I'm using cmake version 3.16.3

Is there a fix for this issue? Thanks in advance

[klingaard]

Which OS is this?

[klingaard]

I started a branch knutel/yaml_include_issue_328 that has @quasiquote1's fix in it. Rob, if you want to try that branch, I'd appreciate it. I'm trying the fix as well.

[klingaard]

I'm also using the conda environment that Jack mentions, which alleviate a lot of annoyances.

[robbellphd]

@klingaard @quasiquote1 @jackjchen Thanks, the change in that patch allowed the build to work. All the regress and example core tests pass. Using ubuntu 20.04, yaml-cpp 0.6.2, cmake 3.23.1 (manually downloaded from github Kitware and applied). Interesting note, the SchedulerTimeout_test seg faulted on the first regress run. When I reran the full regress, it passed.

[robbellphd]

I see that Jammy will be at only cmake 3.22.1 when it is released, don't know if that is enough to work on Sparta out of the box when I update to Jammy. My current Focal was at cmake 3.16.3.

[klingaard]

Thanks for trying it out, Rob! I tested it with RHEL8 with no issues as well. I'll start a PR. Thanks, @quasiquote1 for the suggestion!

[klingaard]

BTW, to see exactly what Sparta is looking for:

cmake -DCMAKE_BUILD_TYPE=Release .. -DSparta_VERBOSE=ON

[jackjchen]

@robbellphd, I am running ubuntu 20.04 with a conda env which currently will solve to use yaml-cpp 0.6.3 (where I don't see this yaml include problem). The other cmake issue you mention may be just a warning that the optional cppcheck tool is not found. If this is the sole issue, you should be able to continue with building and running in my experience, or just install cppcheck.

[robbellphd]

Thanks @jackjchen will look into using conda eventually.

[ghost]

Fixed in master via PR #330