Looking for a previous version.

[bulldogc]

I am trying to grab the latest version of this that will build/run off of ros-melodic. Yes I am aware that is very end of life but it is what it is. I wonder if there might be a convenient way for me to track the right dependency versions if I pulled down an older version? Currently targeting like version 0.18.1 since that seems to be the last point before the cmake versions update past ubuntu18.

[Levi-Armstrong]

You may be able to use the latest if you pip install cmake to get the latest version of cmake and then pull tesseract_ext and update it to point the correct version to build dependencies from source.

[gavanderhoorn]

I am trying to grab the latest version of this that will build/run off of ros-melodic. Yes I am aware that is very end of life but it is what it is

maybe not: what is the reason you are limited to Melodic?

If it's because of robot drivers fi: as long as the message/service/action definitions haven't changed, you should be able to get things to communicate.

There are quite a few nuances when it comes to inter-ROS-distro compatibility, but it can sometimes be made to work.

You'll have to share a bit more information though.

[bulldogc]

OS restrictions on the hardware prevent going over melodic and we can't raise up the cmake release due to project restrictions, so I am stuck at 3.10.2 there.

[gavanderhoorn]

That's not really what I meant.

Docker/LXC/some_other_container_technology fi is often used to work around such restrictions, or running only certain parts of the application on the 'old system', and the rest on a more modern one (perhaps even in a container again).

ROS is multi-host by default. If possible, exploit it.

If you could share a little more information about the hardware and its context, perhaps better guidance/ideas could be offered.

As an example: I run ROS 2 Jazzy on a Clearpath Boxer with pre-2.4 hardware, which was (and still is) running ROS Kinetic originally (that's Ubuntu 16.04, so pre-Melodic even).

[bulldogc]

We are using a custom robot running on a jetson TX2. Getting a container on it might be technologically possible but not contractually feasible for the moment. For all intents and purposes stuck with U18, Cmake 3.10 and what ever we can get melodic to build/run on its own ros master essentially. Currently we are using a fairly ancient version of teseract cobbled together somewhere in 2019 and I am working in bringing it slightly more up to date.

[gavanderhoorn]

Doesn't have to be a full blown container. Perhaps something which brings its own runtime environment could work, such as Conda (RoboStack) or a home grown approach (dynamic linker wrapper and shipping everything to the target except the kernel). I'm using the second approach on a different system.

As long as you only need topics, services and/or actions (ie: no linking), that could/should work.