You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I was wondering if it’s possible to set up this package to compile custom source code when running make px4_sitl gz_<model>.
For example, when creating custom vehicles like the Advanced Plane in the docs, you need to compile a custom Gazebo plugin. I’m also planning to develop a USV (Unmanned Surface Vehicle) for PX4 simulation using the USV models and plugins from osrf/vrx.
Instead of working on plugins directly in the upstream Gazebo repo, it seems more common now to keep custom plugins in the project repo and compile them there. This is actually encouraged in the Gazebo project template.
My idea is to add a src folder to include custom plugins and scripts, and have any needed code in there compiled when running make px4_sitl gz_<model>.
Let me know what you think about this approach!
Edit: I didn't mean to discourage contribution on the upstream Gazebo repo, but this approach allows flexibility in building custom vehicles that require custom plugins.
The text was updated successfully, but these errors were encountered:
Hi,
I was wondering if it’s possible to set up this package to compile custom source code when running
make px4_sitl gz_<model>
.For example, when creating custom vehicles like the Advanced Plane in the docs, you need to compile a custom Gazebo plugin. I’m also planning to develop a USV (Unmanned Surface Vehicle) for PX4 simulation using the USV models and plugins from osrf/vrx.
Instead of working on plugins directly in the upstream Gazebo repo, it seems more common now to keep custom plugins in the project repo and compile them there. This is actually encouraged in the Gazebo project template.
My idea is to add a
src
folder to include custom plugins and scripts, and have any needed code in there compiled when runningmake px4_sitl gz_<model>
.Let me know what you think about this approach!
Edit: I didn't mean to discourage contribution on the upstream Gazebo repo, but this approach allows flexibility in building custom vehicles that require custom plugins.
The text was updated successfully, but these errors were encountered: