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
Currently the ignition-tools code generates a CMake/pkg-config module installed in the system with minimal information (package is pure ruby), the rest of the Ignition family is detecting at building time if ignition-tools is present on the system and installing the corresponding submodule for ign tool. This can be suboptimal:
build time to decide if an user wants or not the ign submodule is not the best moment.
ign modules are cheap in every sense (small ruby files)
Let's remove the check and install ign submodules files unconditionally:
fuel 1
fuel 5 : forward --> 6, main
gui 3 : forward --> 4, 5, main
msgs 1
msgs 5 : forward --> 6, 7, main
sdformat 6
sdformat 9
sdformat 12, main
transport 4
transport 8 : forward --> 9, 10, main
gazebo / sim 3
launch 2
The text was updated successfully, but these errors were encountered:
Currently the ignition-tools code generates a CMake/pkg-config module installed in the system with minimal information (package is pure ruby), the rest of the Ignition family is detecting at building time if ignition-tools is present on the system and installing the corresponding submodule for ign tool. This can be suboptimal:
Let's remove the check and install ign submodules files unconditionally:
The text was updated successfully, but these errors were encountered: