From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Schultschik,
Sven (DI PA DCP R&D 2)" <sven.schultschik@siemens.com>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: [isar-cip-core][PATCH 2/7] add recipe for for edk2
Date: Wed, 19 Oct 2022 15:21:48 +0200 [thread overview]
Message-ID: <adbb2f61-391e-16c7-cd3e-0e12ebb65697@siemens.com> (raw)
In-Reply-To: <PAXPR10MB5037C43EAD82531EC11A63E3902B9@PAXPR10MB5037.EURPRD10.PROD.OUTLOOK.COM>
On 19.10.22 15:14, Schultschik, Sven (DI PA DCP R&D 2) wrote:
>
>
>> -----Ursprüngliche Nachricht-----
>> Von: Kiszka, Jan (T CED) <jan.kiszka@siemens.com>
>> Gesendet: Mittwoch, 19. Oktober 2022 12:58
>> An: Schultschik, Sven (DI PA DCP R&D 2) <sven.schultschik@siemens.com>; cip-
>> dev@lists.cip-project.org
>> Betreff: Re: [isar-cip-core][PATCH 2/7] add recipe for for edk2
>>
>> On 19.10.22 11:21, sven.schultschik@siemens.com wrote:
>>> From: Sven Schultschik <sven.schultschik@siemens.com>
>>> +MAINTAINER = "Sven Schultschik <sven.schultschik@siemens.com>"
>>> +LICENSE = "BSD-2-Clause-Patent"
>>> +
>>> +inherit dpkg
>>> +
>>> +SRC_URI =
>> "gitsm://github.com/tianocore/edk2.git;branch=master;protocol=https;destsuff
>> ix=git/edk2;rev=edk2-stable${PV} \
>>> +
>>> +git://github.com/tianocore/edk2-platforms.git;protocol=https;destsuff
>>> +ix=git/edk2-platforms;rev=3b896d1a325686de3942723c42f286090453e37a \
>>
>> - gitsm (see patch 1/7)
>
> EDK2 really uses submodules which need to be pulled
>
>> - please factor out revisions into separate variables
>>
>> Or can we also address the revisions via release tags? The recipe carries a
>> release version number in the end...
>>
>>> + file://debian \
>>> + "
>>> +S = "${WORKDIR}/git"
>>> +
>>> +BUILD_DEPENDS += ""
>>> +
>>> +TEMPLATE_FILES = "debian/changelog.tmpl debian/control.tmpl
>> debian/rules.tmpl"
>>> +TEMPLATE_VARS += "BUILD_DEPENDS S"
>>> +
>>> +ISAR_CROSS_COMPILE = "0"
>>
>> Why?
>
> EDK2 has it's own build parameter for the target architecture, which activates cross compile
> Within EDK2 build which breaks if isar cross is activated.
> build -p $(ACTIVE_PLATFORM) -b RELEASE -a $(TARGET_ARCH) -t GCC5 -n $(shell nproc)
>
> You suggest to turn it off and try if isar cross compile could be enough?
Cross-compile should give you some relevant toolchain bits and libs at
least. And it makes sure that you have a native toolchain for the build
environment, rather than running with emulation for that.
If you need different compiler settings, adjust the rules file.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-10-19 13:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 9:21 [isar-cip-core][PATCH 1/7] add recipe for optee qemu arm64 sven.schultschik
2022-10-19 9:21 ` [isar-cip-core][PATCH 2/7] add recipe for for edk2 sven.schultschik
2022-10-19 10:57 ` Jan Kiszka
2022-10-19 13:14 ` AW: " Schultschik, Sven
2022-10-19 13:21 ` Jan Kiszka [this message]
2022-10-20 17:59 ` Schultschik, Sven
2022-10-20 16:24 ` Schultschik, Sven
2022-10-21 6:57 ` Jan Kiszka
2022-10-19 9:21 ` [isar-cip-core][PATCH 3/7] add recipe for trusted firmware a qemu arm64 sven.schultschik
2022-10-19 9:21 ` [isar-cip-core][PATCH 4/7] add u-boot patch for qemu to support RPMB sven.schultschik
2022-10-19 9:21 ` [isar-cip-core][PATCH 5/7] add kas files for building qemu secure boot images sven.schultschik
2022-10-19 9:21 ` [isar-cip-core][PATCH 6/7] enhance start-qemu.sh for arm64 secure boot sven.schultschik
2022-10-19 9:21 ` [isar-cip-core][PATCH 7/7] no merge - manually instructions test " sven.schultschik
2022-10-19 10:44 ` [isar-cip-core][PATCH 1/7] add recipe for optee qemu arm64 Jan Kiszka
2022-10-19 10:46 ` Jan Kiszka
2022-10-19 13:05 ` AW: " Schultschik, Sven
2022-10-19 13:14 ` Jan Kiszka
2022-10-19 13:21 ` AW: " Schultschik, Sven
2022-10-19 13:24 ` Jan Kiszka
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=adbb2f61-391e-16c7-cd3e-0e12ebb65697@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=sven.schultschik@siemens.com \
/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