Humble development container fails to build beluga_vdb when following instructions in DEVELOPING.md

[glpuga]

Bug description

The repository fails to build beluga_vdb when using the ROS Humble image, doing:

. /opt/ros/${ROS_DISTRO}/setup.bash
cd /ws
colcon build --symlink-install

as per DEVELOPING.md instructions.

Platform (please complete the following information):

• OS: [e.g. Ubuntu Focal]
• Beluga version: [e.g. tag, commit sha]

How to reproduce

Start docker humble container, and do:

. /opt/ros/${ROS_DISTRO}/setup.bash
cd /ws
colcon build --symlink-install

Expected behavior

All packages build cleanly.

Actual behavior

Additional context

[glpuga]

@hidmic should this package build in Humble?

[hidmic]

It would if OpenVDB was properly packaged on Jammy. It's not. Thus why:

beluga/tools/build-and-test.sh

Lines 33 to 35 in c91454c

	if [ "${ROS_DISTRO}" != "humble" ] && [ "${ROS_DISTRO}" != "iron" ]; then
	ROS_PACKAGES="beluga beluga_ros beluga_amcl beluga_system_tests beluga_tools beluga_vdb"
	fi

only builds it for Noble. We can do better than this though. We could build and install it from source from within the container.

Anyways, yes, we missed updating DEVELOPING.md when #440 went in.

[hidmic]

Hmm, after some thought, I think the proper solution here (other than branching, which I'd very much try to avoid) is to:

• Install from OpenVDB from sources within the Jammy container.
• Add instructions on how to install OpenVDB from sources on Jammy (in the beluga_vdb README)
• Add a note in DEVELOPING.md about skipping beluga_vdb builds unless either of the above are satisfied (using COLCON_IGNORE or else)

FYI @pvela2017

[pvela2017]

Hmm, after some thought, I think the proper solution here (other than branching, which I'd very much try to avoid) is to:

• Install from OpenVDB from sources within the Jammy container.
• Add instructions on how to install OpenVDB from sources on Jammy (in the beluga_vdb README)
• Add a note in DEVELOPING.md about skipping beluga_vdb builds unless either of the above are satisfied (using COLCON_IGNORE or else)

FYI @pvela2017

Hi!

I can work on this !