Merge remote-tracking branch 'upstream/rolling' into banisadr/foxglov…

…e-updates

Merging latest from rolling

source/Concepts/Basic/About-Client-Libraries.rst

@@ -73,15 +73,16 @@ Community-maintained
 
 While the C++ and Python client libraries are maintained by the core ROS 2 team, members of the ROS 2 community maintain additional client libraries:
 
+* `Ada <https://github.com/ada-ros/ada4ros2>`__  This is a set of packages (binding to ``rcl``, message generator, binding to ``tf2``, examples and tutorials) that allows the writing of Ada applications for ROS 2.
 * `C <https://github.com/ros2/rclc>`__  ``rclc`` does not put a layer on top of rcl but complements rcl to make rcl+rclc a feature-complete client library in C. See `micro.ros.org <https://micro.ros.org/>`__ for tutorials.
 * `JVM and Android <https://github.com/ros2-java>`__ Java and Android bindings for ROS 2.
 * `.NET Core, UWP and C# <https://github.com/esteve/ros2_dotnet>`__ This is a collection of projects (bindings, code generator, examples and more) for writing ROS 2 applications for .NET Core and .NET Standard.
 * `Node.js <https://www.npmjs.com/package/rclnodejs>`__ rclnodejs is a Node.js client for ROS 2. It provides a simple and easy JavaScript API for ROS 2 programming.
 * `Rust <https://github.com/ros2-rust/ros2_rust>`__ This is a set of projects (the rclrs client library, code generator, examples and more) that enables developers to write ROS 2 applications in Rust.
+* `Flutter and Dart <https://github.com/rcldart>`__ Flutter and Dart bindings for ROS 2.
 
 Older, unmaintained client libraries are:
 
-* `Ada <https://github.com/ada-ros/ada4ros2>`__
 * `C# <https://github.com/firesurfer/rclcs>`__
 * `Objective C and iOS <https://github.com/esteve/ros2_objc>`__
 * `Zig <https://github.com/jacobperron/rclzig>`__

source/Concepts/Intermediate/About-Different-Middleware-Vendors.rst

@@ -83,3 +83,9 @@ For example, if both ``rmw_cyclonedds_cpp`` and ``rmw_connextdds`` ROS packages
 If ``rmw_fastrtps_cpp`` is ever installed, it would be the default.
 
 See the :doc:`guide <../../How-To-Guides/Working-with-multiple-RMW-implementations>` for how to specify which RMW implementation is to be used when running the ROS 2 examples.
+
+Cross-Vendor Communication
+--------------------------
+
+While different RMW implementations may be compatible in limited circumstances, this is not guaranteed.
+Thus it is suggested that users ensure that all parts of the distributed system are using the same ROS version and the same RMW implementation.

source/Concepts/Intermediate/About-RQt.rst

@@ -51,11 +51,6 @@ Installing From debs
    sudo apt install ros-{DISTRO}-rqt*
 
 
-Building From Source
-^^^^^^^^^^^^^^^^^^^^
-
-See :doc:`Building RQt from Source <../../How-To-Guides/RQt-Source-Install>`.
-
 RQt Components Structure
 ------------------------
 

source/How-To-Guides.rst

@@ -36,7 +36,6 @@ If you are new and looking to learn the ropes, start with the :doc:`Tutorials <T
    How-To-Guides/Cross-compilation
    How-To-Guides/Releasing/Releasing-a-Package
    How-To-Guides/Using-Python-Packages
-   How-To-Guides/RQt-Port-Plugin-Windows
    How-To-Guides/Run-2-nodes-in-single-or-separate-docker-containers
    How-To-Guides/Visualizing-ROS-2-Data-With-Foxglove
    How-To-Guides/Core-maintainer-guide
@@ -53,8 +52,3 @@ If you are new and looking to learn the ropes, start with the :doc:`Tutorials <T
    How-To-Guides/ROS-2-IDEs
    How-To-Guides/Setup-ROS-2-with-VSCode-and-Docker-Container
    How-To-Guides/Using-Custom-Rosdistro
-
-.. toctree::
-  :hidden:
-
-  How-To-Guides/RQt-Source-Install

source/How-To-Guides/Installation-Troubleshooting.rst

@@ -240,25 +240,6 @@ To resolve this error, you will need to:
 
    $ sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
 
-qt_gui_cpp error: SIP binding generator NOT available
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-.. only relevant to Eloquent and Foxy
-
-When building qt_gui_cpp there may be errors look like the following:
-
-.. code-block:: bash
-
-   --- stderr: qt_gui_cpp
-
-   CMake Error at src/CMakeLists.txt:10 (message):
-     No Python binding generator found.
-
-   ---
-   Failed   <<< qt_gui_cpp [ Exited with code 1 ]
-
-To fix this issue, follow :doc:`these steps <RQt-Source-Install-MacOS>` to install dependencies for RQt.
-
 rosdep install error ``homebrew: Failed to detect successful installation of [qt5]``
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 While following the :doc:`Creating a workspace <../Tutorials/Beginner-Client-Libraries/Creating-A-Workspace/Creating-A-Workspace>` tutorial, you might encounter the following error stating that ``rosdep`` failes to install Qt5.

source/How-To-Guides/Launch-file-different-formats.rst

@@ -45,7 +45,7 @@ Each launch file performs the following actions:
         from launch.substitutions import LaunchConfiguration
         from launch.substitutions import TextSubstitution
         from launch_ros.actions import Node
-        from launch_ros.actions import PushRosNamespace
+        from launch_ros.actions import PushROSNamespace
         from launch_xml.launch_description_sources import XMLLaunchDescriptionSource
         from launch_yaml.launch_description_sources import YAMLLaunchDescriptionSource
 
@@ -82,8 +82,8 @@ Each launch file performs the following actions:
             # include a Python launch file in the chatter_py_ns namespace
             launch_py_include_with_namespace = GroupAction(
                 actions=[
-                    # push_ros_namespace to set namespace of included nodes
-                    PushRosNamespace('chatter_py_ns'),
+                    # push_ros_namespace first to set namespace of included nodes for following actions
+                    PushROSNamespace('chatter_py_ns'),
                     IncludeLaunchDescription(
                         PythonLaunchDescriptionSource(
                             os.path.join(
@@ -96,8 +96,8 @@ Each launch file performs the following actions:
             # include a xml launch file in the chatter_xml_ns namespace
             launch_xml_include_with_namespace = GroupAction(
                 actions=[
-                    # push_ros_namespace to set namespace of included nodes
-                    PushRosNamespace('chatter_xml_ns'),
+                    # push_ros_namespace first to set namespace of included nodes for following actions
+                    PushROSNamespace('chatter_xml_ns'),
                     IncludeLaunchDescription(
                         XMLLaunchDescriptionSource(
                             os.path.join(
@@ -110,8 +110,8 @@ Each launch file performs the following actions:
             # include a yaml launch file in the chatter_yaml_ns namespace
             launch_yaml_include_with_namespace = GroupAction(
                 actions=[
-                    # push_ros_namespace to set namespace of included nodes
-                    PushRosNamespace('chatter_yaml_ns'),
+                    # push_ros_namespace first to set namespace of included nodes for following actions
+                    PushROSNamespace('chatter_yaml_ns'),
                     IncludeLaunchDescription(
                         YAMLLaunchDescriptionSource(
                             os.path.join(

source/How-To-Guides/Migrating-from-ROS1.rst

@@ -8,7 +8,9 @@ If you are new to porting between ROS 1 and ROS 2, it is recommended to read thr
    :maxdepth: 1
 
    Migrating-from-ROS1/Migrating-Packages
+   Migrating-from-ROS1/Migrating-Package-XML
    Migrating-from-ROS1/Migrating-Interfaces
+   Migrating-from-ROS1/Migrating-CPP-Package-Example
    Migrating-from-ROS1/Migrating-CPP-Packages
    Migrating-from-ROS1/Migrating-Python-Packages
    Migrating-from-ROS1/Migrating-Launch-Files