-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
Add spatio_temporal_voxel_layer #275
Add spatio_temporal_voxel_layer #275
Conversation
I noticed that the openvdb_vender package builds the OpenVDB from source rather than finding the package from the system. I don't know if this is the proper way not to install openvdb with conda-forge. |
Good catch. Typically we patch vendor packages and add the missing vendor dependency to use the conda-forge version. I am now on the phone, but you can probably find examples of this pattern in the repo, I can provide links as soon as I am on a laptop. |
For reference, here is the vendor package - it looks like all we need to do is to make sure openvdb=10 is available. |
I tried to set openvdb=10.0.1 in |
I guess it is https://github.com/SteveMacenski/spatio_temporal_voxel_layer/blob/616690db7011178014d2c096cf6d56d1c7dfd5f3/openvdb_vendor/CMakeLists.txt . OpenVDB does not seem to contain a lot of breaking changes (even if the major version changes), could it make sense to give it a short with openvdb 12? A patch with |
I have updated |
Here is the build log. It looks like something wrong with |
@Ericsii can you please rebase on top of latest main? Thanks! I do not think this will solve your build failure, but at least we will build on a working base. |
4211cc3
to
40e4b51
Compare
Ok, thanks for the rebase, back to the build error, that is the same on
|
So, it is a bit surprising that the linker complains about missing symbols, as in general it is perfectly fine for a shared library on ELF platform not to resolve all it symbols at link time, as long as those symbols are then eventually present in the binary that loads the shared library (in case of Python extensions, the Python interpreter itself). Indeed, with recent version of CMake if you link with What is different in this project w.r.t. to other projects is these CMake line: https://github.com/SteveMacenski/spatio_temporal_voxel_layer/blob/7801267acfd63d9845c0e581ec3b652ea11c1aa3/spatio_temporal_voxel_layer/CMakeLists.txt#L82-L83 . Patching it out everything should work fine. |
I suggested an upstream solution in SteveMacenski/spatio_temporal_voxel_layer#325 and add it locally as a patch. |
Thanks @Ericsii ! |
WIP.
Reference issue: #270