From: Steffen Sledz <sledz@dresearch-fe.de>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
openembedded-devel <openembedded-devel@lists.openembedded.org>,
angstrom-distro-devel <angstrom-distro-devel@linuxtogo.org>
Subject: Re: meta-angstrom commit 75f0f25e breaks build of opencv from meta-openembedded
Date: Tue, 10 Mar 2015 15:38:50 +0100 [thread overview]
Message-ID: <54FF01FA.4040403@dresearch-fe.de> (raw)
In-Reply-To: <FAE79245-0EDA-4219-86E5-A3950BDA7682@dominion.thruhere.net>
On 10.03.2015 14:50, Koen Kooi wrote:
>
>> Op 9 mrt. 2015, om 12:52 heeft Steffen Sledz <sledz@dresearch-fe.de> het volgende geschreven:
>>
>> Commit 75f0f25e55f0745a011640b5c81d88be99366f45 in meta-angstrom/recipes-tweaks (branch angstrom-v2014.12-yocto1.7) introduces version 10.5 of libav.
>>
>> This version does no longer provide defines like CODEC_ID_H264 which are needed for opencv 2.4.9 from meta-openembedded/meta-oe/recipes-support (branch dizzy).
>>
>> ---------------------> snip <----------------------
>> .../tmp-glibc/work/armv5te-angstrom-linux-gnueabi/opencv/2.4.9+gitAUTOINC+df8e28283f-r0/git/modules/highgui/src/ffmpeg_codecs.hpp:104:7: error: 'CODEC_ID_H264' was not declared in this scope
>> { CODEC_ID_H264, MKTAG('H', '2', '6', '4') },
>> ^
>> .../tmp-glibc/work/armv5te-angstrom-linux-gnueabi/opencv/2.4.9+gitAUTOINC+df8e28283f-r0/git/modules/highgui/src/ffmpeg_codecs.hpp:105:7: error: 'CODEC_ID_H264' was not declared in this scope
>> { CODEC_ID_H264, MKTAG('h', '2', '6', '4') },
>> ^
>> .../tmp-glibc/work/armv5te-angstrom-linux-gnueabi/opencv/2.4.9+gitAUTOINC+df8e28283f-r0/git/modules/highgui/src/ffmpeg_codecs.hpp:106:7: error: 'CODEC_ID_H264' was not declared in this scope
>> { CODEC_ID_H264, MKTAG('X', '2', '6', '4') },
>> ^
>> .../tmp-glibc/work/armv5te-angstrom-linux-gnueabi/opencv/2.4.9+gitAUTOINC+df8e28283f-r0/git/modules/highgui/src/ffmpeg_codecs.hpp:107:7: error: 'CODEC_ID_H264' was not declared in this scope
>> { CODEC_ID_H264, MKTAG('x', '2', '6', '4') },
>> ...
>> ---------------------> snip <----------------------
>>
>> I'm not sure if this problem occurs in the master branches too, but the dizzy/angstrom-v2014.12-yocto1.7 branches are unusable for some of our applications beacause of this problem at the moment. :(
>
> Sorry about that, I looked at that this weekend, but forgot to push the patches to meta-angstrom. 744d6439175058909002d1e22439e93945d53e22 should fix the issues you are seeing.
Yupp. Fixed.
Thx,
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
prev parent reply other threads:[~2015-03-10 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 11:52 meta-angstrom commit 75f0f25e breaks build of opencv from meta-openembedded Steffen Sledz
2015-03-10 13:50 ` Koen Kooi
2015-03-10 14:38 ` Steffen Sledz [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=54FF01FA.4040403@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=angstrom-distro-devel@linuxtogo.org \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox