Solution:
qmake renamed to qmake5 and lives with the other binaries in libexec/bin
Create /usr/bin/qmake5 as a symlink to libexec/bin/qmake5 for Linux
distro builds - triggered by some set of configure flags, NOT default
behaviour for a source build
You definitely don't want support
On 10/24/2012 01:12 AM, d3fault wrote:
On 10/23/12, Lincoln Ramsay a1291...@gmail.com wrote:
We're not renaming things or creating new lists just to match the
names you think we should have.
*sigh*, I had a feeling someone would say something like that.
The changes are trivial at a glance,
Hi everybody,
we are still having problems with the QmlImportPath. There is also already a
bug reported:
https://bugreports.qt-project.org/browse/QTBUG-20539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel
Reminder: The problem looks like this. We have a custom plugin
On 23 Oct 2012, at 19:03, Thiago Macieira thiago.macie...@intel.com
wrote:
On terça-feira, 23 de outubro de 2012 16.33.05, Ziller Eike wrote:
So that if you happen to have a real qmake instead of the wrapper in
the
PATH on linux, you don't realize that when you are doing qmake -qt5 to
On 24 Oct 2012, at 08:04, Konstantin Ritt ritt...@gmail.com
wrote:
Solution:
qmake renamed to qmake5 and lives with the other binaries in libexec/bin
Create /usr/bin/qmake5 as a symlink to libexec/bin/qmake5 for Linux
distro builds - triggered by some set of configure flags, NOT default
-Original Message-
From: development-bounces+kai.koehne=digia@qt-project.org
[mailto:development-bounces+kai.koehne=digia@qt-project.org] On
Behalf Of Wehmer, Matthias
Sent: Wednesday, October 24, 2012 9:56 AM
To: development@qt-project.org
Subject: [Development]
On Tuesday 23. October 2012 19.34.46 Harri Porten wrote:
On Tue, 23 Oct 2012, Mitch Curtis wrote:
After https://codereview.qt-project.org/#change,37988, the Serializing
Qt Data Types page lists the QDataStream version as 13. I thought it'd
be a good idea to ask everyone who is interested to
On 10/24/12, Samuel Rødal samuel.ro...@digia.com wrote:
Lars and Charles both provided good lists of reasons in another part of
this thread for going with the policy of Responsible Disclosure. Clearly
you disagree on the weighting of the pros and cons, but it doesn't seem
like you're able to
On Wed, 24 Oct 2012, Jedrzej Nowacki wrote:
I added that tests durring Qt5 development, sadly streaming was never tested
with older versions. What is the bug, can I help somehow? Is it only Qt5 or
Qt4 too?
We found the reason now:
https://bugreports.qt-project.org/browse/QTBUG-27700
Hi everybody!
As you may remember from last year, the Qt Developer Days in both Munich and
San Francisco, on the first day of the conference there were two options:
Training and the Qt Contributors Day. This year will be no different, and so,
i am very happy to announce the immediate opening
Hi,
I'm stepping down as the maintainer of QtWayland, as I don't have time
to ensure that QtWayland is in top notch shape.
I would like to propose Andy Nichols as the new maintainer.
Jørgen
___
Development mailing list
Development@qt-project.org
tl;dr:
d3fault if you keep up the good work you can join the security team
the security team is for trustworthy individuals
d3fault, we don't trust you
How is my keeping up the good work earning trust? Do you guys really
not see the gaping hole in that logic?
d3fault
On Wed, Oct 24, 2012 at 11:55 AM, d3fault d3faultdot...@gmail.com wrote:
tl;dr:
How is my keeping up the good work earning trust? Do you guys really
not see the gaping hole in that logic?
I do certainly have problem trusting people that show that much interest
in getting access to all
Solution:
qmake renamed to qmake5 and lives with the other binaries in libexec/bin
Create /usr/bin/qmake5 as a symlink to libexec/bin/qmake5 for Linux
distro builds - triggered by some set of configure flags, NOT default
behaviour for a source build
You definitely don't want support
On 24/10/12 4:04 PM, Konstantin Ritt wrote:
You definitely don't want support multiarch configurations out-of-the-box :)
Well, yeah, switching with `sudo ln -svf /usr/lib/qt5/libexec/qmake5
/usr/bin/qmake5` is a way more handy than with `qmake -set-qt 5.0-x86`
(or even with `qmake -set-qt
Please disregard Zeno's personal attacks towards me and his request that
the subject die and we all move on. His type of email is exactly what I
describe two emails back. Waste (so is this one, except to keep the subject
alive).
If you can't say something relevant [to the argument], don't say
On 10/24/2012 11:30 AM, d3fault wrote:
On 10/24/12, Samuel Rødal samuel.ro...@digia.com wrote:
Lars and Charles both provided good lists of reasons in another part of
this thread for going with the policy of Responsible Disclosure. Clearly
you disagree on the weighting of the pros and cons,
+1
I've overheard Andy in hallway conversations where he switched occasionally
from English (accented) to the wayland protocol (1.0 final spec) and back.
Simon
--
Sendt fra min Nokia N924.10.12 12:03 skrev Paul Olav Tvete:
On Wednesday 24 October 2012 11:51:09 Jørgen Lind wrote:
I'm stepping
On 10/24/2012 05:50 PM, Hausmann Simon wrote:
+1
I've overheard Andy in hallway conversations where he switched occasionally
from English (accented) to the wayland protocol (1.0 final spec) and back.
+1 from me as well :)
--
Samuel
___
On 10/24/2012 12:16 PM, Łukasz Korbel wrote:
Hello,
I have build Qt5 Beta following instructions from
http://qt-project.org/wiki/Android (with some small fixes for paths)
I noticed that qt had built without QtDeclarative module, so I've built
it manually.
Its still not recognized as a
That is a mighty beautiful link
On Wed, Oct 24, 2012 at 9:54 AM, Samuel Rødal samuel.ro...@digia.com wrote:
On 10/24/2012 12:16 PM, Łukasz Korbel wrote:
Hello,
I have build Qt5 Beta following instructions from
http://qt-project.org/wiki/Android (with some small fixes for paths)
I noticed
On Oct 24, 2012, at 5:59 PM, Samuel Rødal samuel.ro...@digia.com wrote:
On 10/24/2012 05:50 PM, Hausmann Simon wrote:
+1
I've overheard Andy in hallway conversations where he switched occasionally
from English (accented) to the wayland protocol (1.0 final spec) and back.
+1 from me as
On 10/24/12, Samuel Rødal samuel.ro...@digia.com wrote:
As far as I see it all the options have vulnerabilities, so it shouldn't
be hard to prove that they exist within either approach.
Yep. Close one giant security-through-obscurity vulnerability, open
the door for script kiddies. It's a
Hi,
we are still having problems with the QmlImportPath. There is also already
a bug reported:
https://bugreports.qt-project.org/browse/QTBUG-
20539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel https://bugreports.qt-project.org/browse/QTBUG-
Replying here to some comments on IRC, since I'm rarely online at the
same time as the others, but I don't want to let all the comments go
unanswered...
steveire [06:32:44] CI is seriously depresssing. For the last 24 hours
there has been one successful merge. Many of the others are failing
On 25/10/12 13:00, Rohan McGovern wrote:
True, there used to be Nokia employees reading every failure report and
chasing up apparently unstable tests, either trying to fix the tests, or
acknowledge them via bug reports and marking them insignificant.
Those people are gone and the test results
26 matches
Mail list logo
