meson/docs/markdown/snippets/qt_factory.md

## Qt Dependency uses a Factory

This separates the Pkg-config and QMake based discovery methods into two
distinct classes in the backend. This allows using
`dependency.get_variable()` and `dependency.get_pkg_config_variable()`, as
well as being a cleaner implementation.
Refactor Qt Dependency into proper split classes with factories Currently the Qt Dependencies still use the old "combined" method for dependencies with multiple ways to be found. This is problematic as it means that `get_variable()` and friends don't work, as the dependency can't implement any of those methods. The correct solution is to make use of multiple Dependency instances, and a factory to tie them together. This does that. To handle QMake, I've leveraged the existing config-tool mechanism, which allows us to save a good deal of code, and use well tested code instead of rolling more of our own code. The one thing this doesn't do, but we probably should, is expose the macOS ExtraFrameworks directly, instead of forcing them to be found through QMake. That is a problem for another series, and someone who cares more about macOS than I do. 4 years ago			`## Qt Dependency uses a Factory`

			`This separates the Pkg-config and QMake based discovery methods into two`
			`distinct classes in the backend. This allows using`
			`dependency.get_variable()` and `dependency.get_pkg_config_variable()`, as
			`well as being a cleaner implementation.`