Reenable UWP Builds for Foxy

Question

Reenable UWP Builds for Foxy

ooeygui opened this issue 2 years ago · 6 comments

The ROS2.net UWP builds are not functioning due to ROS2 itself failing to build on the Universal Windows Platform. An effort is under way to upstream ROS2 for UWP, after which time the ROS2.net UWP builds can be reenabled.

Here are the tracking repositories for the various ROS2 on UWP changes:
https://github.com/ms-iot/Fast-DDS.git
https://github.com/ms-iot/rcpputils.git
https://github.com/ms-iot/rcutils.git
https://github.com/ms-iot/libyaml_vendor.git
https://github.com/ms-iot/poco_vendor.git

Answer 1 · 2022-04-21T21:21:52.000Z

During the process of upstreaming these changes, it was discovered that poco_vendor has been archived, instead relying on the OS libraries. Poco itself has not been UWP enabled. UWP has been grafted on - including with poco_vendor and vcpkg.

@esteve I'd like to propose creating a fork of https://github.com/ros2/poco_vendor in the ros2_dotnet organization, which can host poco for UWP changes which are currently in ms-iot until official support is available. I'd also like input on alternative approaches.

Answer 2 · 2022-05-09T21:34:15.000Z

First PRs are pulled into humble. Working on next batch.

Answer 3 · 2022-05-10T07:25:06.000Z

@ooeygui no problem about the poco_vendor fork, but it seems that https://github.com/ros2/poco_vendor has been archived. Is it still being used by ROS2? I think the only part of POCO in use was for dynamically loading a library, which was replaced by calling dlopen / LoadLibrary directly.

Answer 4 · 2022-05-10T16:47:28.000Z

@esteve Let me check on that.

Answer 5 · 2023-11-06T19:34:06.000Z

@ooeygui Are there more details about what's blocking UWP builds, and what would be necessary for builds on Humble and later?

Answer 6 · 2023-11-06T20:28:35.000Z

Hi @ronwalf,
I wish I could continue to work on this.

There are core changes in ROS and the Middleware that make them compatible with the Hololens 2 app container model (which is different than the Hololens 1 app container). I've made those changes in the ms-iot forks, but I have not propagated them upstream into rolling. The code in the forks is "Proof of concept" quality, so need to have effort put into unit tests, and multiplaform testing before they can be PR'd into their respective repos. I don't know what the delta is to migrate the changes to current releases.