New ROS release?

[sea-bass]

Hi all! We just switched from OSQP to ProxQP for a project and got some really nice results.

However, we're noticing some behavior changes in the released rosdistro binaries (0.6.5) which are improved in the latest release (0.7.3) -- would the maintainers be willing to bloom new releases for the next sync?

Thank you for this fantastic library.

[sea-bass]

BTW, having gone through this myself, you will probably not be able to bloom a new version of this package to ROS 2 Humble because nanobind-dev is not available as an apt package on Ubuntu 22.04... assuming you are releasing with Python bindings built.

In the case of my project (RoboPlan) I basically am just not supporting Humble for binary releases.

So probably the best bet is to release 0.7.x to Jazzy and newer, and leave Humble at 0.6.x... or if you're not releasing with bindings, you can also ignore me.

[nim65s]

Hi,

This is currently waiting for ros2-gbp/ros2-gbp-github-org#1075

0.6.5 did not have any python binding.

We can patch them out for humble, or add a FetchContent nanobind as fallback.

[sea-bass]

Thanks for the update!

Having also gone through this myself... FetchContent is also disabled on the ROS build farm :)

[nim65s]

interesting, I did not know, thanks :)

we still have nanobind as a submodule here, so this should work for now

[sea-bass]

Ah yeah, you might also need to get rid of that and instead add a <depend>nanobind-dev</depend>... which again, on Humble it still works via pip install but is just not releasable.

I am not clear if submodules are allowed either... I also went through this with the TOPPRA repo which I was submoduling and instead had to release as its own package.

Don't you love build systems? 😅

[nim65s]

I love the build systems that I can reproduce at home and confidently know if the thing I push has any chance to succeed or not :)

[nim65s]

Ok, so for now we have an error even on lyrical:
https://build.ros2.org/job/Lbin_uR64__proxsuite__ubuntu_resolute_amd64__binary/99/console

09:05:20 -- CMAKE_SYSTEM_PROCESSOR: x86_64
09:05:20 -- [Proxsuite] Using C++ standard: 17
09:05:20 CMake Error at /usr/share/cmake-4.2/Modules/FindPackageHandleStandardArgs.cmake:290 (message):
09:05:20   Could NOT find Simde (missing: Simde_INCLUDE_DIR)
09:05:20 
09:05:20       Reason given by package: Set BUILD_WITH_VECTORIZATION_SUPPORT=OFF or install Simde on your system.
09:05:20    If Simde is already installed, ensure that the CMake variable CMAKE_MODULE_PATH correctly points toward the location of FindSimde.cmake file.
09:05:20 
09:05:20 Call Stack (most recent call first):
09:05:20   /usr/share/cmake-4.2/Modules/FindPackageHandleStandardArgs.cmake:654 (_FPHSA_FAILURE_MESSAGE)
09:05:20   cmake-module/find-external/Simde/FindSimde.cmake:20 (find_package_handle_standard_args)
09:05:20   cmake-module/package-config.cmake:114 (find_package)
09:05:20   CMakeLists.txt:187 (ADD_PROJECT_DEPENDENCY)
09:05:20 
09:05:20 
09:05:20 -- Configuring incomplete, errors occurred!
09:05:20 	cd .obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt

Because https://github.com/ros2-gbp/proxsuite-release/blob/release/lyrical/proxsuite/package.xml#L29 does not have 2a63ea7#diff-37a67ff78eb7260214b323353263b9af40a2fa98719a1e81937fae0159df87a3R29 yet

So the best solution for this would be to make a new source release, @jorisv, when you are available :)

[jorisv]

Can we wait the merge of #437 ? It only missing your green light