Split into papilo library package, papilo program package

[mkoeppe]

... to resolve the circular dependencies scip -> papilo -> scip and soplex -> papilo -> soplex.

@ambros-gleixner

[dimpase]

alternatively, make building/installing papilo executable conditional on boost availability.

[mkoeppe]

... or an option to disable the build of the executable (and the check for its dependencies)

[mkoeppe]

@fschloesser

[fschloesser]

@alexhoen might be able to help here

[alexhoen]

We discussed it and came to the following conclusion::

As you pointed out, if PaPILO is integrated into a solver, the interface is not needed and therefore does not need to be included.

We recommend (besides building PaPILO without any solver) to just include it before building. since PaPILO is a header-only library.

In this case, the following list of instructions should work and the circular dependency should not be a problem.

mkdir papilo/build cd papilo/build cmake (-DLUSOL=0) .. mkdir ../../scip/build cd ../../scip/build cmake -DPAPILO=PATH .. make cd - make
(Unfortunately, Lusol needs to be deactivated to only include the files in SCIP, but we are looking into that)

Boost is used in many places all over PaPILO so making boost optional is not an option

[mkoeppe]

Thanks. There's no problem with most uses of boost (we have the boost headers in Sage) but we are patching out the boost program_options requirement because that requires linking to an actual library, and it is not needed by the header-only library used by SCIP/SoPlex.
https://git.sagemath.org/sage.git/commit/?id=a52e72f39c93852e3f8207619dbbad4a18c781d9

https://trac.sagemath.org/ticket/34726

[alexhoen]

I see.
Would a PaPILO version with optional boost program_options be helpful for you in this case?

[mkoeppe]

Yes, that would be helpful!

[alexhoen]

I implemented a non program_options in which case the cl can not be used anymore.
It will be online mirrored tomorrow

[mkoeppe]

I don't see this change on the master branch

[ambros-gleixner]

This may be slightly confusing: In PaPILO, the latest development branch is called the "develop" branch, and "master" is the stable/bugfix branch. This change was only performed in the develop branch.

[alexhoen]

yes Ambros is right: develop contains the new features and master is last stable release.

a573730

this is the merge commit of making program options optional in the develop branch.

Sorry for the inconvience

[mkoeppe]

Ah, I see, thanks!