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
On Tue, Aug 05, 2014 at 13:07:36 +, Carl Eugen Hoyos wrote:
> Do I understand correctly that you built a binary of x264
> that has an incorrect so name? Is it perhaps sufficient to
> rename the library?
If the Android toolchain behaves like a normal Linux/Unix toolchain,
the (ffmpeg) linking
David Varghese gmail.com> writes:
> Using configure option "--target-os=android" is
> generating shared object files which has extension
> supported by android (.so) .
Thank you for testing this!
> But when I use "--enable -libx264" option the libavutil.so
> (which is generated after buildin
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
> You (of course!) cannot get support here if you edit your configure file.
Why is this obvious?
PO
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
David Varghese gmail.com> writes:
> I have edited the actual configure file
You (of course!) cannot get support here if you
edit your configure file. Instead, please report
what does not work with the unchanged source so
we can fix it.
If you want to compile for Android, please use
the confi
Thanks .
I have edited the actual configure file by replacing the following lines ,
SLIBNAME_WITH_MAJOR='$(SLIBNAME).$(LIBMAJOR)'
LIB_INSTALL_EXTRA_CMD='$$(RANLIB) "$(LIBDIR)/$(LIBNAME)"'
SLIB_INSTALL_NAME='$(SLIBNAME_WITH_VERSION)'
SLIB_INSTALL_LINKS='$(SLIBNAME_WITH_MAJOR) $(SLIBNAME)'
David Varghese gmail.com> writes:
> 2) Build ffmpeg v 2.3
If you need support on this mailing list, please
provide the actual configure line you are using
(not an external script) and the problem you have
with that configure line.
If you believe that our configure script misses
some feature
