spkg-configure for symengine

[dimpase]

symengine does not seem to have pkg-configure interface, so we need to test something

CC: @orlitzky @mkoeppe @isuruf @slel

Component: build: configure

Issue created by migration from https://trac.sagemath.org/ticket/32421

[mkoeppe]

comment:3

Note that the Python wrapper symengine.py uses CMake to find the library (via the CMake metadata installed in local/lib/cmake/symengine) - so that's what spkg-configure.m4 should use too. Of course, this assumes that system cmake is available; but I think it's fine to only use system symengine when also system cmake is present.

[dimpase]

comment:4

Replying to @mkoeppe:

Note that the Python wrapper symengine.py uses CMake to find the library (via the CMake metadata installed in local/lib/cmake/symengine) - so that's what spkg-configure.m4 should use too.

This requires writing cmake config script, i.e. CMakeLists.txt, as far as I can see.
Integrating this into spkg-configure.m4 is above my pay grade...

[isuruf]

comment:5

See https://github.com/symengine/symengine/wiki/Using-SymEngine-from-a-Cpp-project#non-cmake-projects

[dimpase]

comment:6

Replying to @isuruf:

See https://github.com/symengine/symengine/wiki/Using-SymEngine-from-a-Cpp-project#non-cmake-projects

and how about asking for the version?

[orlitzky]

comment:7

If we need a specific feature in newer versions of symengine, we can test for that feature instead of the version. And if nobody knows what features we need... then as a last resort, we can accept any version of symengine, and any consequent bug reports will tell us what we should have checked for.

[isuruf]

comment:8

There's a symengine_version() C function that you can call to get it.
Or you can use the following program to see if it compiles,

#include <symengine/symengine_config.h>
#if (SYMENGINE_MAJOR_VERSION*10000 + SYMENGINE_MINOR_VERSION*100 + SYMENGINE_PATCH_VERSION < 00700)
# error "SymEngine 0.7.0 or newer is required"
error
#endif

[mkoeppe]

comment:9

Replying to @dimpase:

Replying to @mkoeppe:

Note that the Python wrapper symengine.py uses CMake to find the library (via the CMake metadata installed in local/lib/cmake/symengine) - so that's what spkg-configure.m4 should use too.

This requires writing cmake config script, i.e. CMakeLists.txt, as far as I can see.
Integrating this into spkg-configure.m4 is above my pay grade...

Just create a directory conftest.dir and generate the file in there