From: Simon Glass <sjg@chromium.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PULL 2/3] edk2: replace build scripts
Date: Tue, 21 Mar 2023 08:19:09 +1300 [thread overview]
Message-ID: <CAPnjgZ2eFezH4JrtAU08o2BujZyfc+Do2bPVTOJUEtWevjdGZA@mail.gmail.com> (raw)
In-Reply-To: <20230315154914.d2st3c6ioy62cku3@sirius.home.kraxel.org>
Hi Gerd,
On Thu, 16 Mar 2023 at 04:49, Gerd Hoffmann <kraxel@redhat.com> wrote:
>
> Hi,
>
> > The README should mention that you need to use
> >
> > . edk2setup.sh
> >
> > first.
>
> The script will do that if needed.
>
> > Also you need to be in the edk2 directory, I think.
>
> Or use the --core switch, or place the location in the config file in
> the [global] section.
That seems to be resolved with the latest script.
>
> > It would be good if the edk2-clone.sh script could deal with updating
> > an existing checkout so I don't need to remove the old ones each time.
>
> Updating is just "git pull && git submodules update".
Even more reason to put it in the script :-)
>
> > edk2-build.py -c ../edk2-build-config/kraxel/x64.platforms -j30 --silent
>
> That config file expects cwd being edk2-platforms and edk2 being placed
> next to it (../ekd2). edk2-non-osi too. See the [global] section at
> the start of the file.
OK I see.
>
> > BaseTools/BuildEnv: 160: Bad substitution
> > Using Pip Basetools
> > BaseTools/BuildEnv: 184: Bad substitution
> > BaseTools/BuildEnv: 202: -c: not found
>
> Ok, tried updated the script to use bash not sh for that. Does this
> work better for you?
Yes, fixed.
>
> > Do I need to make -C BaseTools first?
>
> No, the script will do that.
Seems to work fine now.
>
> > > +import optparse
> >
> > I think this is obsolete and argparse should be used for new things.
> > The conversion is pretty easy.
>
> Done.
>
OK
> > Silent mode still produces output. Can you add a -s alias and also
> > make it fully silent?
>
> Well, silent means no output from the "build" command, so the console is
> not flooded with build logs (unless there are build errors), output is
> written to logfiles instead.
We have a different understanding of 'silent' ::-)
>
> > If the config file is not found, it seems to say nothing, but just
> > does not work. It should give an error.
>
> Fixed.
Works fine.
Thanks for the great script and the fixes.
Regards,
Simon
next prev parent reply other threads:[~2023-03-20 19:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 11:57 [PULL 0/3] Edk2 stable202302 20230309 patches Gerd Hoffmann
2023-03-09 11:57 ` [PULL 1/3] edk2: update submodule to edk2-stable202302 Gerd Hoffmann
2023-03-09 11:57 ` [PULL 2/3] edk2: replace build scripts Gerd Hoffmann
2023-03-10 13:58 ` Simon Glass
2023-03-15 15:49 ` Gerd Hoffmann
2023-03-20 19:19 ` Simon Glass [this message]
2023-03-09 11:57 ` [PULL 3/3] edk2: update firmware binaries Gerd Hoffmann
2023-03-09 22:09 ` Simon Glass
2023-03-10 6:37 ` Gerd Hoffmann
2023-03-10 21:00 ` Simon Glass
2023-03-10 11:30 ` [PULL 0/3] Edk2 stable202302 20230309 patches Peter Maydell
2023-03-10 13:09 ` Philippe Mathieu-Daudé
2023-03-15 15:56 ` Gerd Hoffmann
2023-03-15 16:16 ` Laszlo Ersek
2023-03-16 7:55 ` Gerd Hoffmann
2023-03-10 13:18 ` Philippe Mathieu-Daudé
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=CAPnjgZ2eFezH4JrtAU08o2BujZyfc+Do2bPVTOJUEtWevjdGZA@mail.gmail.com \
--to=sjg@chromium.org \
--cc=kraxel@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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).