Revision 4cb3aa09

View differences:

doc/faq.texi
395 395
You can also try to hack it and remove more, but if you had problems fixing
396 396
the compilation failure then you are probably not qualified for this.
397 397

  
398
@section I'm using libavcodec from within my C++ application but the linker complains about missing symbols which seem to be available.
399

  
400
FFmpeg is a pure C project, so to use the libraries within your C++ application
401
you need to explicitly state that you are using a C library. You can do this by
402
encompassing your FFmpeg includes using @code{extern "C"}.
403

  
404
See @url{http://www.parashift.com/c++-faq-lite/mixing-c-and-cpp.html#faq-32.3}
405

  
398 406
@section I have a file in memory / a API different from *open/*read/ libc how do i use it with libavformat?
399 407

  
400 408
You have to implement a URLProtocol, see libavformat/file.c in FFmpeg

Also available in: Unified diff