All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Einar Jón" <tolvupostur@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next v3 1/5] package/ti-sgx-libgbm: new package
Date: Tue, 21 Jan 2020 13:07:52 +0100	[thread overview]
Message-ID: <CABhNV23HS7e1iVj=YLMc6d4SWTgNr3YELVCKfLuuE5BZRKwfgw@mail.gmail.com> (raw)
In-Reply-To: <20191230150107.29c15d37@windsurf>

Hello Lothar

Sorry for the late reply.

The ti-sgx-{km, um, demos} update is great, but why do you need the libgbm
repo?
The  ti-sgx-um repo has had it's own libgbm internally for a while (binary
file
build/ti-sgx-um-2a2e5bb090ced870d73ed4edbc54793e952cc6d8/targetfs/ti335x/lib/libgbm.so.1.0.0).
This repo is a year and a half old.

Can't we drop this one and replace BR2_PACKAGE_TI_SGX_LIBGBM
with BR2_PACKAGE_TI_SGX_UM
where it is referenced?

Best regards,
Einar J?n

On Mon, 30 Dec 2019 at 15:01, Thomas Petazzoni <thomas.petazzoni@bootlin.com>
wrote:

> On Fri, 15 Nov 2019 09:49:57 -0300
> unixmania at gmail.com wrote:
>
> > diff --git a/package/Config.in b/package/Config.in
> > index f72c77b416..0a0499421c 100644
> > --- a/package/Config.in
> > +++ b/package/Config.in
> > @@ -541,6 +541,7 @@ endmenu
> >       source "package/ti-sgx-demos/Config.in"
> >       source "package/ti-sgx-km/Config.in"
> >       source "package/ti-sgx-um/Config.in"
> > +     source "package/ti-sgx-libgbm/Config.in"
>
> Alphabetic ordering here was not good (reported by check-package).
>
> > diff --git a/package/ti-sgx-libgbm/Config.in
> b/package/ti-sgx-libgbm/Config.in
> > new file mode 100644
> > index 0000000000..33014b2ed3
> > --- /dev/null
> > +++ b/package/ti-sgx-libgbm/Config.in
> > @@ -0,0 +1,6 @@
> > +config BR2_PACKAGE_TI_SGX_LIBGBM
> > +     bool "ti-sgx-libgbm"
>
> Missing:
>
>         depends on BR2_TOOLCHAIN_HAS_THREADS
>         depends on BR2_PACKAGE_HAS_UDEV
>         select BR2_PACKAGE_LIBDRM
>
> to follow the dependencies of the .mk file.
>
> > +# Extract the license from the gbm.h header instead of distributing the
> whole
> > +# file. This is safe because if the terms change in the header the
> sha256 hash
> > +# will stop matching.
> > +define TI_SGX_LIBGBM_EXTRACT_LICENSE
> > +     head -n 26 $(@D)/gbm.h > $(@D)/license.txt
> > +endef
> > +TI_SGX_LIBGBM_POST_EXTRACT_HOOKS += TI_SGX_LIBGBM_EXTRACT_LICENSE
>
> I've used the complete gbm.h as license file. We already use full
> source files as license files in other packages, it's simple enough,
> and this gbm.h is unlikely to ever change anyway.
>
> I've also taken into account the comments from Yegor, and applied. Thanks!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200121/263583f7/attachment.html>

  reply	other threads:[~2020-01-21 12:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 12:49 [Buildroot] [PATCH/next v3 0/5] fix beaglebone_qt5 unixmania at gmail.com
2019-11-15 12:49 ` [Buildroot] [PATCH/next v3 1/5] package/ti-sgx-libgbm: new package unixmania at gmail.com
2019-11-15 13:29   ` Yegor Yefremov
2019-12-30 14:01   ` Thomas Petazzoni
2020-01-21 12:07     ` Einar Jón [this message]
2019-11-15 12:49 ` [Buildroot] [PATCH/next v3 2/5] package/ti-sgx-{km, um, demos}: bump to latest TI version unixmania at gmail.com
2019-12-30 14:01   ` Thomas Petazzoni
2019-11-15 12:49 ` [Buildroot] [PATCH/next v3 3/5] package/qt5/qt5base: support ti-sgx-libgbm unixmania at gmail.com
2019-12-30 14:01   ` Thomas Petazzoni
2019-11-15 12:50 ` [Buildroot] [PATCH/next v3 4/5] configs/beaglebone_qt5: bump kernel and U-Boot, add weston unixmania at gmail.com
2019-12-30 14:01   ` Thomas Petazzoni
2019-11-15 12:50 ` [Buildroot] [PATCH/next v3 5/5] configs/beaglebone_qt5: don't use custom post-image script unixmania at gmail.com
2019-12-30 14:01   ` Thomas Petazzoni

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='CABhNV23HS7e1iVj=YLMc6d4SWTgNr3YELVCKfLuuE5BZRKwfgw@mail.gmail.com' \
    --to=tolvupostur@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.