On 06/03/20 13:44, Leif Lindholm wrote:
> On Tue, Jun 02, 2020 at 18:20:26 +0200, Laszlo Ersek wrote:
>> On 06/02/20 16:20, Leif Lindholm wrote:
>>> On Tue, Jun 02, 2020 at 15:29:55 +0200, Laszlo Ersek wrote:
I have not been aware of the header name collision scenario (nor that
the
On Tue, Jun 02, 2020 at 18:20:26 +0200, Laszlo Ersek wrote:
> On 06/02/20 16:20, Leif Lindholm wrote:
> > On Tue, Jun 02, 2020 at 15:29:55 +0200, Laszlo Ersek wrote:
> >> I have not been aware of the header name collision scenario (nor that
> >> the [Packages] ordering was supposed to work around
> On Jun 2, 2020, at 8:33 PM, Andrew Fish via groups.io
> wrote:
>
>
>
>> On May 29, 2020, at 7:02 AM, Leif Lindholm wrote:
>>
>> The description of [Packages] sections stated that
>> "Packages must be listed in the order that may be required for specifying
>> include path statements for
> On May 29, 2020, at 7:02 AM, Leif Lindholm wrote:
>
> The description of [Packages] sections stated that
> "Packages must be listed in the order that may be required for specifying
> include path statements for a compiler. For example, the
> MdePkg/MdePkg.dec file must be listed before the
> >>
> >> (since I've been copied)
> >>
> >> I have not been aware of the header name collision scenario (nor that
> >> the [Packages] ordering was supposed to work around such issues).
> >>
> >> I work strictly with edk2 proper, where a name collision like this can
> >> be detected, and so should
On 06/02/20 16:20, Leif Lindholm wrote:
> On Tue, Jun 02, 2020 at 15:29:55 +0200, Laszlo Ersek wrote:
>> I have not been aware of the header name collision scenario (nor that
>> the [Packages] ordering was supposed to work around such issues).
>
> Nor had I...
>
>> I work strictly with edk2
nsal (OSS)
>>
>> Subject: Re: [edk2-devel] [PATCH edk2-InfSpecification] Drop statement on
>> package ordering
>>
>> On 06/01/20 00:43, Leif Lindholm wrote:
>>> Hi Mike,
>>>
>>> Ok, I'm happy to hear that.
>>>
>>> I agree that the
Hi Pankaj,
On Tue, Jun 02, 2020 at 13:37:30 +, Pankaj Bansal (OSS) wrote:
> > How about replacing
> >
> > """
> > Packages must be listed in the order that may be required for specifying
> > include path statements for a compiler. For example, the MdePkg/MdePkg.dec_
> > file must be listed
On Tue, Jun 02, 2020 at 15:29:55 +0200, Laszlo Ersek wrote:
> I have not been aware of the header name collision scenario (nor that
> the [Packages] ordering was supposed to work around such issues).
Nor had I...
> I work strictly with edk2 proper, where a name collision like this can
> be
> -Original Message-
> From: Laszlo Ersek
> Sent: Tuesday, June 2, 2020 7:00 PM
> To: Leif Lindholm ; devel@edk2.groups.io;
> michael.d.kin...@intel.com
> Cc: Andrew Fish ; Pankaj Bansal (OSS)
>
> Subject: Re: [edk2-devel] [PATCH edk2-InfSpecification] Dro
On 06/01/20 00:43, Leif Lindholm wrote:
> Hi Mike,
>
> Ok, I'm happy to hear that.
>
> I agree that the overriding behaviour is useful, and it would be good
> to document it. The problem is that the current wording does not say
> that (in a way that is useful to anyone who does not already know
> From: Kinney, Michael D
> > Sent: Monday, June 1, 2020 10:45 AM
> > To: Pankaj Bansal (OSS) ;
> Leif Lindholm
> > ; devel@edk2.groups.io; Kinney,
> Michael D
> >
> > Cc: Andrew Fish ; Laszlo Ersek
>
> > Subject: RE: [edk2-devel] [PATCH edk2-
> Inf
w Fish ; Laszlo Ersek
> Subject: RE: [edk2-devel] [PATCH edk2-InfSpecification] Drop statement on
> package ordering
>
> Pankaj Bansal,
>
> The override package should be listed before the standard package
> in the [Packages] section of an INF file.
>
> The internal behav
0 8:39 PM
> To: Leif Lindholm ;
> devel@edk2.groups.io; Kinney, Michael D
>
> Cc: Andrew Fish ; Laszlo Ersek
> ; Pankaj Bansal (OSS)
>
> Subject: RE: [edk2-devel] [PATCH edk2-InfSpecification]
> Drop statement on package ordering
>
> Hi Mike,
>
> T
: Leif Lindholm
> Sent: Monday, June 1, 2020 4:14 AM
> To: devel@edk2.groups.io; michael.d.kin...@intel.com
> Cc: Andrew Fish ; Laszlo Ersek ; Pankaj
> Bansal (OSS)
> Subject: Re: [edk2-devel] [PATCH edk2-InfSpecification] Drop statement on
> package ordering
>
> Hi Mi
Hi Mike,
Ok, I'm happy to hear that.
I agree that the overriding behaviour is useful, and it would be good
to document it. The problem is that the current wording does not say
that (in a way that is useful to anyone who does not already know what
it means). And the MdePkg/MdeModulePkg example
Hi Leif,
The reason for this statement is not for performance.
It is if the same include file exists in the same path
in more than one package. Defining this behavior makes
the build system deterministic.
There is use case where a platform package can provide
an include override of a common
The description of [Packages] sections stated that
"Packages must be listed in the order that may be required for specifying
include path statements for a compiler. For example, the
MdePkg/MdePkg.dec file must be listed before the
MdeModulePkg/MdeModulePkg.dec file."
Drop it.
Signed-off-by:
18 matches
Mail list logo
