From: Robert Yang <liezhi.yang@windriver.com>
To: Natural Groove <natural_groove@hotmail.fr>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: crossbuild for arm :FFPLAY not build
Date: Thu, 10 Jul 2014 17:13:48 +0800 [thread overview]
Message-ID: <53BE594C.3040600@windriver.com> (raw)
In-Reply-To: <DUB128-W333CD3D967FBE45F67D02920E0@phx.gbl>
On 07/10/2014 05:02 PM, Natural Groove wrote:
> Hi,
>
> Im trying to crossbuild ffmpeg for arm (colibri-t20).
> I wrote a simplest recipe in order to achieve this, but even if ffmpeg, ffprobe
> and ffserver are build, ffplay isnt, i first thought that i had forgotten some
> dependencies but i dont see which could be missing.
> Any idea why this isnt working?
>
> The recipe:
>
> SRC_URI = "https://www.ffmpeg.org/releases/ffmpeg-2.1.1.tar.gz"
> SRC_URI[md5sum] = "294749b2ebdd22ef7d9b9d12a70d5b8c"
> SRC_URI[sha256sum] =
> "66f521dffefcbb6c09a402f6373e6cef81fbf4284d0a33cdef9a19412df1dd18"
> inherit autotools pkgconfig
> DEPENDS = "yasm-native libsdl libx11 zlib libtheora libogg libass libtool"
> S="${WORKDIR}/ffmpeg-2.1.1"
>
>
> inherit autotools pkgconfig
>
> CROSS_COMPILE =
> "/home/rick/oe-core/build/out-eglibc/sysroots/i686-linux/usr/bin/armv7ahf-vfp-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi-"
>
> EXTRA_OECONF = "--arch=arm --enable-cross-compile
> --cross-prefix=${CROSS_COMPILE} --target-os=linux --enable-gpl
> --enable-libtheora --enable-libvorbis --extra-libs="-ldl" --enable-ffplay
> --enable-shared --enable-pic"
Check config.log to see why --enable-ffplay doesn't work ?
>
> do_configure() {
> ./configure ${EXTRA_OECONF}
> }
Remove the do_configure ()?
// Robert
>
>
> Regards
> Ricko
>
>
>
next prev parent reply other threads:[~2014-07-10 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 9:02 crossbuild for arm :FFPLAY not build Natural Groove
2014-07-10 9:13 ` Robert Yang [this message]
2014-07-10 9:26 ` Anders Darander
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=53BE594C.3040600@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=natural_groove@hotmail.fr \
--cc=yocto@yoctoproject.org \
/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.