Hi Richard,
Like Iikka wrote the primary plan is to leverage package manager to make it
easier to work with additional components. We now have two Qt add-ons (Qt
Network Authorization and Qt Image Formats) to test with. Our thinking is that
the Qt installer is still the way to get the baseline Qt, but we aim to provide
additional items via package manager.
We are still in the early steps and things like integration to tooling is
something that we need to work on. There are also many items that we do not yet
know what works the best, and we want to develop this further to reach a good
end user experience also when it comes to the tooling, discovery of additional
libraries etc.
The idea is that the additional libraries available via the package manager are
available in source code and built locally. The pre-built binaries continue to
be delivered via the Qt installer. Our intention is to store the recipes into
the component source repo root, but these are not in-place yet.
Yours,
Tuukka
On 1.10.2020, 16.08, "Development on behalf of Richard Weickelt"
<[email protected] on behalf of [email protected]> wrote:
Hello Ilkka,
thanks for the heads up. I have some further questions:
1. Will Conan be used to manage dependencies of Qt as well?
2. How will the recipes be managed and where on code.qt.io can I find them?
3. Is TQtC going to host a Conan repository for binary packages as well?
4. What is the Qt Company's position regarding conan-center?
Thanks
BR
Richard Weickelt
_______________________________________________
Development mailing list
[email protected]
https://lists.qt-project.org/listinfo/development
_______________________________________________
Development mailing list
[email protected]
https://lists.qt-project.org/listinfo/development
