Hi, I've written a small tool (enum_opts branch in my tree), which autogenerates texinfo chapters for AVOptions by using our public API. The idea was that those docs would be generated during build process and then @included in avtools manpages. However the problem is that this cannot work with crosscompiling.
Mans suggested that we could instead split the options tables into separate files and parse them with awk or something similar. TBH I don't like this idea very much, because having those tables in separate files is inconvenient and this approach would be quite fragile -- e.g. it'd break on macros (which are present in some tables). Another idea was to generate those docs manually when options change and add them to git. This would solve the crosscompiling issue, but then the docs wouldn't reflect what options are actually present in the build. Yet another possibility would be to combine two approaches -- generate docs during build when possible and fallback to pre-generated with a note that they might not be accurate. Opinions? -- Anton Khirnov _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
