From: Steffen Sledz <sledz@dresearch-fe.de>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [PATCH] efl: sync bbappend version to meta-openembedded
Date: Wed, 05 Nov 2014 13:00:28 +0100 [thread overview]
Message-ID: <545A115C.7070307@dresearch-fe.de> (raw)
In-Reply-To: <CALbNGRQ6c_UoioOFeT9MjPfcetvzJT_iz4ED0UcJHA9SetHfzg@mail.gmail.com>
On 05.11.2014 11:05, Andreas Müller wrote:
> On Wed, Nov 5, 2014 at 9:53 AM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> On 2014-11-05 08:26, Steffen Sledz wrote:
>>>
>>> Signed-off-by: Steffen Sledz <sledz@dresearch-fe.de>
>>> ---
>>> efl-layer/recipes-efl/efl/efl_1.11.4.bbappend | 3 +++
>>> efl-layer/recipes-efl/efl/efl_1.9.3.bbappend | 3 ---
>>> 2 files changed, 3 insertions(+), 3 deletions(-)
>>> create mode 100644 efl-layer/recipes-efl/efl/efl_1.11.4.bbappend
>>> delete mode 100644 efl-layer/recipes-efl/efl/efl_1.9.3.bbappend
>>>
>>> diff --git a/efl-layer/recipes-efl/efl/efl_1.11.4.bbappend
>>> b/efl-layer/recipes-efl/efl/efl_1.11.4.bbappend
>>> new file mode 100644
>>> index 0000000..10c99d8
>>> --- /dev/null
>>> +++ b/efl-layer/recipes-efl/efl/efl_1.11.4.bbappend
>>> @@ -0,0 +1,3 @@
>>> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>>> +
>>> +SRC_URI +=
>>> "file://0001-Add-preprocessor-definitions-for-Vivante-GLES-header.patch"
>>> diff --git a/efl-layer/recipes-efl/efl/efl_1.9.3.bbappend
>>> b/efl-layer/recipes-efl/efl/efl_1.9.3.bbappend
>>> deleted file mode 100644
>>> index 10c99d8..0000000
>>> --- a/efl-layer/recipes-efl/efl/efl_1.9.3.bbappend
>>> +++ /dev/null
>>> @@ -1,3 +0,0 @@
>>> -FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>>> -
>>> -SRC_URI +=
>>> "file://0001-Add-preprocessor-definitions-for-Vivante-GLES-header.patch"
>>
>>
>> Wait. Is this really necessary? What about Andreas Müller's "efl: rename
>> bbappend to match future versions" patch in this list?
>>
> I struggled building efl on for a imx6 machine so I thought it needs
> more investigation. I did not follow this since I don't use efl. Was
> this build tested with bbappend active?
I've made a successful build for nitrogen6x machine (SOC_FAMILY = "mx6:mx6dl:mx6q") with active bbappend.
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2014-11-05 12:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 14:12 [dizzy] bad efl bbappend Steffen Sledz
2014-11-04 19:52 ` Otavio Salvador
2014-11-05 7:24 ` Steffen Sledz
2014-11-05 7:26 ` [PATCH] efl: sync bbappend version to meta-openembedded Steffen Sledz
2014-11-05 8:53 ` Carlos Rafael Giani
2014-11-05 10:05 ` Andreas Müller
2014-11-05 11:35 ` Otavio Salvador
2014-11-05 12:00 ` Steffen Sledz [this message]
2014-11-05 12:09 ` Andreas Müller
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=545A115C.7070307@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.