From: John Soo <jsoo1@asu.edu>
To: "Todor Kondić" <tk.code@protonmail.com>
Cc: "help-guix\\@gnu.org" <help-guix@gnu.org>
Subject: Re: Non-standard builds, autoconf and gcc
Date: Wed, 2 Oct 2019 09:25:28 -0700 [thread overview]
Message-ID: <5F8A99D6-C2C3-4440-A193-D51040D96CA2@asu.edu> (raw)
In-Reply-To: <UZZmKOucmS9CsdGdB6N4ayL_qrsV-O46ZW8mm_9Ew0QKL6liilCZUrEKrrIZaAfdr2x-F3iikev8k9pSm_IfIZNgCGEXL6FvLcKC4xwptts=@protonmail.com>
Hi Todor,
> I am trying to define a package that builds a source which has
>
> a non-standard build procedure. It's a mix of autotools packages and something else. My first attempt was to use the trivial builder...
What is the something else? If it the shape of the build follows the gnu steps with some extra autotools, you may be able to use modify-phases. You would get the majority of the unpacking, replacement of relevant paths, and more. Then you could add some extra steps to work in the autotools specifics. My experience with the trivial builder is that it is best for union builds and copying some files but not much more.
Good luck,
John
next prev parent reply other threads:[~2019-10-02 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 13:49 Non-standard builds, autoconf and gcc Todor Kondić
2019-10-02 16:25 ` John Soo [this message]
2019-10-14 20:29 ` Maxim Cournoyer
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=5F8A99D6-C2C3-4440-A193-D51040D96CA2@asu.edu \
--to=jsoo1@asu.edu \
--cc=help-guix@gnu.org \
--cc=tk.code@protonmail.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.
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).