Thanks for the SONAME info . It was bugging me all this time .
You are correct . The SONAME of my shared object (libx264.so.142) was not
same as my filename (libx264.so) . I'm running on Android , and linking is
done there at runtime . Don't know whether I have handle to linking
commands there.
A
One more thing I wanted to add was libx264 's configure does not provide an
option similar to "--target-os=android" . Thats why I'm not able to make a
shared object file with extension .so (It generates with extension .so.142).
I expect may be just renaming of .so. to .so will work . But still
for
Thanks .
Using configure option "--target-os=android" is generating shared object
files which has extension supported by android (.so) .
But when I use "--enable -libx264" option the libavutil.so (which is
generated after building ffmpeg) is having a dynamic dependency to the
shared object file l
he generated
shared object files (eg : libavutil) has dynamic dependency with
libx264.so. . But I want to make this dependency to .so extension format so that android binary packaging system will be
able to package shared object for libx264 .
On Tue, Aug 5, 2014 at 4:22 PM, Carl Eugen Hoyos
right??
What changes do I need to make to ffmpeg configure file to achieve this?
--
Thanks and Regards ,
David Varghese
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
er as sysroot.
After printing "ERROR: libx264 not found" the ffmpeg starts building and
finishes successfully but libx264 support is not included .
On Fri, Aug 1, 2014 at 7:08 PM, Carl Eugen Hoyos wrote:
> David Varghese gmail.com> writes:
>
> > build_one{./configure
&
files (usually live in include dir and end in .h) or they
> are installed but not in a standard location
>
>
> On 1 August 2014 12:37, David Varghese wrote:
>
> > Hi,
> >
> > I needed to install ffmpeg with libx264 support for enabling H.264
> encoding
> > .
/local/include .
I modified my ffmpeg script by adding --extra-cflags='-I/usr/local/'
--extra-ldflags='-I/usr/local/x264 -L/usr/local/ -ldl' .
But still I'm getting the error .
On Fri, Aug 1, 2014 at 5:16 PM, Reindl Harald
wrote:
>
> Am 01.08.2014 um 13:37 schri
irectories .
What all changes do I need to make to the ffmpeg build script in-order to
make it detect libx264?
--
Thanks and Regards ,
David Varghese
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
doing something seriously wrong here ??
Note : I followed
http://ffmpeg.org/doxygen/trunk/transcoding_8c-example.html for re-encoding
.
--
Thanks and Regards ,
David Varghese
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org
rnley
wrote:
> On 2014-07-23 15:39, David Varghese wrote:
> > Thanks for the reply.
> >
> > Infact I tried to directly manipulate the YUV frame that I got from
> decoder
> > . I tried to modify the Y value of every pixels of every frames to 1 ,
> > expecting to se
*frame = {*YUV420P frame recieved from ffmpeg decoder*}uint8_t
*tempPtr = NULL;
tempPtr = frame->data[0];int j;for(j = 0 ; j < frame->linesize[0] ; j++){
*(tempPtr++) = 1;}
Am I doing something seriously wrong?
On Wed, Jul 23, 2014 at 6:41 PM, Carl Eugen Hoyos wrote:
> Da
,
int brightness, int contrast, int saturation);
but the parameter specification of the above function was difficult to
understand. Can anybody do a little elaboration on the parameters use in
this function?especially inv_table and table .
--
Thanks and Regards ,
David Varghese
13 matches
Mail list logo