From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: hedgewars: fix ppc build
Date: Wed, 25 Dec 2019 14:28:19 +0100 [thread overview]
Message-ID: <20191225132819.QYV0EdcUrSaIlQ67jNwUZQpL_218suqTjeOcepb6AXc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17759@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
New comment by nashimus on void-packages repository
https://github.com/void-linux/void-packages/pull/17759#issuecomment-568899735
Comment:
Thank you for the suggestions. I wasn't aware of the state of fpc on other archs, that's good to know, it would be nice to fix it for as many as possible.
[Hedgewars pas2CTutorial](https://www.hedgewars.org/kb/pas2CTutorial)
> Pas2C is an alternative way to build the engine. It is disabled by default.
>
> Pas2C is intended to be used when building the engine natively (e.g. with FreePascal) fails for some reason. However, Pas2C does have some limitations and you should try to first build Hedgewars normally before attempting a Pas2C build.
>
> Pas2C is our hand-written Pascal-to-C-compiler. It works by converting all Pascal code to C, and then compiling the C code with a C compiler. Pas2C itself is written in Haskell. Yes, we're a little crazy. :-)
>The Pas2C build currently doesn't support the video recorder.
next prev parent reply other threads:[~2019-12-25 13:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 18:19 [PR PATCH] " voidlinux-github
2019-12-24 18:32 ` voidlinux-github
2019-12-24 18:35 ` voidlinux-github
2019-12-24 18:36 ` voidlinux-github
2019-12-25 13:28 ` voidlinux-github [this message]
2019-12-25 16:45 ` [PR PATCH] [Updated] " voidlinux-github
2019-12-25 23:14 ` voidlinux-github
2019-12-26 1:46 ` [PR PATCH] [Updated] " voidlinux-github
2019-12-26 11:22 ` voidlinux-github
2019-12-26 11:23 ` [PR PATCH] [Merged]: " voidlinux-github
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=20191225132819.QYV0EdcUrSaIlQ67jNwUZQpL_218suqTjeOcepb6AXc@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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 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 NNTP newsgroup(s).