doxygen | Official doxygen git repository

I don't think endianness matters to rgb555, and that's why your link bunches rgb555, rgb555le, and rgb555be together. For that matter, your example with rgba also isn't endian sensitive as its components are all <= 8 bits.

As for how rgb555 is represented in 2 bytes (well, 15 bits), you can search FFmpeg repo for rgb555 and see how encoders/decoders handle such pixel format. Here is one I found rpzaenc.c Line 138:

Specifying pix_fmt to rgb24, converts the pixel format to rgb24.

Without much knowledge about filter graphs, we may execute the code, and check the output.

For displaying the output frame, I replaced the "Trivial ASCII grayscale display" with OpenCV method cv::imshow.
Setting up a project that uses both Libav and OpenCV requires some initial effort...

Here is the output frame with the original code (output is Grayscale):

Here is the output frame with AV_PIX_FMT_BGR24 pixel format (output is BGR):

Note: BGR is used (instead of RGB) because OpenCV convention for color ordering is BGR.

When BGR format is used there is a warning message:

Changing video frame properties on the fly is not supported by all filters.

It is probably not the best practice to set pix_fmt in such way...

Complete code:

Use Set-Content, not Set-Variable:

Sure, Sphinx will execute whatever Python code you add to its configuration file conf.py before it starts the documentation build process.

From the Sphinx documentation:

The configuration file is executed as Python code at build time (using importlib.import_module(), and with the current directory set to its containing directory), and therefore can execute arbitrarily complex code. Sphinx then reads simple names from the file’s namespace as its configuration.

Which means pre-build tasks can simply be implemented by running the external program, such as Doxygen in your case, as a subprocess anywhere in conf.py.

If you have clang installed on your system, you can enable the CLANG_ASSISTED_PARSING option in the Doxyfile, which is more accurate but a bit slower than the doxygen builtin preprocessor. This generates the correct call graph on my system.

For those wondering: this was a bug and was fixed in commit ab74ff26b0f9ba3f31d1dce605c4a1809ca9cb5c and is now part of Doxygen release 1.9.3. Huge thanks to @albert for lightning fast patching :-)

Take a look at the SROA pass, which defines a class AllocaSlices::SliceBuilder which inherits from PtrUseVisitor. If you look in that class for calls to Base:: methods, those are making using of PtrUseVisitor.

You are getting high frame rate because you have failed to set packet duration.

• Set the time_base to higher resolution (like 1/60000) as described here:

As seen in the output you've provided, there are 2 problems:

1. There is a target name conflict between probably CppAD and eigen. They both have the uninstall target. It can be seen here: