25.11.2016, 03:38, "Kevin Kofler" :
> Lars Knoll wrote:
>> There are a lot of good arguments towards using the STL and libstdc++
>> more, as it will allow us to interoperate better with the C++ standard,
>> and provides a couple of things that we really want to use. So I can see
>> many good
Den 23-11-2016 kl. 23:10 skrev Thiago Macieira:
On quarta-feira, 23 de novembro de 2016 21:14:52 PST Simon Everts wrote:
That is not relevant here. I am using Windows 10 (64-bit) but I am still
forced (because of 3rt-party-libraries) to develop 32-bit-Qt-applications.
Even if the operating syste
Friedrich W. H. Kossebau wrote:
> Though your comment points to the issue of multiple versions of some libs
> being installed at the same time: if their respective QCH files are all
> being automatically added in Qt Assistant & Co., this will result in some
> confusion, especially when it comes to
Lars Knoll wrote:
> There are a lot of good arguments towards using the STL and libstdc++
> more, as it will allow us to interoperate better with the C++ standard,
> and provides a couple of things that we really want to use. So I can see
> many good arguments towards going down that route. Doing s
Marco Bubke wrote:
> * easier life of Linux packager
Where what you call "easier life" is really a question about whether
distributions can continue shipping Qt at all (at least current versions of
Qt, as opposed to sticking to an LTS version forever, even beyond its EOL
and even ignoring futur
Hi,
Am Donnerstag, 24. November 2016, 11:08:56 CET schrieb Lisandro Damián Nicanor
Pérez Meyer:
> On jueves, 24 de noviembre de 2016 07:38:20 ART Uwe Rathmann wrote:
> > On Tue, 22 Nov 2016 18:05:20 +0100, Friedrich W. H. Kossebau wrote:
> > > Q1: what would be a good system path pattern (on *nix
Hi Uwe,
Am Donnerstag, 24. November 2016, 07:38:20 CET schrieb Uwe Rathmann:
> On Tue, 22 Nov 2016 18:05:20 +0100, Friedrich W. H. Kossebau wrote:
> > Q1: what would be a good system path pattern (on *nixoid systems) for
> > Qt-based libraries to install their QCH files to?
>
> Qwt ( http://qwt.s
On 2016-11-22 06:25, Marco Bubke wrote:
> On November 22, 2016 08:17:57 Thiago Macieira wrote:
>> Theming and styling is a complex operation. It's not just "propagating
>> values". Reading config files will at best get you the right font, correct
>> icon
>> set, and somewhat correct colours. But
So you are writing a style for the QPaintEngine. What if you have a OpenGL back
end or some other back ends where your descriptions does not fit that well any
more? I have seen much more complicated things written in an abstract way, so
it should be possible. And I haven't said that you should u
On jueves, 24 de noviembre de 2016 07:38:20 ART Uwe Rathmann wrote:
> On Tue, 22 Nov 2016 18:05:20 +0100, Friedrich W. H. Kossebau wrote:
> > Q1: what would be a good system path pattern (on *nixoid systems) for
> > Qt-based libraries to install their QCH files to?
>
> Qwt ( http://qwt.sf.net ) of
Hi,
I'd like to nominate Teemu Holappa for the Approver status. He joined Digia
(now The Qt Company) 3+ years ago as a Qt consultant. Teemu has contributed to
meta-boot2qt and anything else that needs fixing to get Qt for Device Creation
releases out the door.
Here is his gerrit dashboard:
ht
> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Thiago
> Macieira
> I know the sample size here is horrible, but in your opinion what compiler
> should
> we keep offering a 32-bit binary build for?
>
> MSVC 201
Op wo 23 nov. 2016 om 23:10 schreef Thiago Macieira <
thiago.macie...@intel.com>:
>
> I know the sample size here is horrible, but in your opinion what compiler
> should we keep offering a 32-bit binary build for?
>
> MSVC 2013
> MSVC 2015
> MinGW
>
>
Currently we're using Qt5.5 with MSVC2010 and
13 matches
Mail list logo
