Closed utke1 closed 4 years ago
BTW - I am running "GNU bash, version 4.2.46(2)"
OK - looking a little bit closer shows that this part of the parsing:
sed -e 's|.*= *||g'
eats up everything until the "=" character in -std=c++11
, hence the result.
To be sure - I would be OK to compile cppad separately but I am somewhat confused by the seeming coexistence of cmake and autotools artifacts in the cppad repo (and I will readily confess that I don't understand cmake builds well, find it somewhat inscrutable and consequently am not a big fan of it :-) )
Perhaps a good way to go is to use CMake for testing the C++ library, and setup.py for testing the python library. That way, cmake would not need to get the version of python correctly (which gets very confusing on many systems).
I am currently in the middle of something else for CppAD, but will try to get to this soon.
I removed the continuation lines in setup.py (and did some other fixing along these lines).
I have revamped the setup so that setup.py does the building and cmake is only used for testing. If you have problems with this, please re-open this bug.
with the latest version of setup.py having:
the output of
bin/get_cppad.sh
showsand the compile fails with
Even if I remove the newline the parsing in get_cppad.sh I see as
still gets a messed ouput because then I see