You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project I am trying to build is a C++ library that uses autotools, which is then wrapped with swig into Python module + extension.
The problem is that if I need to build the extension the setuptools way, I need to replicate all include dirs and compiler options in pyproject.toml for all libs and dependencies that are compiled in the extension.
I've just started, but I am already getting some spurious errors from C++ compiler that some code is invalid.
I already can see that this approach is cumbersome and unmaintainable. First, I don't have necessary C++ skills to troubleshot that, but also maintaining two build toolchains - autotools and setuptools - in parallel just seems plain wrong.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The project I am trying to build is a C++ library that uses autotools, which is then wrapped with
swiginto Python module + extension.The problem is that if I need to build the extension the
setuptoolsway, I need to replicate all include dirs and compiler options inpyproject.tomlfor all libs and dependencies that are compiled in the extension.I've just started, but I am already getting some spurious errors from C++ compiler that some code is invalid.
I already can see that this approach is cumbersome and unmaintainable. First, I don't have necessary C++ skills to troubleshot that, but also maintaining two build toolchains -
autotoolsandsetuptools- in parallel just seems plain wrong.Beta Was this translation helpful? Give feedback.
All reactions