Following the change on SCIP, here is the new procedure to compile and link GLPK with or-tools This currently applies to unix only: First download the latest glpk archive (4.61 at the time of this post). Untar, cd into the glpk directory on linux: ./configure --prefix=<install_path> --with-pic make make install on mac OS X: ./configure --prefix=<install_path> make CFLAGS='--mmacosx-version-min=10.8' make install then add: UNIX_GLPK_DIR=<install_path> in or-tools/Makefile.local recompile or-tools: make clean make cc test it: run bin/integer_programming and bin/linear_programming. Both must display glpk runs. I have no easy solution for glpk on windows currently, still investigating.
Popular posts from this blog
As of today, I pushed support for scip 4.0.0 on both unix and windows. In the process, I have changed the way to setup or-tools to include scip at compilation time. on Unix: untar the scipoptsuite> archive somewhere cd <path to scipoptsuite-4.0.0> Mac OS X: make GMP=false READLINE=false TPI=tny Linux: make GMP=false READLINE=false TPI=tny USRCFLAGS=-fPIC USRCXXFLAGS=-fPIC USRCPPFLAGS=-fPIC in or-tools, edit Makefile.local add: UNIX_SCIP_DIR=<path to sciptopsuite-4.0.0>/scip-4.0.0 make clean make cc to test it, run: bin/integer_programming it should display the scip solver run. on windows: download the compiled library: http://scip.zib.de/download.php?fname=scip-4.0.0.win.x86_64.vc14.opt.spx2.lib.zip download the headers: http://scip.zib.de/download/release/scipoptheaders-4.0.0.tgz uncompress, untar everything. create a directory that will contains what is needed md scip-4.0.0
Hello all, I will soon push a large incompatible change in the CP and Routing libraries. The change will replace parameters (CP solver parameters, routing model parameters, routing search parameters) from struct to protobuf. This will also hide the C++ command line flags (cp_trace_search, routing_first_solution, ...) and make them redundant for controlling the behavior of the libraries. They are currently kept in the C++ library, but will be dropped out eventually. With this move, all functionalities offered by the C++ command line flags will be available from all languages (provided you implement the command line parsing part). Let's see an example (tsp) Before (in C++): // Setting first solution heuristic (cheapest addition). FLAGS_routing_first_solution = "PathCheapestArc"; const Assignment* solution = routing.Solve() ; After (in C++, using the command line flags compatibility) : RoutingSearchParameters parameters = BuildSearchParametersFro