On 12.08.2014, at 02:21, Ivan Kalvachev <ikalvac...@gmail.com> wrote: > It would be decided by the gcc -I inclusion option. > It modifies the search paths for header files, so that it checks these > paths before the system/default ones (When using `#include > "libavcodec/avcodec.h" `) > > Libav headers are probably going to remain in the default /usr/include/ . > Usually this should not be a problem, unless a program uses `#include > <libavcodec/avcodec.h> ` that should be used for system headers (aka > checks the system/default paths first).
Huh? The only difference between "" and <> is that "" also searches relative to the file's directory (and that first). -I applies equally to all. Anyone adding -I/usr/include explicitly deserves some beating. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
