On 24 February 2015 at 03:49, Kevin Kofler wrote:
>
>> * RHEL 7 ships 1.0.1, EOL Jun 2014
>> * CentOS 7 ships 1.0.1, EOL Jun 2014
>
> I think you mean 2024 there (2014 + 10 years).
Whooops, yes, of course. My bad...
>> Of course there are other considerations, like RHEL/CentOS 6 both
>> shipping
Hi all,
If I have understood correctly merge from 'dev' to '5.5' should solve this
issue. Or does someone disagree?
Br,
jani
>>-Original Message-
>>From: development-bounces+jani.heikkinen=theqtcompany.com@qt-
>>project.org [mailto:development-
>>bounces+jani.heikkinen=theqtcompany@
On Feb 24, 2015 8:06 AM, "Adam Majer" wrote:
>
> By rewrite, he meant *port to*. So, you don't have to rewrite
> anything, "just" port it to the API that is available on a given
> platform. By porting it to Qt, then it would be automatically
> available everywhere that Qt is available.
>
> If the
On Mon, Feb 23, 2015 at 07:48:37AM +0100, Mathias Hasselmann wrote:
> Am 17.02.2015 um 14:36 schrieb Cristian Adam:
> > One could rewrite this small utility into Qt and then it would be
> > available everywhere.
>
> Somehow I thought that one of the big benefits of free software and open
> source
Hello,
i am trying to build qt5.5 from git on windows . i do not want to make a deveolper build but want to build the code as i normally do.
After creating the configure.exe, configureing and starting the build, qtcore build fails because it cannot find headers, which normally reside in qtbase\in
Hello list,
I discussed a bit with Thiago and some others on irc this evening and have
realized that the QStandardPaths patch from [1] and discussion on [2] is
trying to solve too many problems at once. I'll list the problems here and
some possible solutions to these problems afterwards so we can
Giuseppe D'Angelo wrote:
> * RHEL 7 ships 1.0.1, EOL Jun 2014
> * CentOS 7 ships 1.0.1, EOL Jun 2014
I think you mean 2024 there (2014 + 10 years).
> Of course there are other considerations, like RHEL/CentOS 6 both
> shipping GCC 4.4, so we might end up dropping support for those
> distributions
Hello Everybody,
I am trying to use a multi-touch screen with my qt application. I have
downloaded the qt 5.4 for Linux (Ubuntu 14.04). But unfortunately
Gesture event does not deliver to the event function.
My goal to catch swipe gesture then assign some task to do so.
I tried to download Qt 5.
On Mon, Feb 23, 2015 at 08:44:57PM +, Richard Moore wrote:
> The qtbase 5.5 branch has been blocked by the revdep for qtdeclarative all
> weekend, but I'm still seeing people staging stuff there. Is anyone
> actually looking at fixing the problem, or are people just blindly staging
> things? Th
The qtbase 5.5 branch has been blocked by the revdep for qtdeclarative all
weekend, but I'm still seeing people staging stuff there. Is anyone
actually looking at fixing the problem, or are people just blindly staging
things? The evidence suggests the latter. :-(
https://codereview.qt-project.org/
I think Kai's approach is probably what would work best for now. As much
as I'd like to, we can't yet use C++11 features unconditionally inside the
core of Qt itself as we'd loose a few platforms that we still need to
support.
But we can (and should) certainly use C++11 in our examples and
documen
On 23/02/15 15:37, "Thiago Macieira" wrote:
>On Monday 23 February 2015 13:20:48 Oswald Buddenhagen wrote:
>> On Mon, Feb 23, 2015 at 12:00:51PM +, Knoll Lars wrote:
>> > Yes, I still don’t like the fact we’re embedding a 1.7M xml file in Qt
>> > Core at all. I’m not too fond of checking the
On Monday 23 February 2015 13:20:48 Oswald Buddenhagen wrote:
> On Mon, Feb 23, 2015 at 12:00:51PM +, Knoll Lars wrote:
> > Yes, I still don’t like the fact we’re embedding a 1.7M xml file in Qt
> > Core at all. I’m not too fond of checking the binary file into the
> > repositories, but it’s pr
On Monday 23 February 2015 10:08:43 Mathias Hasselmann wrote:
> Am 23.02.2015 um 08:11 schrieb Thiago Macieira:
> > On Monday 23 February 2015 07:48:37 Mathias Hasselmann wrote:
> >> Am 17.02.2015 um 14:36 schrieb Cristian Adam:
> >>> One could rewrite this small utility into Qt and then it would b
On 20 February 2015 at 16:28, Koehne Kai wrote:
>> -Original Message-
>> From: development-bounces+kai.koehne=theqtcompany.com@qt-
>> [...]
>> But this is an implementation convenience only. You can't convince me to
>> drop VS2010 to be able to use them internally inside Qt. Or 2008 for Wi
On Monday 23 February 2015 14:39:49 Arnaud Vrac wrote:
> That's true, but the binary file in QStandardPaths::GenericDataLocation +
> "mime/mime.cache" should have been rebuilt with those additional XML files.
Only on systems with shared-mime-info installed.
The XML provider makes things work also
On Mon, Feb 23, 2015 at 2:11 PM, David Faure wrote:
> On Monday 23 February 2015 12:00:51 Knoll Lars wrote:
> > Yes, I still don’t like the fact we’re embedding a 1.7M xml file in Qt
> > Core at all. I’m not too fond of checking the binary file into the
> > repositories, but it’s probably still b
On Monday 23 February 2015 12:00:51 Knoll Lars wrote:
> Yes, I still don’t like the fact we’re embedding a 1.7M xml file in Qt
> Core at all. I’m not too fond of checking the binary file into the
> repositories, but it’s probably still better than continuing with the XML
> file.
Yes. The binary fi
> On 23 Feb 2015, at 13:00, Knoll Lars wrote:
>
>
> Yes, I still don’t like the fact we’re embedding a 1.7M xml file in Qt
> Core at all. I’m not too fond of checking the binary file into the
> repositories, but it’s probably still better than continuing with the XML
> file.
For OS X I’d like
On Mon, Feb 23, 2015 at 12:00:51PM +, Knoll Lars wrote:
> Yes, I still don’t like the fact we’re embedding a 1.7M xml file in Qt
> Core at all. I’m not too fond of checking the binary file into the
> repositories, but it’s probably still better than continuing with the XML
> file.
>
there is n
On 22/02/15 19:20, "David Faure" wrote:
>On Thursday 19 February 2015 01:55:01 Kevin Kofler wrote:
>> Arnaud Vrac wrote:
>> > Commit fbeeaf2 in qtbase adds QT_NO_MIMETYPE:
>> >
>> > "The mime type stuff generates one of the biggest translation units in
>> > QtCore due to the compressed 1.7MB f
On 23/02/15 10:08, "Mathias Hasselmann" wrote:
>Am 23.02.2015 um 08:11 schrieb Thiago Macieira:
>> On Monday 23 February 2015 07:48:37 Mathias Hasselmann wrote:
>>> Am 17.02.2015 um 14:36 schrieb Cristian Adam:
One could rewrite this small utility into Qt and then it would be
available
Am 23.02.2015 um 08:11 schrieb Thiago Macieira:
> On Monday 23 February 2015 07:48:37 Mathias Hasselmann wrote:
>> Am 17.02.2015 um 14:36 schrieb Cristian Adam:
>>> One could rewrite this small utility into Qt and then it would be
>>> available everywhere.
>>
>> Somehow I thought that one of the bi
23 matches
Mail list logo
