From: "André Hentschel" <nerv@dawncrow.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libosmesa: New package
Date: Thu, 1 Oct 2015 00:16:36 +0200 [thread overview]
Message-ID: <560C5F44.8070101@dawncrow.de> (raw)
In-Reply-To: <20150930233743.6835979e@free-electrons.com>
Am 30.09.2015 um 23:37 schrieb Thomas Petazzoni:
> Dear Andr? Hentschel,
>
> On Wed, 30 Sep 2015 23:14:30 +0200, Andr? Hentschel wrote:
>
>> diff --git a/package/libosmesa/libosmesa.hash b/package/libosmesa/libosmesa.hash
>> new file mode 100644
>> index 0000000..0501314
>> --- /dev/null
>> +++ b/package/libosmesa/libosmesa.hash
>> @@ -0,0 +1,2 @@
>> +# From http://lists.freedesktop.org/archives/mesa-announce/2015-September/000175.html
>> +sha256 e36ee5ceeadb3966fb5ce5b4cf18322dbb76a4f075558ae49c3bba94f57d58fd mesa-10.6.8.tar.xz
>> diff --git a/package/libosmesa/libosmesa.mk b/package/libosmesa/libosmesa.mk
>> new file mode 100644
>> index 0000000..f70fd2a
>> --- /dev/null
>> +++ b/package/libosmesa/libosmesa.mk
>> @@ -0,0 +1,30 @@
>> +################################################################################
>> +#
>> +# libosmesa
>> +#
>> +################################################################################
>> +
>> +# When updating the version, please also update mesa3d
>> +LIBOSMESA_VERSION = 10.6.8
>> +LIBOSMESA_SOURCE = mesa-$(LIBOSMESA_VERSION).tar.xz
>> +LIBOSMESA_SITE = ftp://ftp.freedesktop.org/pub/mesa/$(LIBOSMESA_VERSION)
>
> Why are you creating a new package, instead of simply adding a new
> option to the existing mesa3d package?
>
Hi,
I thought I keep it seperate as osmesa is totally standalone,
but looking closer at the mesa3d.mk it seems this is still possible if the comment about libgl is correct.
(We don't need a libgl for osmesa, but if libgl is only build when a DRI driver is selected it is fine)
prev parent reply other threads:[~2015-09-30 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 21:14 [Buildroot] [PATCH] libosmesa: New package André Hentschel
2015-09-30 21:37 ` Thomas Petazzoni
2015-09-30 22:16 ` André Hentschel [this message]
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=560C5F44.8070101@dawncrow.de \
--to=nerv@dawncrow.de \
--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