[FFmpeg-devel] [PATCH] avutil: expand the size of LINE_SZ to 2048.

Stephen Hutchinson qyot27 at gmail.com
Sat Aug 10 12:16:30 CEST 2013

On Sat, Aug 10, 2013 at 4:22 AM, Nicolas George <
nicolas.george at normalesup.org> wrote:

> Why don't you just do it in C? For example, use strcspn/strchr to find the
> length of the next word, and then use this to print it:
>         av_log(..., "%.*s ", length, str);

To be honest, I wanted to do it all in C, but for all the looking I was
doing at the man pages for the str* and printf* functions, I couldn't find
the right documentation or explanations to show how to make the pieces work
together like that.  This helps, so I'll start digging more along these

Also, I do not believe that printing one option per line is a good idea; my
> usual build have 36 build options, mostly --enable-foo: that is exactly the
> size of most of my work ttys.

The one-per-line situation would be applied exclusively to the output of
the -buildconf option, to be consistent with other -h/-formats/-codecs/etc.
options.  The 'configuration:' line displayed during regular invocation
wouldn't change.  I have to deal with 48 build options when doing
cross-compiles; there's no way I'd want to make regular invocation display
it as one-per-line - I already have to scroll up (or increase the window
height of the Terminal/cmd.exe) to see the version number/copyright/build
date lines when running it with all those in there.

> I can suggest this: replace "--enable-foo" by "+foo", and wrap to 76
> columns.

I like the +foo format for regular invocation display, but it'll need
additional rules to compensate for options that aren't prefixed by
--enable- (--extra-cflags/ldflags, --cross-prefix, --arch, --cpu, etc.),
unless those just get ignored for display purposes.

More information about the ffmpeg-devel mailing list