Hello Andreas,
maybe you read my mail to fast. Especially , you seem to have skipped the
>> SSL support.no
>> OpenSSL support.yes
and
> I assume this this is with -openssl passed to configure? From my reading
> of the code, that's the only possibility. Is "openssl
On 2015-07-30 03:38, Gerhard Scheikl wrote:
> The behavior of QString::trimmed has changed from 5.3.2 to 5.5.
> .trimmed() on an empty string (" ") makes it null
> .trimmed() on an empty string ("") doesn't make it null
>
> Is this intended or a bug?
Whether or not it is¹ should not be relevant;
On Thursday 30 July 2015 11:47:16 Olivier Goffart wrote:
> On Thursday 30. July 2015 09:38:12 Gerhard Scheikl wrote:
> > Hi
> >
> > The behavior of QString::trimmed has changed from 5.3.2 to 5.5.
> > .trimmed() on an empty string (" ") makes it null
> > .trimmed() on an empty string ("") doesn't m
On Thursday 30. July 2015 13:33:28 Tomasz Siekierda wrote:
> Hi,
>
> just a quick observation: QNoDebug class can be used in code (compiles,
> works fine), but there is no documentation for it.
>
> Is that intentional? Shouldn't it be either hidden (made private) or
> documented? Although I have
Hi,
just a quick observation: QNoDebug class can be used in code (compiles,
works fine), but there is no documentation for it.
Is that intentional? Shouldn't it be either hidden (made private) or
documented? Although I have just learned about it's existence by accident,
it looks like it can be qu
They are working on it. The first step in working on it is detecting it.
`Allan
On Thursday 30 July 2015, Gunnar Roth wrote:
> Hmmm ok, but for me it looks lije it is supported in master,
> https://chromium.googlesource.com/chromium/src/+/master/build/vs_toolchain.
> py
>
> 1. def_VersionNumber(
Hmmm ok, but for me it looks lije it is supported in master,
https://chromium.googlesource.com/chromium/src/+/master/build/vs_toolchain.py
1. def_VersionNumber():
2. """Gets the standard version number ('120', '140', etc.) based on
3. GYP_MSVS_VERSION."""
4. ifos.environ['GYP_MSVS_VERSION']=='20
On Thursday 30. July 2015 09:38:12 Gerhard Scheikl wrote:
> Hi
>
> The behavior of QString::trimmed has changed from 5.3.2 to 5.5.
> .trimmed() on an empty string (" ") makes it null
> .trimmed() on an empty string ("") doesn't make it null
>
> Is this intended or a bug?
This is caused by 54da2b
On Thursday 30 July 2015, Gunnar Roth wrote:
> Hello,
> does anybody now if and when QtWebEngine will build with VS1025?
>
When Chromium starts supporting building with VS2015. So far it doesn't looks
like it will be in 5.6
`Allan
___
Development maili
Hello,
does anybody now if and when QtWebEngine will build with VS1025?
I build Qt 5.5.0 for win32 64 bit but in th ened there was no
qtwebengine build.
I discovered qtwebengine\tools\qmake\mkspecs\features\functions.prf
and added win32-msvc2015
to the line linux-g++*|win32-msvc2013|macx-clang:
Hi
The behavior of QString::trimmed has changed from 5.3.2 to 5.5.
.trimmed() on an empty string (" ") makes it null
.trimmed() on an empty string ("") doesn't make it null
Is this intended or a bug?
By the way: the output of qDebug is not as expected:
there are additional whitespaces before tru
On 07/30/2015 12:16 AM, Gunnar Roth wrote:
> My effect is that QT_NO_SSL is defined which leads to 100’s of errors.
>
> And i did pass -openssl to configure. I patched configureapp.cpp by removing
> that no’s for opens and ssl ( the result i can see tomorrow)
> and by the way i think the sse2/3/4
yes i'm
2015-07-30 8:49 GMT+02:00 Curtis Mitch :
> I thought that you were writing tests within Qt?
>
>
>
> *From:* Filippo Cucchetto [mailto:filippocucche...@gmail.com]
> *Sent:* Thursday, 30 July 2015 8:41 AM
> *To:* Curtis Mitch
> *Cc:* development@qt-project.org
> *Subject:* Re: [Developmen
13 matches
Mail list logo
