I believe certain issues related to using Chrono::ROS in external projects are also due to an incomplete set up of this module in the Chrono project configuration file.
Harry – I will provide you with an updated configuration template file. If you could test that and confirm that it addresses the issues raised by Madhava I will push it to the main Chrono branch.
--Radu
--
You received this message because you are subscribed to the Google Groups "ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
projectchron...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/projectchrono/002309e7-74ff-4572-a719-39079c3734a5n%40googlegroups.com.
Hi Giri,
Are you using the latest code in the ‘main’ branch of the Chrono GitHub repository? There were some recent commits addressing issues related to this kind of use of the Chrono::ROS module.
If yes, the Chrono CMake project configuration script should be tweaked a little bit more to pass a default for the ROS2_DIR path (Aaron, if you are reading this, could you please look into this?)
But even without that, the solution seems quite straightforward: during CMake configuration of your project, fill in the ROS2_DIR with the path where the CMake configuration files for ROS are located. You must have done this already when you configured Chrono with the ROS module enabled. Simply put in here the same path as you did when configuring Chrono.
--Radu
To view this discussion visit https://groups.google.com/d/msgid/projectchrono/10bec892-65d2-492f-ba01-82aaa30f24d5n%40googlegroups.com.