>> And, what about QtService from QtSolutions ?
> I don't know what that does.
You can look to sources.. ;)
"The QtService component is useful for developing Windows services and
Unix daemons."
BR,
Denis
17.06.2016 9:26, Thiago Macieira пишет:
On sexta-feira, 17 de junho de 2016 08:15:15
On sexta-feira, 17 de junho de 2016 08:15:15 PDT Denis Shienkov wrote:
> > I’d say Qt Core. This should not really require a large addition to it.
>
> Do you mean QtSingleApplication or QtSolutions to QtCore?
QtSingleApplication. I don't know what else is in Solutions, so I can't
welcome them
> I’d say Qt Core. This should not really require a large addition to it.
Do you mean QtSingleApplication or QtSolutions to QtCore?
Because then QtSingleApplication should be removed from QtQtSolutions,
as it will be in QtCore... :)
And, what about QtService from QtSolutions ?
BR,
Denis
16
Hi all,
Interesting little tidbit I thought I'd share with the community -- looks like
VirtualBox is finally upgrading to Qt 5 (5.5.1, to be precise) in the upcoming
5.1 release. Nice to see some major Qt 4 users making the switch!
https://forums.virtualbox.org/viewtopic.php?f=15&t=77998
strin
On lunes, 6 de junio de 2016 7:20:21 A. M. ART Kai Koehne wrote:
> tl;dr: Does anyone have experience with SPDX?
Not here, but...
> Qt modules contain quite some 3rd party code under various (permissible)
> licenses. We've been listening these in the
documentation, but this is
> certainly improv
On quinta-feira, 16 de junho de 2016 19:23:04 PDT Lars Knoll wrote:
> MIME types would be one of my primary candidates to move out. But we should
> consider removing the dependency of mimetypes onto XML in any case, by
> moving the conversion from XML to binary database into a compile step.
Not su
On 16/06/16 20:47, "Development on behalf of Thiago Macieira"
wrote:
>On quinta-feira, 16 de junho de 2016 20:03:09 PDT Konstantin Tokarev wrote:
>> +1, it should be promoted to add-on at least.
>
>As I said, I'd welcome it in QtCore, but a separate module is fine too.
I’d say Qt Core. This sho
On quinta-feira, 16 de junho de 2016 20:03:09 PDT Konstantin Tokarev wrote:
> +1, it should be promoted to add-on at least.
As I said, I'd welcome it in QtCore, but a separate module is fine too.
I've been wondering whether QtCore needs to be split in Qt 6. It's grown too
big. At least the anima
On jueves, 16 de junio de 2016 10:06:45 A. M. ART Kevin Funk wrote:
[snip]
> I'd like to hear more opinions about whether there's still interest in
> having it in Qt proper. There are obviously advantages to it: CI coverage
> (qt- solutions.git isn't covered by CI, right?), and QtSA getting a bit o
16.06.2016, 11:07, "Kevin Funk" :
> On Donnerstag, 16. Juni 2016 03:43:29 CEST Kevin Kofler wrote:
>> Kevin Funk wrote:
>> > To come to the point: We'd like to be able to use QtSingleApplication,
>> > without having to copy it to every KDE application's repository out there
>> > and building
There is datacenter hardware maintenance break on Tuesday 21st of June
(6am-8am UTC+3), Coin will be shutdown a bit earlier and hopefully restart
after.
Cheers,
Jędrek
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/
> -Original Message-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> project.org] On Behalf Of Reynaldo San Juan
> Sent: Thursday, June 16, 2016 3:13 PM
> To: development@qt-project.org
> Subject: [Development] Building Always on same path?
>
> Hi
> I'm developing
Hi
I'm developing a litle app and
I want to build always inside the user Home path. on Unix based systems
is very easy puting the "~"char at the begining of the path,
but o Windows "~" doesn't work, I used instead "%userprofile%" , like
enviroment variable, but isn't working neither.
Could you t
On Thursday 16 of June 2016 06:57:50 Tony Sarajärvi wrote:
> Hi,
>
> Our aim was to get new platforms in immediately after the previous platforms
> branched away from dev branch. Meaning, when 5.7 branch was created and it
> branched away from dev branch, all new platforms aiming for 5.8 should ha
Hi,
Another approach for tvOS and other items that we can not have in by Qt 5.8 FF
(or shortly after), would be to add these into dev after 5.8 has branched and
have these in good time for Qt 5.9. Although we are constantly improving, we
are not yet where we want in the CI flexibility and Qt i
+1
Philippe
On Thu, 16 Jun 2016 12:22:02 +0200
Frederik Gladhorn wrote:
> On onsdag 15. juni 2016 07.15.16 CEST Tuukka Turunen wrote:
> > Hi,
> >
> > I would also like to have all new modules (if any) of Qt 5.8 as well as
> > implement all (feasible) platform and compiler versions well before
> -Original Message-
> From: Development [mailto:development-
> bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of Frederik
> Gladhorn
> Sent: torstaina 16. kesäkuuta 2016 13.22
> To: development@qt-project.org
> Subject: Re: [Development] Qt 5.8 branching & Feature Freeze - Qt Spe
On onsdag 15. juni 2016 07.15.16 CEST Tuukka Turunen wrote:
> Hi,
>
> I would also like to have all new modules (if any) of Qt 5.8 as well as
> implement all (feasible) platform and compiler versions well before the
> feature freeze. Is it possible to agree that latest by 1.8. all these are
> comp
Hi everybody,
Just wanted to let you all know that Qt 5.7 is now released. For all the
details, check out the blog post at
http://blog.qt.io/blog/2016/06/16/qt-5-7-released/ and the web pages at
http://www.qt.io/qt5-7/
Enjoy!
Cheers,
Lars
___
Announc
> Are you trying out of the source builds ?
that's my usual workflow as i need to compile static and dynamic libs
from the same source folder ...
> I opened a ticket yesterday for this, specifically Qt3D, but it can
> compiles if you run from the root tree on the source.
it also compiles fine w
Are you trying out of the source builds ?
I opened a ticket yesterday for this, specifically Qt3D, but it can
compiles if you run from the root tree on the source.
Regards
On Thu, Jun 16, 2016 at 11:27 AM, Jani Heikkinen
wrote:
> >>would be nice if this could be fixed before 5.7.0 comes out.
>
>>would be nice if this could be fixed before 5.7.0 comes out.
Unfortunately impossible, Qt 5.7.0 is coming out today
br,
Jani
From: Development on
behalf of Tim Blechmann
Sent: Thursday, June 16, 2016 12:05 PM
To: development@qt-project.org
Subject: [Devel
hi all,
compiling 5.7.0-rc (sometimes) fails with the following error when
building qt as static library:
> error 15-Jun-2016 20:04:06make[4]: *** No rule to make target
> `/Volumes/build/bamboo-build/THIRDP-QT9-BUILDMAC/build-Qt-5.7.0-rc-macx-clang-static/qt3d/lib/libQt53DQuick_debug.a',
>
On Donnerstag, 16. Juni 2016 03:43:29 CEST Kevin Kofler wrote:
> Kevin Funk wrote:
> > To come to the point: We'd like to be able to use QtSingleApplication,
> > without having to copy it to every KDE application's repository out there
> > and building it ourselves. Several KDE applications (KDevel
"Currently we can’t put anything new in, since Coin setup is frozen."
Due to my limited knowledge with coin, I don't understand this.
Coin, the new CI, should not bind with any paticular branch of Qt, but some
options and scripts could.
For the listed new OSes, openSUSE 42.1, Ubuntu 16.04, RHEL
25 matches
Mail list logo
