Use Ceres_[SOURCE/BINARY]_DIR not CMAKE_XXX_DIR to support nesting. - Using Ceres_[SOURCE/BINARY]_DIR (which are defined by CMake when project(Ceres) is called, in favour of CMAKE_[SOURCE/BINARY]_DIR enables Ceres to be nested within (and built by) a larger CMake project (which also contains other projects). - CMAKE_[SOURCE/BINARY]_DIR always refers to the top-level source and binary directories (i.e. the first encountered), as a result if Ceres is a nested project within a larger project, these would not correctly identify the source/binary directories for Ceres (as they would refer to the root project in which Ceres is nested). - Using Ceres_[SOURCE/BINARY]_DIR should ensure that Ceres always uses the correct source/binary directories, irrespective of whether Ceres is nested or not. Change-Id: I62226ea3f6552b1d7e2bdac1aef02f1f489ae55e
Ceres Solver is an open source C++ library for modeling and solving large, complicated optimization problems. It is a feature rich, mature and performant library which has been used in production at Google since 2010. Ceres Solver can solve two kinds of problems.
Please see ceres-solver.org for more information.
Ceres development happens on Gerrit, including both repository hosting and code reviews. The GitHub Repository is a continuously updated mirror which is primarily meant for issue tracking. Please see our Contributing to Ceres Guide for more details.
The upstream Gerrit repository is
https://ceres-solver.googlesource.com/ceres-solver