On 25 July 2017 at 03:09, Phil Bouchard wrote:
> That's why you have to put chances on your side. Regarding the GC all you
> have to do is look at the logs:
> http://www.war-worlds.com/blog/2012/06/on-android-garbage-collection-can-kill-you
What killed the performance in this case was not GC but
On Monday, 24 July 2017 16:26:10 PDT Thiago Macieira wrote:
> This can also happen intra-Qt too, if you're doing split builds. Suppose
> you're building qtmultimedia again but it's already installed. You need to
> link to qtbase libraries, so the -L for the install dir is provided. That
> means the
On Monday, 24 July 2017 15:20:07 PDT Allan Sandfeld Jensen wrote:
> It is a work-around, but it is an issue that pops up frequently and can take
> a while until solved. I do have development files of the system Qt
> installed, and it usually works just fine. When it does pop up it is
> however quit
On Sonntag, 23. Juli 2017 22:49:11 CEST Martin Koller wrote:
> On Sonntag, 23. Juli 2017 18:54:41 CEST Thiago Macieira wrote:
> > On Sunday, 23 July 2017 01:50:10 PDT Martin Koller wrote:
> > > I found this symbol to be in the qgsttools_p lib but I fear the linker
> > > takes the lib from a wrong p
Thiago Macieira wrote:
> On Monday, 24 July 2017 08:15:58 PDT Phil Bouchard wrote:
>>> How do you know it wasn't some other background process waking up and
>>> doing
>>> something? Like getting the device's location and sending to the cloud? Or
>>> the voice command parser?
>>
>> Because at that
On Monday, 24 July 2017 08:15:58 PDT Phil Bouchard wrote:
> > How do you know it wasn't some other background process waking up and
> > doing
> > something? Like getting the device's location and sending to the cloud? Or
> > the voice command parser?
>
> Because at that time they didn't have voice
On Monday, 24 July 2017 13:30:24 PDT Martin Koller wrote:
> On Montag, 24. Juli 2017 16:52:05 CEST Thiago Macieira wrote:
> > On Monday, 24 July 2017 04:26:55 PDT Martin Koller wrote:
> > > Why does my Qt build use the system installed
> > > /usr/lib64/libqgsttools_p.prl
> > > file and not the one
On Montag, 24. Juli 2017 16:52:05 CEST Thiago Macieira wrote:
> On Monday, 24 July 2017 04:26:55 PDT Martin Koller wrote:
> > Why does my Qt build use the system installed /usr/lib64/libqgsttools_p.prl
> > file and not the one from the build dir
>
> "Because it was found".
Then the solution is to
On 2017-07-24 21:32, Grégoire Barbier wrote:
Le 24/07/2017 à 18:45, Henry Skoglund a écrit :
QMap m1 = {std::pair{2,"score"}, {4,"seven"}, {1,"Four"},
{5,"years"}, {3,"and"}, {6,"ago"}};
Or even this:
QMap m1 { {2, "score"}, {4, "seven"}, };
Yes that works nicely too but it's not blee
Le 24/07/2017 à 18:45, Henry Skoglund a écrit :
QMap m1 = {std::pair{2,"score"}, {4,"seven"}, {1,"Four"},
{5,"years"}, {3,"and"}, {6,"ago"}};
Or even this:
QMap m1 { {2, "score"}, {4, "seven"}, };
--
Grégoire Barbier :: g à g76r.eu
___
Developm
On 2017-07-24 16:53, Thiago Macieira wrote:
On Monday, 24 July 2017 00:00:36 PDT Marc Mutz wrote:
Hi,
We haven't added deduction guides to any Qt class, yet. If you want to
use bleeding-edge C++, use C++, iow: std::map.
std::map currently (GCC 7.1.1) works less well than QMap, since you can't
Thiago Macieira wrote:
> On Monday, 24 July 2017 05:47:34 PDT Phil Bouchard wrote:
>> Thiago Macieira wrote:
>>> On Sunday, 23 July 2017 15:13:50 PDT Phil Bouchard wrote:
>>> But that's just it: the GC doesn't happen as often if you're not under
>>> memory pressure. You can postpone the GC to lat
On Monday, 24 July 2017 05:47:34 PDT Phil Bouchard wrote:
> Thiago Macieira wrote:
> > On Sunday, 23 July 2017 15:13:50 PDT Phil Bouchard wrote:
> > But that's just it: the GC doesn't happen as often if you're not under
> > memory pressure. You can postpone the GC to later and run it less often,
>
On Monday, 24 July 2017 00:00:36 PDT Marc Mutz wrote:
> Hi,
>
> We haven't added deduction guides to any Qt class, yet. If you want to
> use bleeding-edge C++, use C++, iow: std::map.
std::map currently (GCC 7.1.1) works less well than QMap, since you can't even
trick it. The std::pair that std:
On Monday, 24 July 2017 04:26:55 PDT Martin Koller wrote:
> Why does my Qt build use the system installed /usr/lib64/libqgsttools_p.prl
> file and not the one from the build dir
"Because it was found".
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source T
Phil Bouchard wrote:
> Thiago Macieira wrote:
>> But this answers the fact that you did not write a complete replacement of
>> QML.
>
> No not yet obviously. I will try to write a Youtube presentation tonight.
Actually all you have to do is include all of:
- BB++ converter
- C++ conpiler
- Jav
Thiago Macieira wrote:
> On Sunday, 23 July 2017 15:13:50 PDT Phil Bouchard wrote:
>> On 07/23/2017 03:54 PM, Thiago Macieira wrote:
>>> A problem that can again be mitigated by adding more RAM. Sometimes it's
>>> easier/cheaper to just throw hardware at the problem than to rework the
>>> software
On Montag, 24. Juli 2017 08:34:56 CEST Thiago Macieira wrote:
> On Sunday, 23 July 2017 23:03:04 PDT Kevin Kofler wrote:
> > Thiago Macieira wrote:
> > > This is the root of your problem. Something that this plugin or
> > > qgsttools_p needs to link to said that its libraries are in /usr/lib64.
> >
On Montag, 24. Juli 2017 08:32:23 CEST Thiago Macieira wrote:
> On Sunday, 23 July 2017 22:58:02 PDT Martin Koller wrote:
> > So the bug in fact is that qt does not give a correct name for
> > libQt5MultimediaGstTools.prl ?
>
> I don't know if that's a bug. I've never felt a problem with the .prl
On Mon, Jul 24, 2017 at 07:58:30AM +0200, Kevin Kofler wrote:
> Thiago Macieira wrote:
> > No, this is the solution, unless you want to build in a chroot'ed build
> > root. In the environment where you're going to build a given software, you
> > must not have the development packages of that softwa
On Fri, Jul 21, 2017 at 02:55:26PM +0200, Simon Hausmann wrote:
>I was under the impression that
>
>
>
> [1]http://code.qt.io/cgit/qt/qtbase.git/tree/qmake/generators/makefile.cpp#n1304
>
>was the code path hit if the entry in foo.files is not a "//real file or
>target" (as
Hi,
I think there are almost no need for deduction guides, for example a
similar program using QVector compiles fine on gcc-7:
--
#include "qapplication.h"
#include "qvector.h"
#include "qdebug.h"
int main(int argc, char *argv[])
{
Hi,
We haven't added deduction guides to any Qt class, yet. If you want to
use bleeding-edge C++, use C++, iow: std::map.
Patches welcome, bug reports accepted.
Thanks,
Marc
On 2017-07-24 06:32, Henry Skoglund wrote:
Hello, I've been testing more C++17 class template auto deduction
awith gc
23 matches
Mail list logo
