From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Question about use of xxxMACHINExxx Date: Mon, 08 Jul 2024 14:59:47 +0100 Message-ID: <8A595DF1-45F7-449A-94A0-8A1864D411C6@ipfire.org> In-Reply-To: <11cab218-f901-4b7a-b2ed-5c017adb4710@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2284724831227761473==" List-Id: --===============2284724831227761473== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Adolf, Sorry for not being faster at this=E2=80=A6 Still catching up :) This is basically a variable which used to be called MACHINE but was replaced= with xxxMACHINExxx because the string =E2=80=9CMACHINE=E2=80=9D was actually= used in some filename. Not sure I am happy with that name=E2=80=A6 When the root files are generated, we don=E2=80=99t 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 w= ith the placeholder and check if all other architectures generate the same fi= le. -Michael > On 5 Jul 2024, at 11:39, Adolf Belka wrote: >=20 > Hi All, >=20 > When a rootfile is in one of the specific architecture directories, e.g. aa= rch64 do all the aarch64 references just get left as that or should they get = changed to xxxMACHINExxx. >=20 > 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. >=20 > What is the correct approach so I don't go messing things up. >=20 > Regards, >=20 > Adolf >=20 --===============2284724831227761473==--