These are chat archives for symengine/symengine
@certik, since we are separating the python wrappers, I think we should make SymEngineConfig.cmake more robust. How about something like this?
We install all our FindPKG modules. From SymEngineConfig.cmake we set GMP_INCLUDE_DIRS="absolute_path:relative_path" and then call
find_package(GMP). Is this okay?
symengine.pyto specify where the gmp headers/libraries are, but use the fullpath given by
symengineas a hint.
setup.py install --define="GMP_DIR=/path"
symenginerepo. This will force us to make sure that everything is covered by C++ and C tests, and also to think harder about the public API that we expose. For example I think we should have a set of headers that are the public API, and the rest of headers are for internal use only and those can change without problems. For public API, we should be more careful.
symengine.py, we would test just Python, but very very thoroughly.
symengine.pywill pull in a certain git commit of
symengineand that will work. Then if we break the API by a mistake, let's say, then next time we update
symengine.py, we notice that the PR to
symengine.py(that updates the git commit of
symengine) fails, so we either update the wrapper, or fix