interpret that file and
so can the CI system. To the CI system the optional dependencies are
also required ones.
Simon
Original Message
From: Thiago Macieira
Sent: Wednesday, June 10, 2015 18:44
To: development@qt-project.org
Subject: Re: [Development] Specifying module
=theqtcompany@qt-project.org] On Behalf Of Hausmann Simon
Sent: Wednesday, June 10, 2015 9:48 PM
To: Thiago Macieira; development@qt-project.org
Subject: Re: [Development] Specifying module dependencies
Hi,
Why do we need to pin anything beyond the regular git submodules
handling of qt5
On Mon, Jun 15, 2015 at 08:52:52AM +0200, Simon Hausmann wrote:
We also do have at this point a duplication of repository dependencies
in qt.pro as well as in the repository sync.profile. I do believe that
we can eliminate this dependency without any downside, based on your
idea of placing a
On Monday, June 15, 2015 07:40:07 PM Sergio Ahumada wrote:
On 15.06.2015 08:52, Simon Hausmann wrote:
Perhaps there is a misunderstanding here, so let me confirm also what
Joerg
said: At this point we're interested in discussion repository
dependencies. I understand that are somewhat
On 15.06.2015 08:52, Simon Hausmann wrote:
Perhaps there is a misunderstanding here, so let me confirm also what Joerg
said: At this point we're interested in discussion repository dependencies. I
understand that are somewhat parallel to the qt module dependencies and I
also
understand
On Friday, June 12, 2015 09:47:44 AM Oswald Buddenhagen wrote:
On Thu, Jun 11, 2015 at 08:30:37PM +, Gladhorn Frederik wrote:
On Thursday 11. June 2015 18.47.40 Oswald Buddenhagen wrote:
you won't get rid of the redundant dependency specifications anyway,
because qt.pro (and the
On Thu, Jun 11, 2015 at 08:30:37PM +, Gladhorn Frederik wrote:
On Thursday 11. June 2015 18.47.40 Oswald Buddenhagen wrote:
you won't get rid of the redundant dependency specifications anyway,
because qt.pro (and the sync.profile's) are about repository deps,
while the module's
On 11-Jun-15 18:47, Oswald Buddenhagen wrote:
you won't get rid of the redundant dependency specifications anyway,
because qt.pro (and the sync.profile's) are about repository deps, while
the module's requires() (and whatever other methods they use to exclude
themselves) are about module (and
On Wed, Jun 10, 2015 at 08:32:07PM +, Hausmann Simon wrote:
Hi,
Ok :) let's try with reduced qmake syntax (just variables, no functions). We
can still fall back to json if it's too clumsy.
as you can parse anything, what's wrong with parsing the function
calls from qt.pro? they match a
On Thu, Jun 11, 2015 at 03:43:15PM +0200, Simon Hausmann wrote:
On Thursday, June 11, 2015 12:29:10 PM Oswald Buddenhagen wrote:
On Wed, Jun 10, 2015 at 08:32:07PM +, Hausmann Simon wrote:
Hi,
Ok :) let's try with reduced qmake syntax (just variables, no functions).
We can
On Thursday, June 11, 2015 12:29:10 PM Oswald Buddenhagen wrote:
On Wed, Jun 10, 2015 at 08:32:07PM +, Hausmann Simon wrote:
Hi,
Ok :) let's try with reduced qmake syntax (just variables, no functions).
We can still fall back to json if it's too clumsy.
as you can parse anything,
On Thursday 11. June 2015 18.47.40 Oswald Buddenhagen wrote:
On Thu, Jun 11, 2015 at 03:43:15PM +0200, Simon Hausmann wrote:
On Thursday, June 11, 2015 12:29:10 PM Oswald Buddenhagen wrote:
On Wed, Jun 10, 2015 at 08:32:07PM +, Hausmann Simon wrote:
Hi,
Ok :) let's try with
On Wednesday 10 June 2015 18:30:34 Frederik Gladhorn wrote:
4) qt5.git
in qt.pro we list all modules again, with deps:
addModule(qtdeclarative, qtbase, qtsvg qtxmlpatterns)
(amusingly this is not even correct, qtsvg is not a dependency of
qtdeclarative any more)
That's an optional
: Wednesday, June 10, 2015 22:21
To: development@qt-project.org
Subject: Re: [Development] Specifying module dependencies
On Wednesday 10 June 2015 19:33:37 Hausmann Simon wrote:
Any particular reason against json, btw? Qmake can read it out of the box,
as opposed to .ini. So the only other option I
On Wednesday 10 June 2015 19:33:37 Hausmann Simon wrote:
Any particular reason against json, btw? Qmake can read it out of the box,
as opposed to .ini. So the only other option I can think of is a very very
limited qmake subset (variable.subvar = value per line and # comment).
Didn't know
system. To the CI system the optional dependencies are also required ones.
Simon
Original Message
From: Thiago Macieira
Sent: Wednesday, June 10, 2015 18:44
To: development@qt-project.org
Subject: Re: [Development] Specifying module dependencies
On Wednesday 10 June 2015 18:30:34 Frederik Gladhorn
16 matches
Mail list logo
