Recently introduced CRTM cmake build breaks ufs-bundle

[climbfuji]

Description

The recently introduced cmake build for crtm breaks ufs-bundle:

CMake Error at fv3-jedi/CMakeLists.txt:84 (find_package):
  By not providing "Findcrtm.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "crtm", but
  CMake did not find one.

  Could not find a package configuration file provided by "crtm" (requested
  version 2.2.3) with any of the following names:

    crtmConfig.cmake
    crtm-config.cmake

  Add the installation prefix of "crtm" to CMAKE_PREFIX_PATH or set
  "crtm_DIR" to a directory containing one of the above files.  If "crtm"
  provides a separate development package or SDK, be sure it has been
  installed.


-- Configuring incomplete, errors occurred!

Additional information

Until this is resolved, use the Skylab v7 tag of CRTM (workaround is in #48).

[climbfuji]

Workaround was merged (use Skylab v7 release tag for CRTM). This is not a solution, therefore keeping this issue open.

[climbfuji]

@BenjaminTJohnson Unfortunately the update we merged into develop (install prefix fix) did not help - this is still an issue. Hopefully I have some time in the next few weeks!

[BenjaminTJohnson]

I guess I'm confused, I haven't changed cmake related things for a while.

Should I revert the latest change?

[climbfuji]

No, sorry for the confusion. I was hoping the latest change would solve a problem that was introduced between the skylabv7 tag (still ecbuild) and the skylabv8 tag (cmake) of crtm. Looking at the error more closely, that was a fool's hope. It can't find crtmConfig.cmake / crtm-config.cmake.

[rhoneyager-tomorrow]

@climbfuji JCSDA/CRTMv3#140 - I may have fixed this inadvertently, though I'm not a regular ufs-bundle user. Might be worth revisiting.

[climbfuji]

@shlyaeva @fmahebert @BenjaminTJohnson please see @rhoneyager-tomorrow 's message above

[shlyaeva]

Thank you @rhoneyager-tomorrow and @climbfuji for bringing this up. I've just tried to build ufs-bundle with the crtmv3 develop and unfortunately see the same error as in this issue description.

[BenjaminTJohnson]

@shlyaeva @climbfuji @rhoneyager-tomorrow I'm confused why CRTMv3 develop works with jedi-bundle: fv3-jedi is the same commit hash for both jedi-bundle and ufs-bundle. I rolled crtmv3 back to even prior to Ryan's commits, and ufs-bundle was failing before Ryan's commits, so this isn't a very new issue.

Specifically:

jedi-bundle: -- [fv3jedi] (1.9.0) [d3c800b]
ufs-bundle: -- [fv3jedi] (1.9.0) [d3c800b]

Any thoughts about what might be different between these two?