Closed Dekker1 closed 3 years ago
LGTM.
I think we want to add it to release/6.3.0 as well?
Hi Mikael,
I thought the 6.3.0 release was already out. I'm happy for it to go into the release/6.3.0 instead
Is there an ETA for 6.3.0?
I will get this merge soon, just haven't had the time.
@yurivict We would like to get the 6.3.0
release out, but have stalled due to two factors
The latter issue can be "solved" by only making a source-code release and not creating pre-compiled artifacts. The former is more important though, since we do not want to release a version that has not been tested sufficiently.
You can probably merge this into the 6.3.0 branch.
Merged into the release/6.3.0 branch as well.
This PR is to make
fzn-gecode
ready to be used with MiniZinc from the moment youmake install
.This is achieved by changing two things:
PREFIX/share/minizinc/solvers/gecode.msc
PREFIX/share/minizinc/gecode
instead ofPREFIX/share/gecode/mznlib
. (This is the standard location for MiniZinc libraries and where the library would be installed by the MiniZinc bundle)Once
make install
is run you can extendMZN_SOLVER_PATH
withPREFIX/share/minizinc/solvers
to make the installed Gecode directly available to MiniZinc. If thePREFIX
is a standard location, such as/usr/local/
, then the solver configuration will immediately be detected.These changes will make the Gecode repository more self-sufficient within the MiniZinc infrastructure and will allow developers and users to easily use different versions of Gecode with MiniZinc.
Possible future improvements might be to allow CMake/autotools to append the name/id in the configuration for custom versions of Gecode. (For now this went beyond my auto tools knowledge).