It's so kind of you. In my private opinion, I think attach a section on how to disable and enable the version prefixed symbol generation in README or some where else is fine with me and this will take less effort.
2012/11/28 Luca Barbato <[email protected]> > On 11/28/12 2:12 PM, fei wang wrote: > > Hi all, > > I have a question on the link of latest libav libraries. > > ####Background#### > > I am porting the latest libav to android by a ndk(cross-compile it > > through ndk standalone toolchain, passing sys-root parameter to configure > > script) on Linux. After that I found the new libav libraries cannot link > > well with other modules > > while my previous libraries based on ffmpeg works well. Then I look into > > the symbol table and compared them with each other and found that all > > internal defined symbols in latest libav libraries > > are prefixed with a LIBAVCODEC_54/ LIBAVFORMAT_54/LIBAVUTIL_52, but my > > other modules which depending on these apis exported by libav libraries > > refers to the original symbols which is not prefixed with these version > > information(I am very certain that i have used the proper header files). > > ####Question#### > > So can any body help me to fix this link problem? > > You should build the libraries unversioned. > > > I guess we might add a toolchain switch for android to get you that > right out of box. That might involve changing again the library creation > rules though =_=; > > lu > > _______________________________________________ > libav-devel mailing list > [email protected] > https://lists.libav.org/mailman/listinfo/libav-devel >
_______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
