From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Quentin Schulz" <quentin.schulz@cherry.de>,
<docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 3/6] overview-manual: convert configuration-compile-autoreconf.png to svg
Date: Mon, 24 Feb 2025 11:37:10 +0100 [thread overview]
Message-ID: <D80LZCBAIW4S.1NEGX4Z5BGFPG@bootlin.com> (raw)
In-Reply-To: <4fc256cb-9ecb-4f75-8f11-72ee88fa517d@cherry.de>
Hi Quentin,
On Mon Feb 24, 2025 at 11:26 AM CET, Quentin Schulz wrote:
> Hi Antonin,
>
> On 2/24/25 10:19 AM, Antonin Godard wrote:
>> Hi Quentin,
>>
>> On Thu Feb 20, 2025 at 5:13 PM CET, Quentin Schulz wrote:
>>> Hi Antonin,
>>>
>>> On 2/18/25 10:11 AM, Antonin Godard via lists.yoctoproject.org wrote:
>>>> Convert the png file to an SVG file, and add the UNPACKDIR reference.
>>>>
>>>
>>> The arrows for the build directory are misaligned, especially for the
>>> machine-specific package.
>>
>> Yes, I noticed afterwards too. There were some font issues, rsvg-convert was not
>> properly picking them up. And also having so many arrows require precision that
>> is not taken into account when converting from SVGs to PNGs.
>>
>> In the end, I think having the different arrows as text (for the rightmost part)
>> is much better and will always meet the alignment no matter what the font is.
>> E.g:
>>
>> ${PV} -------- WORKDIR
>>
>
> Maybe
>
> ${PV} <------- WORKDIR
>
> ?
Yes, that sounds good.
>
>> So now the output is this:
>> https://lufi.bootlin.com/r/EuK0sscTNP#uV4rb2CQCPCMXONMGiBTfR9PY8BTDm0g0xeIAI+AsH8=
>>
>> What do you think?
>>
>
> I do not see much of a difference with "real" arrows, so that's fine by
> me :)
>
>>> I'm also a bit skeptical about the position of the star before
>>> EXTRA_OECONF, it feels like it's somehow part of the variable name.
>>> Maybe add a space or make the star appear a bit higher (like in the
>>> current PNG?).
>>
>> I will adjust that.
>>
>>> A remark for the original content as well, but I don't really understand
>>> why B isn't passed to do_configure and do_install as well? Isn't it
>>> where build artifacts will be configured before do_compile runs and from
>>> where do_install will run in order to install files into $D?
>>>
>>> do_configure[dirs] = "${B}"
>>> do_install[dirs] = "${B}"
>>>
>>> in base.bbclass for example.
>>>
>>> I'm wondering also if we shouldn't have a bidirectional arrow for B for
>>> the configure and compile task as they are run from there, i.e. they
>>> generate files in there as well?
>>
>> I agree, B is used in all three.
>>
>> For do_install, I guess a unidirectional arrow would make more sense as D is
>> already used to point towards the other way.
>>
>
> Unidirectional D arrow makes sense to me as there's nothing D before
> do_install I think?
Yes that's what I meant, I think the current figure looks good. Just missing B
in the other way. Sorry if that wasn't clear.
> Now to come to think of it, I'm not sure there's anything in B before
> do_configure? So should we have unidirectional for do_configure and
> bidirectional for do_compile?
True I also agree.
Thanks for your feedback, appreciate it :)
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-02-24 10:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 9:11 [PATCH 0/6] Updates around the UNPACKDIR variable Antonin Godard
2025-02-18 9:11 ` [PATCH 1/6] overview-manual: convert source-fetching.png to svg and fix UNPACKDIR Antonin Godard
2025-02-20 16:03 ` [docs] " Quentin Schulz
2025-02-18 9:11 ` [PATCH 2/6] overview-manual: convert patching.png to svg Antonin Godard
2025-02-20 16:05 ` [docs] " Quentin Schulz
2025-02-18 9:11 ` [PATCH 3/6] overview-manual: convert configuration-compile-autoreconf.png " Antonin Godard
2025-02-20 16:13 ` [docs] " Quentin Schulz
2025-02-24 9:19 ` Antonin Godard
2025-02-24 10:26 ` Quentin Schulz
2025-02-24 10:37 ` Antonin Godard [this message]
2025-02-18 9:11 ` [PATCH 4/6] overview-manual: convert analysis-for-package-splitting.png " Antonin Godard
2025-02-20 16:18 ` [docs] " Quentin Schulz
2025-02-24 10:44 ` Antonin Godard
2025-02-24 10:48 ` Quentin Schulz
2025-02-18 9:12 ` [PATCH 5/6] overview-manual: add UNPACKDIR in the directory description Antonin Godard
2025-02-20 16:22 ` [docs] " Quentin Schulz
2025-02-18 9:12 ` [PATCH 6/6] ref-manual/variables: improve the UNPACKDIR documentation Antonin Godard
2025-02-20 16:41 ` [docs] " Quentin Schulz
2025-02-24 10:53 ` Antonin Godard
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=D80LZCBAIW4S.1NEGX4Z5BGFPG@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@cherry.de \
--cc=thomas.petazzoni@bootlin.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 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.