Hi,
It’s possible to develop apps with mingw against a vcpkg build. The vcpkg
packages themselves cannot be built with mingw yet. I think that is a missing
feature.
Simon
> On 16. Jul 2018, at 18:29, Konstantin Tokarev wrote:
>
>
>
> 13.07.2018, 17:57, "Mårten Nordheim" :
>>> On
13.07.2018, 17:57, "Mårten Nordheim" :
> 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:
>
El viernes, 13 de julio de 2018 14:55:59 -03 Mårten Nordheim escribió:
> On 13.07.2018 18:43, Lisandro Damián Nicanor Pérez Meyer wrote:
> > El viernes, 13 de julio de 2018 11:56:44 -03 Mårten Nordheim escribió:
> > [snip]
> >
> >>> I understand this as: at configure time download 3rdparty code.
On 13.07.2018 18:43, Lisandro Damián Nicanor Pérez Meyer wrote:
El viernes, 13 de julio de 2018 11:56:44 -03 Mårten Nordheim escribió:
[snip]
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
El viernes, 13 de julio de 2018 11:56:44 -03 Mårten Nordheim escribió:
[snip]
> > 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
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
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
> >>
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
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
age-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> project.org] On Behalf Of Thiago Macieira
> Sent: Monday, June 11, 2018 1:18 PM
> To: development@qt-project.org
> Subject: Re: [Development] QtCS 2018: Third-party and security policy
>
> On Monda
On Monday, 11 June 2018 10:56:42 CEST EXT Eike Ziller wrote:
> If we are about to release Qt Creator with LLVM/Clang 6.0, and LLVM/Clang
> 6.1 is released, this has good chances to introduce bugs. Aside from that,
> updating the binaries that we ship is an effort, since they are profile
>
> On 10. Jun 2018, at 22:48, Thiago Macieira wrote:
>
> On Sunday, 10 June 2018 18:17:31 IST Giuseppe D'Angelo wrote:
>>> 0) Where not really necessary, delete the third-party code and force the
>>> use of a system library (see assimp discussion, can be applied to
>>> qtimageformats too).
>>
On Sunday, 10 June 2018 18:17:31 IST Giuseppe D'Angelo wrote:
> > 0) Where not really necessary, delete the third-party code and force the
> > use of a system library (see assimp discussion, can be applied to
> > qtimageformats too).
>
> What's the definition of "necessary" here? We're having
Hi Thiago,
thanks for starting these conversations on the mailing list. I'll miss
this QtCS, so this is great for me and for whomever else won't be able
to attend.
Il 08/06/2018 22:10, Thiago Macieira ha scritto:
There's a session scheduled for Monday (unless it gets moved). Here's what I
On Saturday, 9 June 2018 16:38:46 IST EXT Marco Bubke wrote:
> So what about some embedded scenario. What is a system library in that
> sense. If people ship their own binary it's not part of Qt anymore. So it's
> their problem but for the user it's still a problem and by a high
> probability you
On June 9, 2018 04:10:58 Thiago Macieira wrote:
> There's a session scheduled for Monday (unless it gets moved). Here's what I
> will propose.
>
> 0) Where not really necessary, delete the third-party code and force the use
> of a system library (see assimp discussion, can be applied to
There's a session scheduled for Monday (unless it gets moved). Here's what I
will propose.
0) Where not really necessary, delete the third-party code and force the use
of a system library (see assimp discussion, can be applied to qtimageformats
too).
1) Third-party bundled should be opt-in,
17 matches
Mail list logo
