From: Markus Klotzbuecher <mk@mkio.de>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: naming of link to fitImage with initramfs
Date: Fri, 1 Mar 2019 16:45:01 +0100 [thread overview]
Message-ID: <20190301154501.GA24139@e460.mkio.de> (raw)
Hello everyone
After updating to thud, I noticed that the naming of the softlink to a
fitImage with an INITRAMFS_IMAGE effectively changed from the form
fitImage-${INITRAMFS_IMAGE}-${MACHINE}.bin
to
fitImage-${INITRAMFS_IMAGE}-${MACHINE}-${MACHINE}
This happens because the latter is constructed in
kernel-fitimage.bbclass as
fitImage-${INITRAMFS_IMAGE_NAME}-${KERNEL_FIT_LINK_NAME}
where kernel.bbclass sets:
INITRAMFS_IMAGE_NAME ?= ${INITRAMFS_IMAGE}-${MACHINE}
and kernel-artifact-names.bbclass defines:
KERNEL_FIT_LINK_NAME ?= "${KERNEL_ARTIFACT_LINK_NAME}"
and
KERNEL_ARTIFACT_LINK_NAME ?= "${MACHINE}"
leading ${MACHINE} being added two times.
Is this intentional or am I missing something? I'm not attached to the
old naming, but the double MACHINE in the link seems a bit odd.
Thanks in advance!
Best regards
Markus
--
Markus Klotzbuecher
Freelancer Embedded, Distributed & Real-time Systems
Am See 28, 78465 Konstanz, Germany
reply other threads:[~2019-03-01 15:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190301154501.GA24139@e460.mkio.de \
--to=mk@mkio.de \
--cc=openembedded-core@lists.openembedded.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