Inconsistent include path in cmake package

[wspear]

I am constructing a simple test for alquimia as deployed by Spack as part of the E4S testsuite. To do this I'm just extracting the test_alquimia_c_utils.c test and setting up a cmake build against the installed package. But I'm running into an issue. This test code does its includes like:
#include "alquimia/alquimia_constants.h"
But the installed share/alquimia/alquimia.cmake uses this in its include path setup:
/home/wspear/bin/SPACK/spack/opt/spack/linux-ubuntu20.04-westmere/gcc-9.4.0/alquimia-1.0.9-pfi4oostbni47etbzzcsmatu5ncnfqje/include/alquimia

Since the source is asking for a file with respect to the top level include directory it isn't found. Editing the source file doesn't fix it since the header files also do their includes with respect to the base include directory.

If there is a better way to set up a quick sanity check for an installed version of alquimia I would be happy to hear about it. I'm fine with bypassing cmake altogether.

[smolins]

So you want to set up a test for Alquimia separately from the Alquimia package using tests that come with Alquimia. These tests were designed to work as part of Alquimia's build so we did not think about your issue. I am far from understanding all this as I was not involved in this software engineering work. I am glad to accept suggestions how to modify/adapt the tests to make things work.

[wspear]

That is my objective. I was able to build test_alquimia_c_utils with a makefile. Can you confirm that is a reasonable sanity test for an install? If that's the case I'm all set on my side.

The issue I ran into with the cmake build might be a legitimate bug. To me, it looks like the cmake-provided include path needs to be
{install path}/include
rather than
{install path}/include/alquimia

But I'm not sure if anything actually uses {install path}/share/alquimia/alquimia.cmake and if not it's probably not a big deal.