From: ludo@gnu.org (Ludovic Courtès)
To: Jelle Licht <wordempire@gmail.com>
Cc: 28840@debbugs.gnu.org
Subject: bug#28840: openrct2 cannot find data-path
Date: Fri, 20 Oct 2017 18:01:10 +0200 [thread overview]
Message-ID: <87efpxvmex.fsf@gnu.org> (raw)
In-Reply-To: <CAPsKtfK2-k95SJCjjAb6_uXkBwDXeFNEDFak7GCFts2A7xRP3Q@mail.gmail.com> (Jelle Licht's message of "Sat, 14 Oct 2017 23:38:35 +0200")
Hi Jelle,
Jelle Licht <wordempire@gmail.com> 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=/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.
Are you talking about the game assets, or is it something different?
(Did you see the discussion at
<https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28794#8>?)
Cheers,
Ludo’.
next prev parent reply other threads:[~2017-10-20 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 21:38 bug#28840: openrct2 cannot find data-path Jelle Licht
2017-10-20 16:01 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efpxvmex.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28840@debbugs.gnu.org \
--cc=wordempire@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.