Closed jedbrown closed 6 years ago
@dmed256 Moving the discussion here from the Spack issue.
A user executable could link to libceed.so
. That doesn't say anything about the location let alone existence (e.g., Debian-style split packages) of headers. If the user isn't supposed to include these kernels in their code (I don't think they are), I would say it doesn't belong in prefix/include.
How does the occa cache work? Where is it? Note that our make install
should work with DESTDIR
.
Fixed in #51 by using dladdr()
.
The .okl files cannot be found after installation. They could be embedded in the libceed library, found at a fixed prefix, optionally respect an environment variable
CEED_DATA_PATH
, or be located relative to the shared library according todladdr()
.see https://github.com/spack/spack/pull/7423#issuecomment-375840822 and https://github.com/CEED/libCEED/pull/45#issuecomment-376013152