Dome support

[j-rivero]

This ticket tracks Dome support for various platforms.

• See all supported platforms for Dome on this page.
• See the definition of Ignition's support categories on this page.

---

Operating System	Architecture	Packaging	CI	Functionality
Ubuntu Bionic	amd64	✅ Yes	✅ Yes, every pull request	✅ All
.	i386	✅ Yes	No	✅ All
.	arm64	❓ Maybe	No	Most low-level libraries known to work
.	armhf	❓ Maybe	No	Most low-level libraries known to work, DART physics engine not available
Ubuntu Focal	amd64	✅ Yes	✅ Yes, every pull request	✅ All
.	arm64	❓ Maybe	No	Most low-level libraries known to work
.	armhf	❓ Maybe	No	Most low-level libraries known to work, DART physics engine not available
Debian Buster	amd64, i386, arm64, armhf	❓ Maybe	No	Several libraries known to work
MacOS Catalina and BigSur	-	✅ Yes	✅ Yes, every pull request	Ignition only works in headless mode (GUI does not render; instead of using ign gazebo fuel.sdf command, use ign gazebo -s fuel.sdf to start the server only).
Windows 10	.	❓ Maybe	Some libraries tested on every pull request	Command line utilities are not supported. All packages up to but not including ign-gazebo are currently building. DART physics engine is not supported. Qt (GUI functionality) is not supported.

---

There are some problems affecting different platforms in Dome:

Legend 🟢 in the repo 🟡 waiting in the buildfarm 🔴 requires action ⚫ no release

• Ubuntu amd64 platforms:

  • 🟢 Focal/amd64
  • 🟢 Bionic/amd64

• Ubuntu i386 platforms:

  • 🟢 Bionic/i386:

• Brew

  • 🟢 Bottles

• Ubuntu ARM platforms:

  • 🟢 Focal/arm64

  • 🟢 Bionic/arm64

  • ⚫ Focal/armhf:

    • Not supported (previous work: needs ign-gui4)

  • ⚫ Bionic/armhf:

    • Not support (previous work: missing dart packages from PPA are not in the repo)

• Debian i386 platforms:

  • ⚫ Not supported

• Debian amd64 platforms:

  • ⚫ Sid/*:
    • Not supported. Need to check conflicts with current libraries there
  • 🔴 Buster/amd64:
    • Patching pending: needs code fixes in ign-transport9 to use the right zmq code, mostly port Suppress focal-specific warnings gazebosim/gz-transport#159 to work with Debian too (see also issue ign-transport9 debbuilds failing on debian buster gazebosim/gz-transport#220).
      • debbuilder chain: ign-transport9 -> ign-gui4 -> ign-gazebo4

• Debian ARM platforms:

  • 🟡 Buster/arm64

    • ign-math6 built.

  • 🔴 Buster/armhf (raspbian)

    • ign-plugin
      • ogre-2.1
    • ign-rendering

/usr/bin/ld: CMakeFiles/ignition-rendering3.dir/TransformController.cc.o:(.rodata+0x0): multiple definition of `typeinfo name for ignition::rendering::v3::Store<ignition::rendering::v3::Scene>'; CMakeFiles/ignition-rendering3.dir/OrbitViewController.cc.o:(.rodata+0x0): first defined here
/usr/bin/ld: CMakeFiles/ignition-rendering3.dir/TransformController.cc.o:(.data.rel.ro+0x0): multiple definition of `typeinfo for ignition::rendering::v3::Store<ignition::rendering::v3::Scene>'; CMakeFiles/ignition-rendering3.dir/OrbitViewController.cc.o:(.data.rel.ro+0x0): first defined here

[chapulina]

Why is Buster/armhf a candidate to exclusion? We already have some debs for it:

[j-rivero]

Why is Buster/armhf a candidate to exclusion? We already have some debs for it:

My impression is that the level of buster/armhf users does not worth the effort of the maintenance cost. Just an impression.

[chapulina]

My impression is that the level of buster/armhf users does not worth the effort of the maintenance cost

Got it, I was mainly wondering if it was a technical reason. Agreed that we can leave it out for now.

[ruffsl]

Isn't the current version of raspbian based on buster?

• https://www.raspberrypi.org/blog/buster-the-new-version-of-raspbian/

Seems like that could shutout a lot of students using the default armhf image.

[j-rivero]

Isn't the current version of raspbian based on buster?

* https://www.raspberrypi.org/blog/buster-the-new-version-of-raspbian/

Seems like that could shutout a lot of students using the default armhf image.

I think that it is a good reason to build them. Thanks Ruffin.

[j-rivero]

@chapulina my impression at this point would be to reduce the number of platforms supported to:

• U, Focal (amd64, arm64)
• U. Bionic (amd64, i386, arm64)
• D. Buster (amd64, armhf)

Reasons are mainly maintenance costs (patches needed and releasing times for arm*) and no evidence of active use base for the rest of platforms at this moment.

[chapulina]

Ok, so you're suggesting we drop:

• U, Focal (armhf)
• U, Bionic (armhf)
• D, Buster (arm64. i386)

I think this is ok for now. If users come asking for other combinations we can look into it.

What do you think of updating the docs to include Buster once that's done?

https://ignitionrobotics.org/docs/dome/install

[scpeters]

I just saw a debbuild failure of ign-common3 on buster armhf:

• https://build.osrfoundation.org/job/ign-common3-debbuilder/975/

The following tests FAILED:
	  5 - UNIT_Console_TEST (Failed)
	  9 - UNIT_Filesystem_TEST (Failed)
	 66 - UNIT_ColladaLoader_TEST (Failed)
Errors while running CTest

maybe a filesystem or permissions problem?

[chapulina]

Closing this ticket as Dome is about to EOL (#600) and we've made the final releases. Here's the status of Linux releases at EOL: