qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "qemu devel list" <qemu-devel@nongnu.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Igor Mammedov" <imammedo@redhat.com>
Subject: Re: [Qemu-devel] recursive submodules
Date: Wed, 6 Mar 2019 12:44:19 +0000	[thread overview]
Message-ID: <20190306124419.GG20806@redhat.com> (raw)
In-Reply-To: <32ad1a44-5398-53de-9adf-9e6ac9f60805@redhat.com>

On Wed, Mar 06, 2019 at 01:30:06PM +0100, Laszlo Ersek wrote:
> Hi,
> 
> in order to build any OVMF platform firmware image from the submodule at
> "roms/edk2", the (recursive) OpenSSL submodule at
> "roms/edk2/CryptoPkg/Library/OpensslLib/openssl" needs to be initialized
> as well.
> 
> Am I right to think this would be the first recursive submodule in QEMU?
> How should I approach this? (I see we have a related script at
> "scripts/git-submodule.sh".)

The scripts/git-submodule.sh file is called automatically by "make"
in QEMU to activate any submodules that are required during the normal
build a QEMU developer does.

The ROM submodules are special though. AFAIK, these are never built as a
side effect of the QEMU build process, so never need to be initialized by
the git-submodule.sh script.  Developers always just use the pre-built
ROM files bundled in QEMU. The only people checking out the ROM submodules
are the maintainers who periodically build a new binary ROM.

So in this sense the fact that EDK has submodules shouldn't be a factor,
as we would not expect EDK to be built by regular QEMU developers

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2019-03-06 12:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 12:30 [Qemu-devel] recursive submodules Laszlo Ersek
2019-03-06 12:44 ` Daniel P. Berrangé [this message]
2019-03-06 13:31   ` Laszlo Ersek
2019-03-06 14:55     ` Alex Bennée

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=20190306124419.GG20806@redhat.com \
    --to=berrange@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=lersek@redhat.com \
    --cc=philmd@redhat.com \
    --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).