[Libav-user] Source code debugging libav using Xcode

Gary Overall goverall at hotmail.com
Fri Mar 29 01:02:27 CET 2013

Thank you for your help.  I feel like I am very close.  I did as you said, and it did actually build the libav libraries as I compiled and ran my project within Xcode.  I had to put  the location of the libraries in my header search path to to be able to include the .h files.  However, when I try to call anything in the libraries (ie av_register_all();) I get the following linker error.  I just assumed that since I put the ffmpeg source tree as a target dependency, that the linker would find the library files.  Am I still missing a critical step??

  "_av_register_all", referenced from:
      -[FFAppDelegate applicationDidFinishLaunching:] in FFAppDelegate.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

It found the .h files, but it did not seem to find the libraries.  
Thanks,Gary O
> From: rjvbertin at gmail.com
> Date: Thu, 28 Mar 2013 09:29:52 +0100
> To: libav-user at ffmpeg.org
> Subject: Re: [Libav-user] Source code debugging libav using Xcode
> In xcode 3, I simply add a new external build target to which I add the ffmpeg source tree. Add that target as a dependency to your own target, and you should be set. If you want to be extra sure, build ffmpeg with the same compiler you use in your project.
> BTW, I have a git project up over on github.com/RJVB that shows how to make a monolithic framework out of the FFmpeg libs .
> _______________________________________________
> Libav-user mailing list
> Libav-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/libav-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ffmpeg.org/pipermail/libav-user/attachments/20130328/c0792cae/attachment.html>

More information about the Libav-user mailing list