From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: doxygen: add documentation
Date: Thu, 25 May 2023 20:29:23 +0200 [thread overview]
Message-ID: <20230525182923.eO3w_P6lorZ3EHEJ6Lxa4jsu3_FghontndV8YpcSBOk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44079@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
New comment by meator on void-packages repository
https://github.com/void-linux/void-packages/pull/44079#issuecomment-1563331927
Comment:
Ugh. This happens every time. Why do build systems always want to execute the program they are building?
This isn't my first time in the rodeo. AFAIK there are two solutions to this: `build_helper=qemu` and stuff `vtargetrun`
somewhere in doxygen's build system or make doxygen depend on itself (the cross version on the native version) and then use native version's files in the cross package. I would prefer the second solution because I am not familiar with doxygen's build system.
I don't want to invest time into this if it will be rejected so: Will this be rejected? Is this too hacky for void-packages?
Offline documentation is really nice.
next prev parent reply other threads:[~2023-05-25 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 17:58 [PR PATCH] " meator
2023-05-25 18:29 ` meator [this message]
2023-05-27 16:34 ` meator
2023-05-27 18:26 ` [PR PATCH] [Updated] " meator
2023-05-31 11:23 ` [PR PATCH] [Updated] doxygen: update + " meator
2023-05-31 11:26 ` meator
2023-05-31 11:26 ` meator
2023-07-30 14:21 ` meator
2023-10-29 1:45 ` doxygen: " github-actions
2023-11-12 1:46 ` [PR PATCH] [Closed]: " github-actions
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=20230525182923.eO3w_P6lorZ3EHEJ6Lxa4jsu3_FghontndV8YpcSBOk@z \
--to=meator@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).