We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
pybind11 seem to be able to do what we are currently using Boost.Python for today.
Some of the reasons in favour of migrating
cmake/boost.cmake
gaussianfft
Some reasons against migrating
The text was updated successfully, but these errors were encountered:
When using pybind11 instead of boost we avoid the issue which arise when boost version in RMS and boost version in gaussianfft are different.
Sorry, something went wrong.
No branches or pull requests
pybind11 seem to be able to do what we are currently using Boost.Python for today.
Some of the reasons in favour of migrating
cmake/boost.cmake
contributes quite a bit to the complexity of compilinggaussianfft
Some reasons against migrating
The text was updated successfully, but these errors were encountered: