Dependency management with Qt Shared Library?
-
I am coming from the world of gradle/cocopods/npm/nuget/etc dependency management.
I am writing a Qt app (https://github.com/NightVsKnight/NDI-Monitor) and now I want to refactor it from
a Stand Alone Apptoa Shared Library plus a demo app showing how to use that Library.What is the modern recommended best practice higher level sequence of events for someone wanting to use a 3rd party widget library in their own app/library?
Are they expected to just clone or copy the source code and/or supporting binaries and manually add them to their makefile, possibly just using git submodules?How to best structure my own project repo and code to best be used by other people?
I've read https://doc.qt.io/qt-6/sharedlibrary.html and am familiar with dll import/export, but it seems simpler, especially to avoid instruction incompatibility issues, to just share out my source code and not the complied binaries.
Or, is there the concept of Qt dependency management where they can specify the name or id or url of the dependency and it auto magically is usable to their own app/library?
Basically, is there a "qpm"? A "Qt Package Manager" in the cloud to share either code or binaries or both?
Thanks,
Pv -
Hi,
In fact, there's is a qpm. However, the service will be retired in the near future and they recommend what I was about to suggest you as well: check conan. Qt is also available through it.
