A lot of unspecified library dependencies when using static library from other build system

When building a static library using qul_add_target with QML_PROJECT and STATIC_LIBRARY, and wanting to use this library from another build system, it's unclear which libraries have to be linked against and in what order.

Libraries such as MonotypeUnicodeEngineShaperDisabled, DeviceLink, Core, Platform, Controls, MonotypeFontEngine, PNGDecoderNull, WorldTypeSpark, ITypeSparkAligned etc all have to be linked against in some arbitrary order.

In addition, if the qmlproject contains custom modules, automatically generated libraries for those modules also have to be linked against, and they have obfuscated names such as "libLib_test_qmlproj9bd6.a", when the module target name is "test_qmlproject_static_library_with_module".

This all makes it easy to get linker errors without any clear guide on how to solve them.

One thing that would be nice is if all these libraries could somehow be bundled into a single static library that could be linked against in the application project.

If that's not possible, it would be useful to have a file listing all the required libraries and their required link order.