From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Dariqq <dariqq@posteo.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
73028@debbugs.gnu.org,
"Florian Pelz" <pelzflorian@pelzflorian.de>
Subject: [bug#73028] [PATCH] doc: Document usage of #:out-of-source? for meson-build-system.
Date: Sat, 14 Sep 2024 22:41:16 +0900 [thread overview]
Message-ID: <87plp6s683.fsf@gmail.com> (raw)
In-Reply-To: <8a62a876-58e8-401f-9716-9b661bd008f5@posteo.net> (dariqq@posteo.net's message of "Thu, 12 Sep 2024 19:19:02 +0000")
Hi Dariqq,
Dariqq <dariqq@posteo.net> writes:
> On 12.09.24 14:02, Maxim Cournoyer wrote:
>> Hi Dariqq,
>> Dariqq <dariqq@posteo.net> writes:
>> [...]
>>
>>>>> Maybe it should not be an option at all and instead be #t
>>>>> unconditionally in 'install-license-files phase in meson-build-system?
>>>> Given most build phases of the gnu-build-system, which support
>>>> #:out-of-source? are reused in the meson-build-system, this argument
>>>> needs to be set to #t (which it currently is). But perhaps there's a
>>>> way to hide it from the users, perhaps via the 'private-keywords'
>>>> variable defined in the 'lower' procedure of the (guix build-system
>>>> meson) module (I haven't tested).
>>>>
>>>
>>> Something like that might be a better solution. I am not sure how
>>> these 'private-keywords' work: It looks like #:meson is one but you
>>> can definitly override the default meson being used. Also the
>>> private-arguments seem to get stripped from the arguments in the bag
>>> (not sure what that is exactly) so they might not be passed to the
>>> build phases
>> I think your understanding is correct. The private options are
>> accepted
>> on the build system, but not propagated to the lower build strata
>> (applied to phases). So what we'd like here is to *not* expose an
>> #:out-of-source argument at the build system level, and enforce
>> #:out-of-source #t for the lower build code. I guess the static #t
>> argument could be added to the bag arguments.
>>
>
> This does not work. I tried adding that to the arguments in the bag
> (and reverting the previous patch) but get an error:
>
> Unrecognized keyword: #:out-of-source?
>
> I guess this is because meson-(cross-)build now get a keyword they
> don't know.
Hm. Thanks for trying it out.
> Maybe we could replace the install-license-files function with a
> version that has #:out-of-source? set to #t?. Not sure if there is an
> elegant way to do this?
Is this really the only reused phase from gnu-build-system that makes
use of #:out-of-source? I'd expect the 'configure' to be one, also.
And in general it'd be a bit more risky; new gnu-build-system phases
that would make use of #:out-of-source could start breaking in the
future until thye are specially handled.
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-09-14 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 16:26 [bug#73028] [PATCH] doc: Document usage of #:out-of-source? for meson-build-system Dariqq
2024-09-11 6:09 ` Maxim Cournoyer
2024-09-11 15:18 ` Dariqq
2024-09-12 0:56 ` Maxim Cournoyer
2024-09-12 7:12 ` Dariqq
2024-09-12 12:02 ` Maxim Cournoyer
2024-09-12 19:19 ` Dariqq
2024-09-14 13:41 ` Maxim Cournoyer [this message]
2024-09-19 14:07 ` Dariqq
2024-09-22 5:57 ` 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=87plp6s683.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=73028@debbugs.gnu.org \
--cc=dariqq@posteo.net \
--cc=ludo@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).