2012/2/27 Måns Rullgård <[email protected]>: > Felipe Contreras <[email protected]> writes: > >> 2012/2/27 Måns Rullgård <[email protected]>: >>> Felipe Contreras <[email protected]> writes: >>> >>>> tidspbridge? That would be a bit cumbersome: tidspbridge_mpeg4.c >>>> --enable-tidspbridge, and so on. And inconsistent, because the library >>>> would be tidsp. But it's your call. >>> >>> Since you named that library, you don't get to use it as an argument in >>> this discussion. >> >> Who named the library is irrelevant; it's still *inconsistent*. >> >> The name is libtidsp. You get to call libav support for libtidsp >> whatever you want, but anything other than libtidsp, or tidsp, is >> *inconsistent*. Kind of calling vaapi hwaccel, intellink hwaccel. > > You could fix that by renaming the library.
That's not up to you, all you can decide is if to be inconsistent, or not. And as I have stated before; tidsp doesn't conflict with anything else; neither dsplink, nor syslink (which are dead anyway), and even less the only option for the future; remoteproc. -- Felipe Contreras _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
