From: Ricardo Wurmus <rekado@elephly.net>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: New build-system quest (premake4 t-engine)
Date: Thu, 20 Jul 2017 15:08:13 +0200 [thread overview]
Message-ID: <878tjjfe82.fsf@elephly.net> (raw)
In-Reply-To: <87shi6fxf0.fsf@gmail.com>
Hi Oleg,
> I try to package premake4 build-system and t-engine game. I have an
> issue with "No such file or directory" "../bla/bla/bla/*.h".
[…]
>
> But building with guix build failed. Checkout patch and logs. Any
> ideas appreciating :-)
Have you tried using the “gnu-build-system” and replacing the configure
phase with your invocation of premake4?
One difference between “guix build” and “guix environment” is that the
latter builds a profile first, so environment variables for libraries or
headers really only have to be set to a single directory
(e.g. $GUIX_ENVIRONMENT/lib or $GUIX_ENVIRONMENT/include).
“guix build”, on the other hand, builds up long chains of directories as
the values for these environment variables.
> ./pre-inst-env guix environment -C t-engine
> source ./environment-variables
> cd t-engine*
> make
> succeeded.
Did you not have to run premake4 first? If you don’t need it then it
would be sufficient to use the gnu-build-system and delete the configure
phase.
(I don’t think we need a new build system for the case where just the
configure phase differs slightly, but maybe I’m missing something.)
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-07-20 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 21:20 New build-system quest (premake4 t-engine) Oleg Pykhalov
2017-07-20 13:08 ` Ricardo Wurmus [this message]
2017-07-24 21:08 ` Oleg Pykhalov
2017-07-25 21:18 ` Ricardo Wurmus
2017-07-26 6:25 ` Oleg Pykhalov
2017-07-26 8:51 ` Ricardo Wurmus
2017-07-26 12:54 ` Oleg Pykhalov
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=878tjjfe82.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=go.wigust@gmail.com \
--cc=guix-devel@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).