[email protected] writes: > 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).
My suggestion was to move the tables to separate files and compile those on the host against a tool that prints the doc fragments in a manner similar to tablegen. -- Måns Rullgård [email protected] _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
