From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6] intel-gmmlib: new package.
Date: Tue, 22 Jan 2019 14:57:51 +0200 [thread overview]
Message-ID: <87r2d4hmsw.fsf@tarshish> (raw)
In-Reply-To: <ea-mime-5c45c4f8-23fb-726a437b@www-6.netcourrier.com>
Hi Louis-Paul,
Please avoid top-posting.
On Mon, Jan 21 2019, lpdev wrote:
> The default install target is installing a bunch of header files on
> the target, while unecessary. Maybe Buildroot scripts are cleaning
> them before creating the image?
Correct. See the target-finalize target definition in the top level
Makefile.
> Concerning the /lib folder, it is an error indeed. It must be in
> /usr/lib. Any other suggestions?
Just leave the libraries where upstream install target put them.
> This is my first contribution to the Buildroot project ;)
Thanks for you contribution. This is not bad for first time.
Good luck,
baruch
>> Thank you for your feedback!
>
> De : Baruch Siach <baruch@tkos.co.il>
> ? : Louis-Paul Cordier <lpdev@cordier.org>
> Sujet : Re: [Buildroot] [PATCH 1/6] intel-gmmlib: new package.
> Date : 19/01/2019 19:29:31 Europe/Paris
> Copie ? : buildroot at buildroot.org;
> Bernd Kuhls <bernd.kuhls@t-online.de>;
> Mahyar Koshkouei <mahyar.koshkouei@gmail.com>
>
> Hi Louis-Paul,
>
> On Fri, Jan 18 2019, Louis-Paul Cordier wrote:
>> Signed-off-by: Louis-Paul Cordier <lpdev@cordier.org>
>> ---
>> package/Config.in | 1 +
>> package/intel-gmmlib/Config.in | 8 ++++++++
>> package/intel-gmmlib/intel-gmmlib.hash | 2 ++
>> package/intel-gmmlib/intel-gmmlib.mk | 21 +++++++++++++++++++++
>> 4 files changed, 32 insertions(+)
>> create mode 100644 package/intel-gmmlib/Config.in
>> create mode 100644 package/intel-gmmlib/intel-gmmlib.hash
>> create mode 100644 package/intel-gmmlib/intel-gmmlib.mk
>>
>> diff --git a/package/Config.in b/package/Config.in
>> index 5036421a73..9082ed9956 100644
>> --- a/package/Config.in
>> +++ b/package/Config.in
>> @@ -1265,6 +1265,7 @@ menu "Graphics"
>> source "package/harfbuzz/Config.in"
>> source "package/ijs/Config.in"
>> source "package/imlib2/Config.in"
>> + source "package/intel-gmmlib/Config.in"
>> source "package/irrlicht/Config.in"
>> source "package/jasper/Config.in"
>> source "package/jpeg/Config.in"
>> diff --git a/package/intel-gmmlib/Config.in b/package/intel-gmmlib/Config.in
>> new file mode 100644
>> index 0000000000..8d9fab7ce3
>> --- /dev/null
>> +++ b/package/intel-gmmlib/Config.in
>> @@ -0,0 +1,8 @@
>> +config BR2_PACKAGE_INTEL_GMMLIB
>> + bool "intel-gmmlib"
>> + depends on BR2_x86_64
>> + help
>> + The Intel(R) Graphics Memory Management Library provides
>> + device specific and buffer management for the Intel(R)
>> + Graphics Compute Runtime for OpenCL(TM) and the Intel(R)
>> + Media Driver for VAAPI.
>> diff --git a/package/intel-gmmlib/intel-gmmlib.hash b/package/intel-gmmlib/intel-gmmlib.hash
>> new file mode 100644
>> index 0000000000..7e3b3dfd3f
>> --- /dev/null
>> +++ b/package/intel-gmmlib/intel-gmmlib.hash
>> @@ -0,0 +1,2 @@
>> +# Locally computed
>> +sha256 e3114d7ddd429f1b9aa43a1b1d0086d881fbf4d90e4a90ab8577c369d2e3a5e1 intel-gmmlib-18.3.0.tar.gz
>> diff --git a/package/intel-gmmlib/intel-gmmlib.mk b/package/intel-gmmlib/intel-gmmlib.mk
>> new file mode 100644
>> index 0000000000..206ea6db86
>> --- /dev/null
>> +++ b/package/intel-gmmlib/intel-gmmlib.mk
>> @@ -0,0 +1,21 @@
>> +################################################################################
>> +#
>> +# intel-gmmlib
>> +#
>> +################################################################################
>> +
>> +INTEL_GMMLIB_VERSION = 18.3.0
>> +INTEL_GMMLIB_SITE = https://github.com/intel/gmmlib/archive
>> +INTEL_GMMLIB_LICENSE = MIT
>> +INTEL_GMMLIB_LICENSE_FILES = COPYING
>> +
>> +INTEL_GMMLIB_INSTALL_STAGING = YES
>> +INTEL_GMMLIB_SUPPORTS_IN_SOURCE_BUILD = NO
>> +
>> +INTEL_GMMLIB_CONF_OPTS += -DRUN_TEST_SUITE=OFF
>> +
>> +define INTEL_GMMLIB_INSTALL_TARGET_CMDS
>> + cp -a $(STAGING_DIR)/usr/lib/libigdgmm* $(TARGET_DIR)/lib
>
> This is unusual. Can't you use the default install make target like the
> staging install? Why do you install in /lib on target when upstream
> installs in /usr/lib on staging?
>
> If this is all intended please explain why in a comment.
>
> baruch
>
>> +endef
>> +
>> +$(eval $(cmake-package))
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2019-01-22 12:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 20:10 [Buildroot] [PATCH 0/6] *** Add Intel QuickSync support to ffmpeg *** Louis-Paul Cordier
2019-01-18 20:10 ` [Buildroot] [PATCH 1/6] intel-gmmlib: new package Louis-Paul Cordier
2019-01-19 18:29 ` Baruch Siach
2019-01-21 13:11 ` lpdev at cordier.org
2019-01-22 12:57 ` Baruch Siach [this message]
2019-01-28 19:57 ` LP C
2019-01-30 8:36 ` Baruch Siach
2019-01-18 20:10 ` [Buildroot] [PATCH 2/6] intel-mediadriver: " Louis-Paul Cordier
2019-01-18 20:10 ` [Buildroot] [PATCH 3/6] intel-mediasdk: " Louis-Paul Cordier
2019-01-18 20:10 ` [Buildroot] [PATCH 4/6] ffmpeg: bump to version 4.1. ffserver is not supported anymore Louis-Paul Cordier
2019-01-18 20:10 ` [Buildroot] [PATCH 5/6] ffmpeg: enable Intel QuickSync support Louis-Paul Cordier
2019-01-18 20:10 ` [Buildroot] [PATCH 6/6] Update DEVELOPERS Louis-Paul Cordier
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=87r2d4hmsw.fsf@tarshish \
--to=baruch@tkos.co.il \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox