Vendor packages for cumm and spconv

[esteve]

Code of Conduct

• I have read CODE OF CONDUCT and Support Guidelines before creating this Discussion post.

Contents

The packages for https://github.com/autowarefoundation/spconv_cpp are provided as manually generated Debian packages, is there a reason why they are not distibuted as vendor packages? (like https://github.com/ros2/tinyxml2_vendor, https://github.com/ros2/pybind11_vendor, etc.)

[esteve]

@mitsudome-r @xmfcx please tag the perception team, I only know of @knzo25 who is the maintainer of https://github.com/autowarefoundation/spconv_cpp

[drwnz]

@esteve thanks!
Please have a look @YoshiRi @amadeuszsz
(I think we should add @amadeusz as a maintainer for this package).

[amadeuszsz]

@esteve
I only remember the reason why this package is not being built from source in CI — it's due to the long build time.

I believe we can install spconv using a vendor package, as shown in the example. Would you like to take care of this task? I can try to look into it as well, but I can’t promise when - sorry.

[knzo25]

@esteve
spconv depends on cuda. did that not made it not possible?

[esteve]

@knzo25 I'm sorry I don't follow your question. Both cumm and spconv could be built either from source or from our Debian buildfarm, which supports CUDA too.

I created a simple vendor package for cumm (see https://github.com/esteve/cumm_vendor) that only exports the header files, I was going to do another package for spconv, but I can't reproduce the steps in https://github.com/autowarefoundation/spconv_cpp/blob/main/HOW_TO_UPDATE.md, the instructions seems out of date and can't be reproduced in an empty Docker container.

[amadeuszsz]

@esteve

the instructions seems out of date and can't be reproduced in an empty Docker container.

Could you please try apt install cuda-nvrtc-dev-12-4 first and let us know about an error?