Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supporting Fedora Asahi Remix #939

Closed
peterdavidfagan opened this issue Feb 9, 2024 · 3 comments · Fixed by ros-infrastructure/rospkg#265
Closed

Supporting Fedora Asahi Remix #939

peterdavidfagan opened this issue Feb 9, 2024 · 3 comments · Fixed by ros-infrastructure/rospkg#265

Comments

@peterdavidfagan
Copy link

peterdavidfagan commented Feb 9, 2024

I wish to debug and develop ROS 2 code on my MacbookAir with Fedora Asahi Remix but currently this aarch-based distribution is not recognised by rosdep.

Update: I realise this may be more of a rospkg issue, as os_detect is imported from this package.

@cottsay
Copy link
Member

cottsay commented Feb 10, 2024

I realise this may more of a rospkg issue, as os_detect is imported from this package.

Doing it properly requires both. We want rospkg to know the difference between Fedora and Fedora Asahi Remix, but as it stands right now, we want rosdep to treat both distributions the same since they'll contain the same packages.

@peterdavidfagan
Copy link
Author

peterdavidfagan commented Feb 10, 2024

In the interim I got things running by editing the release files (super suboptimal but I wanted to see if drivers worked as expected for GPU). Foxglove + mujoco sim works:

foxglove_on_mac

Further update: many ROS package dependencies don't seem to have releases for fedora though :(. I also tried Asahi Ubuntu but it only supports 23.10.

@tfoote
Copy link
Member

tfoote commented Mar 1, 2024

For short term workarounds you can use the ROS_OS_OVERRIDE to force the detection or the --os= option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants