Using the manifest kludge only delays the problem. When the next 8.x
version of Windows is released GetVersionEx will presumably resume lying
to Qt/your application about the Windows version you are running. Which
version it gives you is anyone's guess.
On 21/10/13 04:47, Raul Metsma wrote:
El Martes, 22 de octubre de 2013, Knoll Lars escribió:
> So much for Linux distributions keeping binary compatibility.
Isn't exactly the same situation as with Qt? When the "next version of Qt 4.8"
breaks binary compatibility, libqt5 is introduced. You link against either one
or the other, and g
Hello,
It's time for final testing of Beta candidate packages. The aim is to make sure
that there are no blocking issues before the Beta release at 12:00 CET on
Wednesday.
Could you help us with testing?
1. Packages are available here (build #109):
http://download.qt-project.org/snapshots
HarfBuzz-NG supports OT font sanitizing. Since Qt 5.2, there is an
experimental HB-NG shaper backend (turned off by default).
Regards,
Konstantin
2013/10/22 GD dev
> Hi there,
>
> I was wondering if latest Qt (5.2) has/plans to have font sanitizer,
> something like OpenType font sanitizer in C
On terça-feira, 22 de outubro de 2013 15:51:56, Philip Ashmore wrote:
> Sounds like you need a generic plug-in framework that allows you to ask
> for a "udev" component that you ask for an IUDev interface.
>
> Oh wait, I've written one, called v3c-dcom, available in SourceForge.
We have it too: i
On Tuesday 22 October 2013 15:44:00 Simon Hausmann wrote:
> On Tuesday 22. October 2013 15.35.24 Tobias Hunger wrote:
> > On 22.10.2013 15:31, Nicolás Alvarez wrote:
> > > I don't think the standard is relevant here. The C++ standard doesn't
> > > and can't say anything about whether 'break' and 'c
On 22/10/13 15:42, Thiago Macieira wrote:
> On terça-feira, 22 de outubro de 2013 11:39:30, Pau Garcia i Quiles wrote:
>> What about dlopen/dlsym?
>
> I hate that option. I hate where we use it and I'd rather we didn't.
>
> In particular, since we're trying to locate one of two major versions, we
On terça-feira, 22 de outubro de 2013 14:08:28, Martin Smith wrote:
> > actually, I think that he shouldn't go through this process since he was
> > a Nokia employee before Open Governance was in place, so he should have
> > been added before the Open Governance launch. If that was not the case,
>
On terça-feira, 22 de outubro de 2013 11:39:30, Pau Garcia i Quiles wrote:
> What about dlopen/dlsym?
I hate that option. I hate where we use it and I'd rather we didn't.
In particular, since we're trying to locate one of two major versions, we need
to try first the .so.1 version and, if that fa
Hi there,
I was wondering if latest Qt (5.2) has/plans to have font sanitizer,
something like OpenType font sanitizer in Chromium (
https://code.google.com/p/ots/wiki/DesignDoc), without which random user
fonts could leave embedded system (running Qt) open to security attacks.
Regards,
Gaurav Kam
On 22 October 2013 15:22, Keith Gardner wrote:
> Couldn't Q_FOREACH/foreach use the range based for loops if the compiler
> supports it? This way, there is no C++ trickery to enable the feature.
No, because the semantics are different.
--
Giuseppe D'Angelo
_
On Tuesday 22. October 2013 15.35.24 Tobias Hunger wrote:
> On 22.10.2013 15:31, Nicolás Alvarez wrote:
> > I don't think the standard is relevant here. The C++ standard doesn't
> > and can't say anything about whether 'break' and 'continue' are allowed
> > in a statement expression inside the 'for
On 22.10.2013 15:31, Nicolás Alvarez wrote:
> I don't think the standard is relevant here. The C++ standard doesn't
> and can't say anything about whether 'break' and 'continue' are allowed
> in a statement expression inside the 'for' header, because statement
> expressions don't exist in the stand
Hi all,
during one of the last release meetings, we had a chat about "Tier 1" or
reference platforms. I mentioned that IMHO the "Tier 1" notion known in Qt
prior Qt5 is not used in Qt5 anymore. I was not able to provide references off
the top of my head, and now I took some time to collect refe
El martes, 22 de octubre de 2013, Tobias Hunger escribió:
> I just noticed that clang from trunk is no longer able to build Qt
> applications. This is due to a change which makes clang consider "break"
> statements outside of a loop body or switch statement illegal.
>
> Unfortunately this triggers
On Tue, Oct 22, 2013 at 8:15 AM, Tobias Hunger wrote:
> Hello,
>
> I just noticed that clang from trunk is no longer able to build Qt
> applications. This is due to a change which makes clang consider "break"
> statements outside of a loop body or switch statement illegal.
>
> Unfortunately this t
Hello,
I just noticed that clang from trunk is no longer able to build Qt
applications. This is due to a change which makes clang consider "break"
statements outside of a loop body or switch statement illegal.
Unfortunately this triggers on each Q_FOREACH/foreach used by Qt
applications!
The
On Oct 22, 2013, at 1:06 PM, Sergio Ahumada wrote:
> On 10/22/2013 01:00 PM, Mitch Curtis wrote:
>> On 10/22/2013 11:53 AM, Martin Smith wrote:
>>> I nominate Topi as an approver. Topi has been the leader of the Qt
>>> documentation team in Oslo for a long time.
>>>
>>> A search for topi.rei..
On Tue, Oct 22, 2013 at 11:40 AM, Giuseppe D'Angelo wrote:
> On 22 October 2013 12:35, Laszlo Papp wrote:
> > PS.: But yes, so much for Linux distributions keeping binary
> compatibility.
> > :/
>
> PS: there is no such concept for non-LSB software. For those, you just
> need to compile it agains
On 10/22/2013 01:00 PM, Mitch Curtis wrote:
> On 10/22/2013 11:53 AM, Martin Smith wrote:
>> I nominate Topi as an approver. Topi has been the leader of the Qt
>> documentation team in Oslo for a long time.
>>
>> A search for topi.rei...@digia.com at codereview.qt-project.org shows that
>> Topi h
On 22 October 2013 13:00, Mitch Curtis wrote:
> On 10/22/2013 11:53 AM, Martin Smith wrote:
>> I nominate Topi as an approver. Topi has been the leader of the Qt
>> documentation team in Oslo for a long time.
>>
>> A search for topi.rei...@digia.com at codereview.qt-project.org shows that
>> Top
On 10/22/2013 11:53 AM, Martin Smith wrote:
> I nominate Topi as an approver. Topi has been the leader of the Qt
> documentation team in Oslo for a long time.
>
> A search for topi.rei...@digia.com at codereview.qt-project.org shows that
> Topi has been very active both submitting patches and rev
On 22 October 2013 12:35, Laszlo Papp wrote:
> PS.: But yes, so much for Linux distributions keeping binary compatibility.
> :/
PS: there is no such concept for non-LSB software. For those, you just
need to compile it against the distribution itself; binaries produced
by other means have no such
On Tue, Oct 22, 2013 at 8:27 AM, Knoll Lars wrote:
> On 22.10.13 09:24, "Thiago Macieira" wrote:
>
> >On terça-feira, 22 de outubro de 2013 07:01:22, Knoll Lars wrote:
> >> >There are two major versions of libudev in use in major distros:
> >> >libudev.so.0
> >> >and libudev.so.1. The new one ha
I nominate Topi as an approver. Topi has been the leader of the Qt
documentation team in Oslo for a long time.
A search for topi.rei...@digia.com at codereview.qt-project.org shows that Topi
has been very active both submitting patches and reviewing patches for the Qt
documentation and for the
Hello,
What about dlopen/dlsym?
Due to problems like this, InterSystems ( http://www.intersystems )
resorted to:
a) Distribute third-party dependencies, and
b) dlopen/dlsym *every* third-party dependency in their software (and they
have quite a lot: zlib, OpenSSL, Xerces, Samba, libXSLT, libXML2,
On terça-feira, 22 de outubro de 2013 07:27:50, Knoll Lars wrote:
> So much for Linux distributions keeping binary compatibility. Not
> providing the package means you break every 3rd party app that needs
> libudev and doesn't come as part of the package management.
Distros have never promised com
Hi guys,
e.g. related to QtSerialPort we can try to rewrite the libudev linking
dynamically.. I'm think..
Probably we will be in time to 5.2... :)
Best regards,
Denis
22.10.2013, 11:28, "Knoll Lars" :
> On 22.10.13 09:24, "Thiago Macieira" wrote:
>
>> On terça-feira, 22 de outubro de 2013 07:
Hello,
Not having libudev results in not having hotplugging and proper device
discovery for the evdev inputs plugins (and platforms that have the input stuff
built-in, like eglfs).
This does not mean those plugins will not build or will not work since there is
a (limited) fallback option that
Although not closely related to Qt development, I just wanted to say that while
IE10 could not load the Gerrit site, IE11 shipping with Windows 8.1 does render
the site correctly. From the few days testing, so far IE11 seems like a decent,
moreover capable browser, both the desktop and the touch
On 22.10.13 09:24, "Thiago Macieira" wrote:
>On terça-feira, 22 de outubro de 2013 07:01:22, Knoll Lars wrote:
>> >There are two major versions of libudev in use in major distros:
>> >libudev.so.0
>> >and libudev.so.1. The new one has been in use for about a year, so we
>>can
>> >expect the need
On terça-feira, 22 de outubro de 2013 07:01:22, Knoll Lars wrote:
> >There are two major versions of libudev in use in major distros:
> >libudev.so.0
> >and libudev.so.1. The new one has been in use for about a year, so we can
> >expect the need to support both versions for the next few years of bu
On 22.10.13 08:09, "Thiago Macieira" wrote:
>On terça-feira, 22 de outubro de 2013 06:05:13, Hausmann Simon wrote:
>> I think the problem is shipping binaries that accommodate the fact that
>> every distro ships libudev in a different major version. That means you
>> can't reliably use dynamic li
33 matches
Mail list logo
