From: Vivien Kraus <vivien@planete-kraus.eu>
To: Maxime Devos <maximedevos@telenet.be>, guile-user <guile-user@gnu.org>
Subject: Re: Does the eval-when example work?
Date: Fri, 21 Oct 2022 19:41:28 +0200 [thread overview]
Message-ID: <4cc167d9a1131484b6539957ee48d36a48421e74.camel@planete-kraus.eu> (raw)
In-Reply-To: <0be9df35-559e-3c06-a190-1cb30f84daa6@telenet.be>
Le jeudi 20 octobre 2022 à 10:53 +0200, Maxime Devos a écrit :
> If so, this is not exactly what I am looking for. I am looking for a
> > way to run the (date) form during the compilation phase, and save
> > the
> > date to the compilation unit so that it does not change. Is this
> > possible?
>
> I don't know the answer, but for (bit-for-bit) reproducibility,
> please
> support something like
> <https://reproducible-builds.org/docs/source-date-epoch/>.
I have to confess, I lied to you. I’m not interested in the compilation
date. What I want is to encode the typelib path at compile time, so I
can tell guile-gi where to find the typelibs (including the recursive
pkg-config requirements). Now that I know how to do that, I don’t have
to propagate any inputs, and I don’t have to keep pkg-config around at
run-time (except if the compilation cache gets invalidated, but who
does that).
prev parent reply other threads:[~2022-10-21 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 20:32 Does the eval-when example work? Vivien Kraus
2022-10-19 20:47 ` Jean Abou Samra
2022-10-22 13:26 ` Jean Abou Samra
2022-10-20 8:53 ` Maxime Devos
2022-10-21 17:41 ` Vivien Kraus [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4cc167d9a1131484b6539957ee48d36a48421e74.camel@planete-kraus.eu \
--to=vivien@planete-kraus.eu \
--cc=guile-user@gnu.org \
--cc=maximedevos@telenet.be \
/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).