public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "tlaronde@polynum.com" <tlaronde@polynum.com>
To: devel@edk2.groups.io, gaoliming@byosoft.com.cn
Cc: "'Bob Feng'" <bob.c.feng@intel.com>,
	"'Yuwei Chen'" <yuwei.chen@intel.com>
Subject: Re: [edk2-devel] ??: [PATCH 1/1] BaseTools: remove useless header inclusion
Date: Sun, 29 Jan 2023 10:45:02 +0100	[thread overview]
Message-ID: <Y9ZAHruDIm4aOK8F@polynum.com> (raw)
In-Reply-To: <011101d93385$52b411e0$f81c35a0$@byosoft.com.cn>

Hello,

Le Sun, Jan 29, 2023 at 09:59:29AM +0800, gaoliming via groups.io a écrit :
> With this change, does GenFv pass build on Linux environment?

It should: there is absolutely nothing in GenFvInternalLib.c using
uuid_* or UUID_*. Furthermore, the API exposed by FreeBSD uuid.h and
util-linux-ng uuid/uuid.h are totally different; so this is why I
wondered, from the start, what the inclusions were achieving.

If the Linux build should fail, this would be by side-effect because a
header included via uuid.h is missing.

I can not test a Linux environment: I have none.

BTW, in the patch, I should have removed the -luuid in GNUMakefile too.

> 
> > -----????-----
> > ???: tlaronde@polynum.com <tlaronde@polynum.com>
> > ????: 2023?1?26? 18:03
> > ???: devel@edk2.groups.io
> > ??: Bob Feng <bob.c.feng@intel.com>; Liming Gao
> > <gaoliming@byosoft.com.cn>; Yuwei Chen <yuwei.chen@intel.com>
> > ??: [PATCH 1/1] BaseTools: remove useless header inclusion
> > 
> > GenFvInternalLib.c: useless inclusion and dependency on uuid.h.
> > 
> > From 6c0ba96fa11390750e102ebd277f59ef38970394 Mon Sep 17 00:00:00
> > 2001
> > From: Thierry LARONDE <tlaronde@polynum.com>
> > Date: Thu, 26 Jan 2023 10:49:12 +0100
> > Subject: [PATCH] Remove useless uuid.h include.
> > 
> > Signed-off-by: Thierry LARONDE <tlaronde@polynum.com>
> > ---
> >  BaseTools/Source/C/GenFv/GenFvInternalLib.c | 5 -----
> >  1 file changed, 5 deletions(-)
> > 
> > diff --git a/BaseTools/Source/C/GenFv/GenFvInternalLib.c
> > b/BaseTools/Source/C/GenFv/GenFvInternalLib.c
> > index 6bd59515b1..2df7182f8b 100644
> > --- a/BaseTools/Source/C/GenFv/GenFvInternalLib.c
> > +++ b/BaseTools/Source/C/GenFv/GenFvInternalLib.c
> > @@ -14,11 +14,6 @@ SPDX-License-Identifier: BSD-2-Clause-Patent
> >  // Include files
> >  //
> > 
> > -#if defined(__FreeBSD__)
> > -#include <uuid.h>
> > -#elif defined(__GNUC__)
> > -#include <uuid/uuid.h>
> > -#endif
> >  #ifdef __GNUC__
> >  #include <sys/stat.h>
> >  #endif
> > --
> > 2.39.0
> > 
> > --
> >         Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
> >                      http://www.kergis.com/
> >                     http://kertex.kergis.com/
> > Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C
> 
> 
> 
> 
> 
> 
> 

-- 
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                     http://www.kergis.com/
                    http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C

  reply	other threads:[~2023-01-29  9:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 10:03 [PATCH 1/1] BaseTools: remove useless header inclusion tlaronde
2023-01-29  1:59 ` 回复: " gaoliming
2023-01-29  9:45   ` tlaronde [this message]
2023-01-30  6:42     ` [edk2-devel] ??: " Bob Feng

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-list 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=Y9ZAHruDIm4aOK8F@polynum.com \
    --to=devel@edk2.groups.io \
    /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