On 2018/04/27 0:15, James Almer wrote:
On 4/26/2018 8:08 PM, Josh de Kock wrote:
The postproc library is only used in a single filter, so should be moved into 
the filter itself if the filter was to stay, but the filter has all of its 
internal filters now in lavfi itself. (Also it's a bit weird to have a separate 
library of filters which is used in a filter in the filter library).

If libpostproc can't be merged into the filter (or nobody bothers to do
it), then it could be moved to a separate repository, much like the
nvidia headers.


This is another 'solution', though I think it would just be better to redirect users to existing equivalent functionality in lavfi itself (see my other mail replying to carl).

[...]
  enabled threads && ! enabled pthreads && ! enabled atomics_native && die "non 
pthread threading without atomics not supported, try adding --enable-pthreads or --cpu=i486 or higher if you are 
on x86"
  enabled avresample && warn "Building with deprecated library libavresample"
+enabled postproc && warn "Building with deprecated library libpostproc"
+enabled pp_filter && warn "Building with deprecated filter pp"

Superfluous warning, the first one is enough. You don't see a warning
for resample_filter below the one for libavresample.


Fair, I had it like that initially, was unsure if they should be separate.

if test $target_os = "haiku"; then
      disable memalign


--
Josh
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Reply via email to