From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Jack Hill <jackhill@jackhill.us>
Cc: guix-devel@gnu.org
Subject: Re: Help me create a janet-build-system
Date: Sat, 15 May 2021 21:55:20 +0200 [thread overview]
Message-ID: <28180c9b9b7306bc6b8f9cdc370006d62a2fcf8c.camel@student.tugraz.at> (raw)
In-Reply-To: <alpine.DEB.2.21.2105151515460.2109@marsh.hcoop.net>
Am Samstag, den 15.05.2021, 15:25 -0400 schrieb Jack Hill:
> Leo,
>
> Thanks for your reply
>
> On Sat, 15 May 2021, Leo Prikler wrote:
>
> > Your code imports (guix utils), but (guix utils) is not present
> > within
> > the module closure present at build time.
> > Did you mean (guix build utils)?
>
> I used cc-for-target and cxx-for-target from (guix utils). Where
> would I add (guix utils) so it is included on the build side?
In my opinion, these flags ought to be added on the build-system side
of things, not on the build side. There you can just add those two
flags to the ones already provided by the package.
> > > More generally, I expect there are many ways I could improve the
> > > build system. What are they?
> > I know little about jpm, but in my opinion you ought to let the
> > user
> > customize the flags passed on to jpm at least in the build target
> > --
> > not so sure about check and install. If janet-build-system allows
> > some
> > degree of customization, consider also letting the user override
> > the
> > test-target.
>
> I think I should at least try to make the with-toolchain package
> transformation option work. Beyond that, I'm not sure how much
> customization jpm offers without editing project.janet. [...]
If certain guixy things would require you to edit/create that file, you
should do that. I think ant-build-system does something similar.
Regards,
Leo
prev parent reply other threads:[~2021-05-15 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 5:07 Help me create a janet-build-system Jack Hill
2021-05-15 7:00 ` Leo Prikler
2021-05-15 19:25 ` Jack Hill
2021-05-15 19:55 ` Leo Prikler [this message]
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=28180c9b9b7306bc6b8f9cdc370006d62a2fcf8c.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=guix-devel@gnu.org \
--cc=jackhill@jackhill.us \
/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.