From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#28840: openrct2 cannot find data-path Date: Fri, 20 Oct 2017 18:01:10 +0200 Message-ID: <87efpxvmex.fsf@gnu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44875) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e5ZkP-00010g-Uu for bug-guix@gnu.org; Fri, 20 Oct 2017 12:02:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e5ZkK-0004xm-KL for bug-guix@gnu.org; Fri, 20 Oct 2017 12:02:09 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:43868) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e5ZkK-0004xe-Hn for bug-guix@gnu.org; Fri, 20 Oct 2017 12:02:04 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e5ZkI-000836-8k for bug-guix@gnu.org; Fri, 20 Oct 2017 12:02:03 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: (Jelle Licht's message of "Sat, 14 Oct 2017 23:38:35 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Jelle Licht Cc: 28840@debbugs.gnu.org Hi Jelle, Jelle Licht skribis: > The recently committed (and awesome) openrct2 built correctly, > but cannot currently find the needed language and shader files > for the game and therefore crashes. To make it work, I currently > have to invoke it via a command like > `--openrct-data-path=3D/gnu/store/-openrct2-0.1.1/share/openrct2/', > which imho is not optimal. > > I dove into the source of openrct, and it seems there are still > some vestiges of the cmake flag we want, namely > ORCT2_RESOURCE_DIR. Sadly, support for configuring this variable > seems to have been removed about 4 months ago. > > I opened an issue upstream regarding this[1], but maybe there is > an easy workaround we can use until a fix is hopefully released. > I was thinking of either a phase which calls `wrap-program', or > adding the required flag back via a short snippet. Are you talking about the game assets, or is it something different? (Did you see the discussion at ?) Cheers, Ludo=E2=80=99.