Skip to content

Commit

Permalink
gazebo: use OGRE 1.9
Browse files Browse the repository at this point in the history 
This fixes a freeze when adding more than one light.
  • Loading branch information
@lopsided98
lopsided98 committed Mar 16, 2022
1 parent 22d0db7 commit b1a844a
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions pkgs/gazebo/default.nix
View file
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{ lib, mkDerivation, fetchurl, fetchpatch, cmake, pkg-config, ronn, libGL
, openal, hdf5, curl, tinyxml, tinyxml-2, libtar, gts, libusb1, qtbase, gdal
, libuuid, graphviz, libsForQt5, freeimage, boost, protobuf, sdformat, tbb
, ogre1_10, ffmpeg, ignition, ignition-cmake ? ignition.cmake0
, ogre1_9, ffmpeg, ignition, ignition-cmake ? ignition.cmake0
, ignition-common ? ignition.common, ignition-math ? ignition.math4
, ignition-transport ? ignition.transport8, ignition-msgs ? ignition.msgs
, ignition-fuel-tools ? ignition.fuel-tools4
Expand Down Expand Up @@ -70,7 +70,7 @@ mkDerivation rec {
protobuf
sdformat
tbb
ogre1_10
ogre1_9
ffmpeg
ignition-math
ignition-transport
Expand Down

2 comments on commit b1a844a

@jtojnar
Copy link
Contributor

@jtojnar jtojnar commented on b1a844a May 2, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you have a reproducer for this? ogre_1_9 has been recently dropped: NixOS/nixpkgs#222564

Or do you remember why you reverted the 1.12 bump? a405f62

@lopsided98
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See #260

Nixpkgs currently has Ogre 1.10 and 13. Gazebo fails to build with 13. Gazebo more or less works with 1.10, but adding more than one light causes it to freeze. There don't appear to be any plans to support newer versions, since Gazebo classic only has minimal maintenance now. I may have to maintain 1.9 in this overlay.

Please sign in to comment.