On 01/23/19 17:13, Laszlo Ersek wrote:
> FWIW, I've asked
>
> - both on edk2-devel, about adding .NOTPARALLEL to the generated inner
> makefiles:
>
> "parallelism in the module-level, generated GNUmakefile's"
> https://lists.01.org/pipermail/edk2-devel/2019-January/035463.html
>
> - and on
On 01/22/19 13:02, Laszlo Ersek wrote:
> On 01/21/19 20:30, Peter Maydell wrote:
>> On Mon, 21 Jan 2019 at 19:09, Laszlo Ersek wrote:
>>> It wasn't clear to me whether and how multi-threaded builds were
>>> supposed to be used by maintainers, whenever they'd update
>>>
On 01/21/19 20:30, Peter Maydell wrote:
> On Mon, 21 Jan 2019 at 19:09, Laszlo Ersek wrote:
>> It wasn't clear to me whether and how multi-threaded builds were
>> supposed to be used by maintainers, whenever they'd update
>> "tests/data/uefi-boot-images/*".
>>
>> I saw that "make" was invoked
On Mon, 21 Jan 2019 at 19:09, Laszlo Ersek wrote:
> It wasn't clear to me whether and how multi-threaded builds were
> supposed to be used by maintainers, whenever they'd update
> "tests/data/uefi-boot-images/*".
>
> I saw that "make" was invoked everywhere as $(MAKE), but that didn't
> clarify
On 01/21/19 13:17, Philippe Mathieu-Daudé wrote:
> Hi Laszlo,
>
> On 1/18/19 11:33 PM, Laszlo Ersek wrote:
>> Introduce the following build scripts under "tests/uefi-test-tools":
>>
>> * "build.sh" builds a single module (a UEFI application) from
>> UefiTestToolsPkg, for a single QEMU emulation
Hi Laszlo,
On 1/18/19 11:33 PM, Laszlo Ersek wrote:
> Introduce the following build scripts under "tests/uefi-test-tools":
>
> * "build.sh" builds a single module (a UEFI application) from
> UefiTestToolsPkg, for a single QEMU emulation target.
>
> "build.sh" relies on cross-compilers when
Introduce the following build scripts under "tests/uefi-test-tools":
* "build.sh" builds a single module (a UEFI application) from
UefiTestToolsPkg, for a single QEMU emulation target.
"build.sh" relies on cross-compilers when the emulation target and the
build host architecture don't