redirect stdout to
/dev/null. The reasons why it failed are printed on stderr.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
};
QByteArray toJson() const; //### Merge in Qt6
QByteArray toJson(JsonFormat format) const;
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
::deleteLater);
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
QDBusConnection::callWithCallback. And that one is made
simpler and easier by QDBusPendingReply and QDBusPendingCallWatcher, two
classes inspired by QFuture and QFutureWatcher.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
On segunda-feira, 4 de março de 2013 14.49.15, Thiago Macieira wrote:
I think the proposed API addition is actually quite natural. It is not
without precedent (QTimer::singleShot()), and would result in quite
simple, readable code.
I disagree on both accounts. It's not natural
On terça-feira, 5 de março de 2013 08.38.17, André Somers wrote:
I'd appreciate a reply on the point that when using a QFutureWatcher,
you don't know if the future is already done or not at the moment you
connect.
It's not done, by construction.
--
Thiago Macieira - thiago.macieira
On terça-feira, 5 de março de 2013 08.54.35, André Somers wrote:
Op 5-3-2013 8:41, Thiago Macieira schreef:
On terça-feira, 5 de março de 2013 08.38.17, André Somers wrote:
I'd appreciate a reply on the point that when using a QFutureWatcher,
you don't know if the future is already done
should setup the connection before the future.
Fair enough. You can create the QFutureWatcher before the future. The code is
even more clear that way.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
Download at:
http://macieira.org/qtchooser/
Changelog:
Frederik Gladhorn (3):
Make bash script work
Make messages slightly nicer.
Warn about recursive calls
Shawn Rutledge (1):
Expand leading tilde in tool path (for e.g. ~/dev/qt5)
Thiago Macieira (10):
Add
to be built-in to QtCore depending on the
configuration: we need the locale codec in order to translate paths from
UTF-16.
You'll probably run into an infinite loop unless you completely avoid QString
and all our FS classes.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel
disconnected. The
receiver needs to deal with it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
On domingo, 10 de março de 2013 23.54.42, Sze Howe Koh wrote:
What's holding us back? What does installing the moc file mean?
You install the output from moc.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
it. I'd much
rather use real iOS-looking controls than simply slap on Fusion.
The whole point is that you shouldn't use QtWidgets at all on mobile
platforms. Just don't.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
On segunda-feira, 11 de março de 2013 19.45.48, André Pönitz wrote:
On Mon, Mar 11, 2013 at 08:37:19AM -0700, Thiago Macieira wrote:
On segunda-feira, 11 de março de 2013 07.41.02, Jake Thomas Petroules
wrote:
Jens claimed on the blog that the native look and feel matters less
.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http://lists.qt
to real embedded, and
it does not scale up to the usual bunch of engineering applications
Qt was serving well in the past.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
that at least one QtCore developer supports this approach
anyway.
Did he also mention that the QtCore maintainer thinks that using one type for
all of those is a bad idea?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
reporter
is way too involved to make that assessment.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing
of the Core: Event
system bugs that I receive and reassign to GUI: Window management become
Unassigned.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
no such API (read: it's not QtWidgets!). So we have two
options: create and develop it, or not. The question is: if we need to
implement it, do we need to implement it before the QML API?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
will not see it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http
. If there is
no semi-colon, do not add one.
I also recommend not touching the unnecessary braces. Those are usually the
result of code changes inside the block. The non-whitespace churn is entirely
unnecessary.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology
-
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http://lists.qt
On domingo, 17 de março de 2013 11.13.01, Olivier Goffart wrote:
On Sunday 10 March 2013 10:09:24 Thiago Macieira wrote:
On domingo, 10 de março de 2013 23.54.42, Sze Howe Koh wrote:
What's holding us back? What does installing the moc file mean?
You install the output from moc.
Yes
to the mailing list that discusses development of Qt. You
have a Qt 4 problem.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
depend on?
Will you make moc's output files respect source- and binary-compatibility?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
to the conclusion
that creating old/5.0 is a good idea.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing
been assigned a new bug.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt
of the functionality I've been working on,
I encourage you to give it a try. It might make you change your mind
about QIosStyle being a waste of time. :)
I appreciate your work and wish you success. But please be prepared to accept
failure too.
--
Thiago Macieira - thiago.macieira
On terça-feira, 19 de março de 2013 15.02.35, Olivier Goffart wrote:
On Monday 18 March 2013 07:49:07 Thiago Macieira wrote:
We are talking about it.
As the one who says -2, you are the one who is supposed to state your
objections.
I did. I said I wanted to discuss this more before it went
On terça-feira, 19 de março de 2013 14.55.57, Ahumada Sergio wrote:
On 12/19/2012 04:56 PM, Thiago Macieira wrote: On quarta-feira, 19 de
dezembro de 2012 14.07.29, List for announcements
regarding Qt releases and development wrote:
Please check out my blog post post at
http
is that
there will be no further 5.0.x releases. And even if there are due to security
issues, we may choose to branch off the release tag.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed
is that the 5.1.0 release process takes
longer than expected. If we can't get 5.1.0 out within 3 months of 5.0.2, I'll
be among those requesting a 5.0.3 release. There are currently 101 patches in
stable that aren't in releases (97 not cherry-picked, according to git
cherry).
--
Thiago Macieira
).
The online installer isn't enough or suitable for people who want to build
from sources. But I guess that we can just leave a link to download.qt-
project.org for the source download.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
beyond just running 'configure' and 'make'...
I agree with that. We should include instructions (or a link) to how to clone
from Git and contribute.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
(*)
Wintab
XCB
zlib (*)
qtimageformats:
libmng
libtiff
qtjsbackend:
V8
qtscript:
JavaScriptCore
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
-picked, both of which are bad.
Obviously the bugfixing of stuff that is *only* in dev needs to go to dev, until
that content appears on stable too.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http://lists.qt
On quarta-feira, 20 de março de 2013 09.50.22, Thiago Macieira wrote:
We're feature-freezing 5.1. It's time to verify if any of the third-party
libraries we include in Qt need updating to newer versions. I recommend
updating all of them to their latest versions.
Actually, the merges
will say it in
capital letters so everyone understands:
QT 5.1 IS FEATURE FROZEN
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
that we don't use our own zlib on sane systems, where the
system copy is usually highly optimised.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
the testlines
depending on the PCRE version (!)
I'd say upgrade the bundled copy and update the test to match, but leave the
minimum version unchanged. The bug is a corner-case.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
-stable in qt history, I think.
It's not the first dev-stable merge. The direction does not matter. This merge
is no different than the previous ones.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
as it
has always been ever since we introduced Git usage for Qt, back in 2008.
(I'm sure there was a blog, with a picture of Lars and Simon talking to the
sysadmins, turning the Git repository live for the first time, but I can't find
it)
--
Thiago Macieira - thiago.macieira (AT) intel.com
used the bundled copy -- no distro we were
testing had the minimum required PCRE.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
On quinta-feira, 21 de março de 2013 10.06.00, Thiago Macieira wrote:
(I'm sure there was a blog, with a picture of Lars and Simon talking to the
sysadmins, turning the Git repository live for the first time, but I can't
find it)
Thanks to Daniel:
http://blog.qt.digia.com/blog/2008/09/28/qt
]
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http://lists.qt
better EGL headers from
your vendor, with no X11 requirements?
PS: please send text emails
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
/QUrl.html.h:1:0,
2.
from
../../../../include/QtGuihttp://qt-project.org/doc/QtGui.html/../../src/gui/kernel/qeventhttp://qt-project.org/doc/QEvent.html.h:56,
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
with Mesa header I will be able to have hardware
acceleration from qt?
That's how you run, not how you compile.
As far as I know, the Mesa libraries are binary compatible with any other
vendor's, so you can replace them at runtime with an implementation with
hardware acceleration.
--
Thiago
#include X11/Xutil.h
typedef Display *EGLNativeDisplayType;
typedef Pixmap EGLNativePixmapType;
typedef Window EGLNativeWindowType;
#endif /* MESA_EGL_NO_X11_HEADERS */
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
, can you also attach the output of:
gcc -xc++ -v - /dev/null 21 /dev/null
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
for the IO part in Qt?
No, Qt has no QPA for I/O.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing
have no objections
of it belonging to QtCore. It can be with an imagined future extension to the
API too.
That doesn't mean that it must move if you can't find a good example.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
On domingo, 24 de março de 2013 23.43.31, Mark wrote:
On Sun, Mar 24, 2013 at 11:01 PM, Thiago Macieira
thiago.macie...@intel.com wrote:
On domingo, 24 de março de 2013 22.47.03, Mark wrote:
That made me wonder, is there a way to change IO backends in Qt?
Because if i could swap
contact one of the cloud organisations. You'll also need to
explain why your idea is superior to the Open Build Service and similar tools
by Linux distributions.
PS: I don't think we've committed to entering the Qt Project as a mentoring
organisation in the GSoC.
--
Thiago Macieira - thiago.macieira
find we don't actually want to release them,
for whatever reason?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
belong in that library.
But please check with the Plasma devs whether they'll accept using private
API. Distro maintainers do not like when someone uses private API.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
On segunda-feira, 25 de março de 2013 17.05.12, Frederik Gladhorn wrote:
Mandag 25. mars 2013 08.30.45 skrev Thiago Macieira:
On segunda-feira, 25 de março de 2013 10.46.50, Sergio Ahumada wrote:
Next step is to get qt5.git updated and add qtquickcontrols, qtsensors,
qtserialport
On segunda-feira, 25 de março de 2013 22.46.36, Stephen Kelly wrote:
On Monday, February 25, 2013 17:12:02 Stephen Kelly wrote:
On Monday, February 25, 2013 08:07:48 Thiago Macieira wrote:
It was a matter of timing. Since GCC 4.8 is not released yet, I can't
make
the case for it being
up to the contributor and reviewers to decide
whether the change is too complex for stable.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
selectors would likely replace #ifdefs for
loading platform specific data in non-graphical situations.
Ok, then I agree the class belongs in QtCore.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
On segunda-feira, 25 de março de 2013 18.19.57, Alan Alpert wrote:
tl;dr - Okay, let's make it private for 5.1 (also works for
BlackBerry) and aim to polish it for 5.2.
Maintainer agrees. Go for it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source
On terça-feira, 26 de março de 2013 14.07.56, Sergio Ahumada wrote:
As far as I understand, the CI is all in Finland, so GMT +2.
In other words, the tests are effectively disabled.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
saying the new behaviour is correct,
then fine. But otherwise, it might be a compiler bug that gets fixed before the
release. We don't need the churn in our code.
2) even if it's a real issue, depending on how far away that compiler's
release is, it does not qualify as release-critical.
--
Thiago
think you should ask in the GStreamer MLs how to make your non-
standard options the default, so that each application and library doesn't
have to be modified to know about it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
-mentors-announce?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.
-
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed
On quinta-feira, 28 de março de 2013 13.35.22, Thomas Senyk wrote:
Question on the side: This is a commit for stable, right?
... It can be considered a build-bug-fix... or not?
Stable, it's a build fix.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source
not have DLLs in the lib
directory. I think Ossi has already pointed this out to the packaging team.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
.
For cross-compilations, the bootstrap library will be used by the host tools
in qttools (lupdate, lrelease).
Note that Linguist itself won't be built, so you must have another build of Qt
somewhere in order to create the translations in the first place.
--
Thiago Macieira - thiago.macieira
-capable as possible.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
that we'll bootstrap only moc, uic and rcc for regular
builds, so we won't need to install it. We'll need to install it for cross-
compilation builds.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
inside the Qt Project, I'd
say it's acceptable.
Gerrit Admins, please give John the rights as Maintainer. John, please create
a task against the bugtracker itself requesting your extra rights and point to
this thread as proof.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect
+mccarthy.aa...@gmail.com
git gp b5728f3 -b 714ff76a75c1262aee052a7f9a637528d2be8063~
git gp -b 4d1dc4b32bb4c4c25bde720299557a4ff3e344e2~ :/Re-shuffle
That git gp didn't do anything
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
for now.
(The only way to distinguish between them seems to be a check for
__apple_build_version__ .)
For details about the bug: see
http://llvm.org/bugs/show_bug.cgi?id670
*/
That bug is marked as fixed, but it does not show which version of Clang it was
included in.
--
Thiago
On quinta-feira, 11 de abril de 2013 20.40.17, Jan Kundrát wrote:
On Thursday, 11 April 2013 20:17:22 CEST, Thiago Macieira wrote:
Clang.
Its support for brace initialisation was incomplete. See the comment:
Thanks for pointing me in the right direction. I've seen that ML thread
before
On sexta-feira, 12 de abril de 2013 02.18.09, Olivier Goffart wrote:
On Thursday 11 April 2013 13:26:16 Thiago Macieira wrote:
On quinta-feira, 11 de abril de 2013 20.40.17, Jan Kundrát wrote:
On Thursday, 11 April 2013 20:17:22 CEST, Thiago Macieira wrote:
Clang.
Its support
can't find cmd.exe.
How is that possible? Do you have any theories how that can happen? Did the
build somehow erase cmd.exe during the build? Did PATH somehow get corrupted?
Windows 8 bug?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
that to unserialise as 9am because
I changed the system time zone. If I want a time relative to UTC then I
would use UTC, Offset or Time Zone.
Thiago, do you agree with John here?
Yes, I do.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source
out of the box already for Qt 5.1, since most of the needed parts
are already in place.
And +1 from me.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
, apparently. :)
:-)
But thanks for the service! It's greatly appreciated.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
it has happened in one of the main repositories.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing
On segunda-feira, 22 de abril de 2013 07.44.31, Qi Liang wrote:
Looks like the sync script(s) is running on your server(from codereview to
gitorious)?
No, this is no the codereview-gitorious sync. This is just updating the
repositories so the statistics script can run.
--
Thiago Macieira
.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http://lists.qt
for a policy change: do not rebase any branch in the main
repositories. And the reason is that a lot of people have those branches by
simple virtue of cloning the main qtbase. It's not possible to be sure
everyone knows the policies of each branch. Therefore, we define one only: no
rebase.
--
Thiago
On segunda-feira, 22 de abril de 2013 16.59.27, Oswald Buddenhagen wrote:
On Mon, Apr 22, 2013 at 07:48:07AM -0700, Thiago Macieira wrote:
On segunda-feira, 22 de abril de 2013 16.25.30, Oswald Buddenhagen wrote:
as far as i'm concerned, the push policy for all non-mainline branches
On segunda-feira, 22 de abril de 2013 17.44.41, Oswald Buddenhagen wrote:
On Mon, Apr 22, 2013 at 08:11:22AM -0700, Thiago Macieira wrote:
On segunda-feira, 22 de abril de 2013 16.59.27, Oswald Buddenhagen wrote:
And where is it documented for winrt?
why should it be?
Because
On terça-feira, 23 de abril de 2013 11.18.33, Oswald Buddenhagen wrote:
On Mon, Apr 22, 2013 at 10:19:05AM -0700, Thiago Macieira wrote:
Not necessarily. They may have simply found out about the branch due to
our
public posts and blogs, so they're just looking around. Hypothetically
(you can't load the two plugins at the same time).
I'm going to wait for other people to suggest solutions to this. Mine, for the
moment, is a hammer...
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
or
qdbusxml2cpp. Therefore, simply build it normally.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing
/doc.pri had:
adp_docs.depends += sub-qdoc3 # qdoc3
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing
to some people is less of a problem than
rebasing.
Besides, the fact that we made it worse in one aspect is not a justification
for accepting it elsewhere too.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
On terça-feira, 23 de abril de 2013 19.47.25, Olivier Goffart wrote:
On Tuesday 23 April 2013 08:48:41 Thiago Macieira wrote:
I'm going to wait for other people to suggest solutions to this. Mine, for
the moment, is a hammer...
My suggested solution:
In the header:
Put those functions
] was missing. Can you give me the link?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt
in QtQml, so that QtQuick1 retains compatibility with Qt 4.
No, we should just do what Olivier suggested. It solves the problem more
neatly.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
are the things people should be
aware of?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
the
recipe :)
I thought the rule was I want the cake and eat it too... :-)
Anyway, a pre-built image is much bigger to download than a set of Puppet
rules.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
.
With that, Ossi's patch is one step in the right direction and one step in the
wrong direction. We should not re-generate the headers if they are present,
but we should still do it if they aren't -- and that includes shadow builds.
So the patch needs a little fixing.
--
Thiago Macieira
On segunda-feira, 29 de abril de 2013 18.09.14, Oswald Buddenhagen wrote:
On Mon, Apr 29, 2013 at 07:44:18AM -0700, Thiago Macieira wrote:
On segunda-feira, 29 de abril de 2013 11.06.11, Oswald Buddenhagen wrote:
my current solution is entirely predictable: git builds always run
syncqt
With that in mind, I would suggest we change *both* coding styles to
optionally permit the braces, and strongly suggest it for more-complex
conditionals. In particular, it should suggest you leave the braces if you've
reduced the statements to one line.
--
Thiago Macieira - thiago
1101 - 1200 of 6027 matches
Mail list logo
