kyle-basis
kyle-basis
> > I'm happy to do the legwork to write my own CMake file, integration, etc - but I'd like to avoid forking the core library itself. Would a PR...
I don't mind forking as long as eventually my fork and upstream converge, sounds good.
Did some more work on this - found two more areas that depends on ROS - logging and the CMake file itself. Both of those are by necessity compile time...
I don't have a desire to introduce complexity to TF either. CMake - I want to do something like this: ``` FetchContent_Declare( tf2 GIT_REPOSITORY https://github.com/ros2/geometry2.git SOURCE_SUBDIR tf2 ) FetchContent_MakeAvailable(tf2) ```...
That would work for me. Sent from my iPhoneOn Nov 13, 2024, at 6:07 PM, Chris Lalancette ***@***.***> wrote: and have it compile as a standalone library. This might require...
Copying the ros types out is something I'm not excited to do - it means that now I always go through an additional copy, from the internal to the ROS...
Only test fails are due to linting - do y'all have a script to fix this automatically?
Linting fixed - not sure why tf2_rospy is failing on jenkins, though