Heads up for incoming changes

By -
Hello,

we are working on a few changes, some will break compatibility in C++.

Callbacks are going away. We will use std::function now. The result is fantastic as we can now pass inline code where callbacks where needed (custom limits, variable and value evaluators,  search logs...). I have decided to break compatibility and not keep the old API. Please note that this affects only the C++ layer as this was already hidden in the other languages. I expect this change to land around the end of January.

We will switch to  github for our source repository sometime in Q1. I don't know exactly when.

I am contemplating swiching to cmake for our build system, unfortunately this is a totally different way of thinking, and I need time to adjust.

Thank you all and happy new year.

Comments

  1. AnonymousJanuary 30, 2015 at 1:52 AM

    Re: callbacks, does this mean the callbacks can be lambda functions too? Great news if so! I wanted to use an object method as a callback but couldn't find how to do it, so I've done a hack for now, but a capturing-lambda would be even better!

    ReplyDelete

Post a Comment

Popular posts from this blog

Linking glpk with or-tools on unix

By -
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.
Read more

Changing the way we link with SCIP

By -
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  
Read more

Heads up, upcoming incompatibility in the CP/Routing library

By -
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
Read more