Hello,
Qt-5.4.0 was built from sources at 10.9 build machine
with flag -no-c++11
and in qtbase/mkspecs/macx-clang/qmake.conf
was set:
QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.6
The application does run at 10.6 target but crashes:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID
On Monday 26 January 2015, Ilya Kowalewski wrote:
> The label itself has nothing to do with messages or notifications. As you
> can see on the screenshot, it's informative string assigned to the icon
> itself. A possible usecase I keep in mind is to display number of unread
> messages there (for a
> On 26 Jan 2015, at 09:09, Robert Iakobashvili wrote:
>
> It seems that QStyle returns 0.
>
> Should I create some style in advance and pass it to application?
> Which style could be appropriate for 10.6?
>
> Yes, I know that 10.6 is not a supported target for 5.4.0,
> but any advise or direc
Dear Morten,
Thank you very much!
Sincerely,
Robert
On Mon, Jan 26, 2015 at 10:53 AM, Sorvig Morten <
morten.sor...@theqtcompany.com> wrote:
>
> > On 26 Jan 2015, at 09:09, Robert Iakobashvili
> wrote:
> >
> > It seems that QStyle returns 0.
> >
> > Should I create some style in advance and pas
Hi,
Gerrit upgrade rescheduled for next Tuesday morning, Jan-27, starting 07:00 CET.
Estimate for down time is max three hours.
BR,
Ismo
From: development-bounces+ismo.haataja=theqtcompany@qt-project.org
[mailto:development-bounces+ismo.haataja=theqtcompany@qt-project.org] On
Behalf Of
On Friday 23 January 2015 15:03:44 Turunen Tuukka wrote:
> Hi,
>
> *.qt-project.org certificate will expire 25th Jan. New one is ordered, but
> will take a bit more time to be in use.
I guess that's the reason why no integration succeeds in qtbase atm (always
some ssl test error)?
If so, it mig
Hello,
What would be the possibility of getting the CI system to build for QNX 6.5.0,
apart from 6.6.0 which it already does?
Currently, I have been manually searching for merge requests that cause
regressions but from time to time something always manages to slip thru, last
case being https://co
On 26 January 2015 at 19:28, Marc Mutz wrote:
> I guess that's the reason why no integration succeeds in qtbase atm (always
> some ssl test error)?
>
> If so, it might be a good idea to suspend qtbase integration tasks until
> it's
> fixed, unless people like to have it running as a compilation o
Sigh. It looks like some of the tests are using qt-project.org even though
they aren't supposed to:
void
tst_QSslSocket_onDemandCertificates_member::onDemandRootCertLoadingMemberMethods()
{
QString host("qt-project.org");
// not using any root certs -> should not work
QSslSocketPtr so
Hi
Would it be enough if we added it only to the nightly 'state' builds? Having it
in the general configurations would once again increase the load that's already
quite high. Building it once a day per branch for the whole Qt5 wouldn't be
that bad.
-Tony
> -Original Message-
> From: d
10 matches
Mail list logo
