Closed
Description
openedon Oct 4, 2018
Description
Currently ortools provide its own custom base
library but it should use abseil-cpp instead which is the official way to get Google C++ "basic" set of libraries.
Here the roadmap of origin/abseil branch:
CCTZ Integration (DEPRECATED)
cctz
is not needed anymore since abseil-cpp ship its own version.
(they have copy/paste the cctz code in https://github.com/abseil/abseil-cpp/tree/master/absl/time/internal/cctz)
note: debian already provide a cctz
package...
- Patch
cctz
to add cmake install rule (Missing CMake install rules cctz#82) - Backport cmake install rule to
google/cctz
(cf Add CMake install rules cctz#83) - Add
cctz
as third party deps in Makefile - Revert
cctz
to Makefile (cctz is now integrated in abseil-cpp)
Abseil-cpp Integration
- Patch
abseil-cpp
to add cmake intall rule (Step 6: Allow Abseil to be installed and used with find_package() abseil/abseil-cpp#111) - Backport cmake install rule to
abseil/abseil-cpp
([WIP] CMake Install rule proposal abseil/abseil-cpp#182) - Add
abseil-cpp
to Makefile based build on unix - Add
abseil-cpp
to Makefile based build on windows - Add
abseil-cpp
to CMake based build - Port or-tools to abseil: C++ Part (unix)
- Port or-tools to abseil: C++ Part (windows)
- Port C++ example to abseil
- Port or-tools to abseil: Python Part
- Port Python example to abseil
- Port or-tools to abseil: Java Part
- Port Java example to abseil
- Port or-tools to abseil: .Net Part
- Port .Net example to abseil
- Update Python archive rules
- Update .Net runtime nuget package
- Update CC/Java/.Net archive rules
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment