From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105532] Broken map generation in Northgard game
Date: Fri, 29 Jun 2018 17:47:13 +0000 [thread overview]
Message-ID: <bug-105532-502-MNSusMXKTb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105532-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 686 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105532
--- Comment #7 from Christian Lanig <freedesktop@lanig.email> ---
(In reply to Alexander Tsoy from comment #5)
> (In reply to Christian Lanig from comment #4)
> There are native linux binaries in the linux subfolder.
Yes. You are right. I renamed Northgard.exe and the game still starts. I
thought that Haxe would somewhere start the Windows binary after loading the
data file because shipping it to Linux users didn't make that much sense to me.
I'm sorry for the confusion.
Still, Haxe might be useful to localize the roots of the issue.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1570 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-06-29 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 22:10 [Bug 105532] Broken map generation in Northgard game bugzilla-daemon
2018-03-15 22:21 ` bugzilla-daemon
2018-06-08 8:51 ` bugzilla-daemon
2018-06-27 5:25 ` bugzilla-daemon
2018-06-29 17:14 ` bugzilla-daemon
2018-06-29 17:24 ` bugzilla-daemon
2018-06-29 17:32 ` bugzilla-daemon
2018-06-29 17:47 ` bugzilla-daemon [this message]
2018-07-21 9:09 ` bugzilla-daemon
2018-07-21 15:17 ` bugzilla-daemon
2018-07-25 4:41 ` bugzilla-daemon
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=bug-105532-502-MNSusMXKTb@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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.
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.