-
Notifications
You must be signed in to change notification settings - Fork 15
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
Build Python bindings against existing sparrow installation #9
Comments
I think the answer is: no. The wrapper requires its own source files that are present in the repository. I think this is what what you are asking for, right? |
For some context, I'm trying to build Python bindings with multiple versions of Python and want to reduce the overhead from compiling the C++ part over and over again. Having just the C++ library installed first and than compile the Python bindings for several Python versions against the "old" library would be very useful. |
Ohh. then this may be all you need:
You should be able to just reconfigure cmake, not needing to rebuild the other targets. This still has the overhead of installing the main library every time, but it hopefully builds it only once. |
I think I could solve this by introducing a new switch to skip the build of the library Patch for
|
I have tested the above codes, both versions, yours and mine work. While I understand the usage of your flag in the use case that you describe I am unsure if it is clean to just add it. For now this issue will stay open, I have not staged that patch for the next release. |
I'm currently using this setup to build the Python bindings for |
To clarify: I was talking about the import in your patch.
with this it is possible to have version 3.0.0 installed on a system, but to try and build the version 4.0.0 bindings against it. If you generate the same possible problem in the conda dependency resolution, then yes I would advise to fix the wrapper version to be the same as the library version. |
I made the version constraint exact to ensure it always matches inside the conda build and environment. This should ensure my little hack for splitting the C++ and Python part of the library will be compatible. |
Is there a possibility to build the Python bindings against an existing installation of sparrow?
The text was updated successfully, but these errors were encountered: