On Thu, Apr 04, 2019 at 04:10:35PM +0800, Linjie Fu wrote: > Use the profile constraint flags to determine the exact va_profile for > HEVC_REXT. > > Directly cast PTLCommon to H265RawProfileTierLevel, and use > ff_h265_get_profile > to get the exact profile. > > Signed-off-by: Linjie Fu <linjie...@intel.com> > --- > [v2]: use constraint flags to determine the exact profile, expose the > codec-specific stuff at the beginning. > [v3]: move the VA version check to fix the compile issue. > [RFC]: is it acceptable to cast PTLCommon to H265RawProfileTierLevel for > convenience? The members in PTLCommon should be strictly matched in > H265RawProfileTierLevel. > > libavcodec/vaapi_decode.c | 73 +++++++++++++++++++++++++++++++-------- > 1 file changed, 58 insertions(+), 15 deletions(-)
breaks build with shared libs:
libavcodec/libavcodec.so: undefined reference to `ff_h265_get_profile'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [ffmpeg_g] Error 1
make: *** Waiting for unfinished jobs....
libavcodec/libavcodec.so: undefined reference to `ff_h265_get_profile'
libavcodec/libavcodec.so: undefined reference to `ff_h265_get_profile'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [ffplay_g] Error 1
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [ffprobe_g] Error 1
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Old school: Use the lowest level language in which you can solve the problem
conveniently.
New school: Use the highest level language in which the latest supercomputer
can solve the problem without the user falling asleep waiting.
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
