[Development] QtCS 2018: Third-party and security policy

Mårten Nordheim marten.nordheim at qt.io
Fri Jul 13 16:56:44 CEST 2018

On 13.07.2018 16:49, Lisandro Damián Nicanor Pérez Meyer wrote:
> El viernes, 13 de julio de 2018 10:59:09 -03 Mårten Nordheim escribió:
>> On 05.07.2018 16:48, Thiago Macieira wrote:
>>> On Thursday, 5 July 2018 01:56:43 PDT Kai Koehne wrote:
>>>> PS: Notes from the session at the Qt Contributor Summit are available at
>>>> https://wiki.qt.io/QtCS2018_Third-Party_Sources_Policy_and_Security
>>> Thanks Kai.
>>> Do we have a volunteer to trial out vcpkg and explain to the rest of us
>>> how it would work for Qt? Will it be invisible to our users and
>>> ourselves? Note how Linux distros don't have it nor does Homebrew on Mac.
>> I implemented a POC here: https://codereview.qt-project.org/#/c/234478/
>> I'm not sure if this is what people had in mind (e.g. installing
>> dependencies during configure), but it works at the moment for what I've
>> tested it for.
> I understand this as: at configure time download 3rdparty code.

That's how the current POC works, but it can/likely will change. And 
then you could use vcpkg to download your dependencies first and just 
let configure deal with picking up the libraries (for the most part).


More information about the Development mailing list