-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
building with CGAL 5 #56
Comments
Joachim Reichel suggests it needs |
The relationship between cmake and setup.py seems to complicate the build conditions. Joachim says the mere presence of cmake means it is invoked in pybuild build, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946233. But it doesn't work that way for me. For me it's either |
This seems like it's related to pypa/setuptools#1732 (comment): setuptools indeed uses the C compiler, not C++, to compile C++ projects. Only the linker step uses |
Hm. Well, the CMake files aren't terribly important to me, but sometimes I use them to debug which is why I don't want to toss them completely. If we can find another way of making this work, that'd be great. |
If we're clear on the intended role of cmake (intended for developer debugging only) then Debian can just ignore it. Perhaps a comment could be added to CMakeLists.txt or README to make that clear The failing CGAL 5 build is documented at https://buildd.debian.org/status/package.php?p=pygalmesh |
Fixing this right now. |
Alright, all done now. |
Thanks, will test. |
pygalmesh needs some help to build against CGAL 5, which is now header-only.
Dropping the CGAL libraries themselves is easy enough. (I guess you'd want the build able to work with both CGAL 4 or 5)
But then there's a more subtle problem (on Debian unstable). setup.py seems to be invoking gcc to compile the extensions, but the files are C++. setup.py does refer to C++, but nevertheless the build proceeds with x86_64-linux-gnu-gcc instead of x86_64-linux-gnu-g++.
Consequently when running tests,
The missing symbol is in
libstdc++.so
.The text was updated successfully, but these errors were encountered: