Change Details

Works as intended. Ideally this could evolve into an at least 1 of 2 approaches: - use QTextBrowser for rendering (like Qt Assistant does by default; not the prettiest but it does the job for most documentation) - hand off HTML to the user's browser, letting both applications do what they do best.

It would be nice if CMake's summary printed a list of optional dependencies that were disabled explicitly.

Works as intended. Ideally this could evolve into an at least 1 of 2 approaches: - use QTextBrowser for rendering (like Qt Assistant does by default; not the prettiest but it does the job for most documentation) - hand off HTML to the user's browser, letting both applications do what they do bestIt would be nice if CMake's summary printed a list of optional dependencies that were disabled explicitly.