Opened 12 years ago
#2078 new defect
--enable-librtmp does not remove ffmpegs native RTMP_PROTOCOL's from libavprotocols
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Component: | build system |
Version: | HEAD | Severity: | normal |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Reproduced by developer: | no | Analyzed by developer: | no |
Description
Configuring ffmpeg with --enable-librtmp results in a config.mak like
CONFIG_LIBRTMP=yes
!CONFIG_RTMP_PROTOCOL=yes
!CONFIG_RTMPHTTP_PROTOCOL=yes
!CONFIG_RTMPT_PROTOCOL=yes
CONFIG_LIBRTMP_PROTOCOL=yes
CONFIG_LIBRTMPE_PROTOCOL=yes
CONFIG_LIBRTMPS_PROTOCOL=yes
CONFIG_LIBRTMPT_PROTOCOL=yes
CONFIG_LIBRTMPTE_PROTOCOL=yes
When configuring mplayer with --enable-librtmp ffmpeg's internal RTMP*_PROTOCOL
variables keep untouched, which leads to unplayable rtmp stream urls.
An example url that is valid for the next 7 days is:
rtmp://artestras.fcod.llnwd.net/a3903/o35/mp4:geo/videothek/default/arteprod/A7_SGT_ENC_04_046446-027-A_PG_HQ_DE?h=7c1e3b3628471c59ea431d929fbef472
Furthermore extra_ldflags will not be enriched with "-lrtmp" when configuring mplayer with --enable-librtmp
Attached a diff against revision 35023 ./configure
diff for ./configure r35023 patch strip native rtmp_protocol from ffmepg and enable extra_ldflags