From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Question about use of xxxMACHINExxx
Date: Mon, 08 Jul 2024 14:59:47 +0100 [thread overview]
Message-ID: <8A595DF1-45F7-449A-94A0-8A1864D411C6@ipfire.org> (raw)
In-Reply-To: <11cab218-f901-4b7a-b2ed-5c017adb4710@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]
Hello Adolf,
Sorry for not being faster at this… Still catching up :)
This is basically a variable which used to be called MACHINE but was replaced with xxxMACHINExxx because the string “MACHINE” was actually used in some filename. Not sure I am happy with that name…
When the root files are generated, we don’t replace anything, but if we read a rootfile from config/rootfiles, we will replace this variable with the architecture we are building for. Sometimes this method allows us to have just a generic root file for all architectures, sometimes this does not work because there are extra files or something like that.
So when you have such a case, you need to manually replace the architecture with the placeholder and check if all other architectures generate the same file.
-Michael
> On 5 Jul 2024, at 11:39, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi All,
>
> When a rootfile is in one of the specific architecture directories, e.g. aarch64 do all the aarch64 references just get left as that or should they get changed to xxxMACHINExxx.
>
> Looking at some files in the directories it looks like they get left alone but when I have done the samba rootfile update for x86_64 I have , most times, changed any x86_64 reference to xxxMACHINExxx.
>
> What is the correct approach so I don't go messing things up.
>
> Regards,
>
> Adolf
>
next prev parent reply other threads:[~2024-07-08 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 10:39 Adolf Belka
2024-07-08 13:59 ` Michael Tremer [this message]
2024-07-08 14:51 ` Adolf Belka
2024-07-08 15:42 ` Michael Tremer
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=8A595DF1-45F7-449A-94A0-8A1864D411C6@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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