On Tue, Feb 5, 2019 at 6:29 AM Carl Eugen Hoyos <ceffm...@gmail.com> wrote: > How would this be better than printing a warning if the feature > could not be enabled as it is already done in some situations?
In most systems I've worked with, if I say "enable something" and it cannot be enabled I want the ./configure to exit out immediately with a non-zero error code. Especially when doing scripted builds, the last thing I want to do is have the script run to completion and then have to pipe stderr to a file and grep the output for warnings that something didn't get included. That's just my opinion though. :-) Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel