unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jelle Licht <wordempire@gmail.com>
To: 28840@debbugs.gnu.org
Subject: bug#28840: openrct2 cannot find data-path
Date: Sat, 14 Oct 2017 23:38:35 +0200	[thread overview]
Message-ID: <CAPsKtfK2-k95SJCjjAb6_uXkBwDXeFNEDFak7GCFts2A7xRP3Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 940 bytes --]

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=/gnu/store/<hash>-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.

- Jelle


[1]: https://github.com/OpenRCT2/OpenRCT2/issues/6473


p.s. Besides these rather small issues, I can confirm that OpenRCT2
works.

[-- Attachment #2: Type: text/html, Size: 1333 bytes --]

             reply	other threads:[~2017-10-14 21:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-14 21:38 Jelle Licht [this message]
2017-10-20 16:01 ` bug#28840: openrct2 cannot find data-path Ludovic Courtès
2017-10-20 16:37   ` Jelle Licht
2017-10-20 20:21     ` Ludovic Courtès
2017-10-21  8:44       ` Rutger Helling
2017-10-26 12:18         ` Jelle Licht
2017-10-26 17:27           ` Ludovic Courtès
2017-10-26 18:10             ` Jelle Licht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPsKtfK2-k95SJCjjAb6_uXkBwDXeFNEDFak7GCFts2A7xRP3Q@mail.gmail.com \
    --to=wordempire@gmail.com \
    --cc=28840@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).