On sexta-feira, 21 de setembro de 2012 16.47.11, Thiago Macieira wrote:
> Include the major version number (5) in all library base names, like on
> Windows, on all platforms. On Windows we already have QtCore5.dll and
> QtV85.dll, so I recommend having libQtCore5.so.5. For Mac, I'
On sexta-feira, 21 de setembro de 2012 17.24.16, Thiago Macieira wrote:
> Good examples are: qtcreator, assistant, linguist, qmlviewer, qmlscene,
> qmlplugindump, qmlprofiler, xmlpatterns, qdbus, qdbusviewer, qglinfo
Actually, the qml ones are not good examples since they can load p
are technically-
speaking arch-independent.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description: This
On sexta-feira, 21 de setembro de 2012 17.33.01, Stephen Kelly wrote:
> On Friday, September 21, 2012 16:47:11 Thiago Macieira wrote:
> > Rationale:
> > --
> >
> > This is a rewriting of the book in how to name a library.
>
> It seems like it might be somet
On sexta-feira, 21 de setembro de 2012 18.01.28, Thiago Macieira wrote:
> include/- versioned include dirs:
> QtCore5 or QtCore-5 or QtCore.5 or Qt5Core/
Oops, this won't work, as it breaks source-compatibility completely.
It needs to be:
include/
at now. But if you do have a good solution with
DCAS, we could consider it later. We just need to double the size of QMutex
now.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
K
>
> Solutions that map to C++11 concepts, with single-sized atomics, would
> probably be best. Like what is there now.
Better, yes, but we're not constrained by C++11 constraints. We can write
assembly.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel O
t's coming, what's already present, how to use it with
or on other technology (devices, architectures, other libraries, frameworks,
etc.)
Be creative and submit your proposal at
https://qtconference.kdab.com/node/12
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect
On sexta-feira, 21 de setembro de 2012 18.01.28, Thiago Macieira wrote:
> qt5/ - arch-specific support files:
> bin/ or libexec/
> - executables not run by the user, like syncqt, lrelease,
> lupdate imports/
>
er touches. Therefore, your problem is not related to
syncqt.
More than likely, it's just a down-to-earth bug caused by referring to a file
that doesn't exist, on your configuration.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technolo
no for the sake of laziness. That's not what's happening
> here though.
That's exactly what's happening. I'm bringing the proposal to the table and
you're starting to resist it.
> Currently, it's not distros proposing this.
Yes it is. Did you think I came up
le
> implementation of it. My mails here are an attempt to understand why your
> proposal is the only/best way.
I think the proposal spoke for itself. Goal: co-installation of all files.
The current Qt Project's position is that we don't support that. We require Qt
to be installed
g that QtQuick2 not be released
with Qt 5.0. :-)
The searched directory structure needs to be fixed by the time of the first
release of QtQuick2. I am suggesting we leave QtQuick1 alone with its broken
scheme -- even in spite of the fact that EVERYONE that uses Qt Quick, uses
version 1.
--
Thiago Maci
lation
problem differently.
Let me ask you a question, though: suppose someone installs Qt 5 globally as
frameworks (/System/Frameworks/QtCore.framework), then updates Qt 4.8. Which
is the default symlink target?
And how does one select, at compile time, whether to compile & link to Qt 4 or
to Q
rs for the different include
> & link paths (e.g. qmake does that for you).
>
> When compiling for different Mac OS SDKs you'd set a different sysroot.
Ah, I see! That explains a lot.
Final question: do our Mac binaries set up like the above? Unlike the SDK
builds for Mac, the l
les and saving them
back, or don't operate at all on files. In fact, Designer could be in this
category too, if we don't care about Qt 3 compatibility anymore.
When we had an incompatible change for Assistant, we released the previous
version as a separate tool for those who needed it (as
On segunda-feira, 24 de setembro de 2012 11.30.47, Stephen Kelly wrote:
> On Sunday, September 23, 2012 18:46:21 Thiago Macieira wrote:
> > Probably. But we've been saying for 7 years that pkg-config is the
> > official
> > way of finding Qt. CMake's use of qmake
On segunda-feira, 24 de setembro de 2012 11.33.40, Stephen Kelly wrote:
> On Friday, September 21, 2012 16:47:11 Thiago Macieira wrote:
> > In particular, note that it's also possible to load two different major
> > versions of a given library into memory, as the dynam
On segunda-feira, 24 de setembro de 2012 11.34.45, Stephen Kelly wrote:
> On Friday, September 21, 2012 18:20:33 Thiago Macieira wrote:
> > On sexta-feira, 21 de setembro de 2012 18.01.28, Thiago Macieira wrote:
> > > include/- versioned include dirs:
> > >
On segunda-feira, 24 de setembro de 2012 11.35.26, Stephen Kelly wrote:
> On Friday, September 21, 2012 18:01:28 Thiago Macieira wrote:
> > lib/- arch-specific files (also lib or lib//)
> >
> > ./ - versioned libraries (.a, .so, .la, .prl)
On segunda-feira, 24 de setembro de 2012 10.20.12, Knoll Lars wrote:
> Hi Thiago,
>
> On Sep 21, 2012, at 6:01 PM, Thiago Macieira
wrote:
> > The Qt 5 file hierarchy upon installation should be:
> can you maybe come put up some motivations here and what you're trying to
dir. I make the same
> > recommendation: move it into lib/qt5 by default.
>
> I'm personally fine with both. It also simplifies configuration (removes two
> options that we'd need to support), but I'd like to hear if someone sees
> any problems with moving these two
On segunda-feira, 24 de setembro de 2012 13.33.35, a.gra...@gmail.com wrote:
> Hi Thiago,
>
> On 21 September 2012 21:41, Thiago Macieira
wrote:
> > This is the right mailing list :-)
> >
> > The Qt Developers Conference Call for Papers is still open. If you haven
ting from Qt Quick 1 to
Qt Quick 2.
> > True, we could add the platform-independent search paths in a later
> > release. Also note that the search functionality is is implemented in
> > QStandardPaths. It already has the necessary logic.
>
> Let's leave this out of 5.0, to simplify
e the include dir back to QtDeclarative/
3) rename the qmake module file back to qt_declarative.pri (so we get
QT += declarative back)
In addition, my hierarchy proposal also proposes splitting the import dirs,
but let's continue that discussion there.
--
Thiago Macieira - thiago.macieira (AT)
Giving it a few days until people chime in.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description
On segunda-feira, 24 de setembro de 2012 15.38.46, Thomas McGuire wrote:
> Well, in Qt5, QtQuick has been split up into libQtQml and libQtQuick, so it
> can't just be renamed back to libQtDeclarative.
Why not?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect -
t; The even better way would be to make this transparent when building. In
> principle, the build system should know whether this is a QML 1 or QML 2
> plugin, and could adapt the path accordingly.
Could be. But it sounds like a bit too much magic for me.
--
Thiago Macieira - thiago.maciei
On quinta-feira, 7 de junho de 2012 09.43.40, Thiago Macieira wrote:
> I've just had an idea to make this optimisation slightly more generic. I
> need to experiment a little to see if it's worth it. If it is, I'll send a
> replacement and let reviewers judge which one is
On terça-feira, 25 de setembro de 2012 12.20.08, Fathi Boudra wrote:
> As far as I'm concerned, I welcome Thiago's patch.
An option has been added to configure: -no-strip or -strip=no
The default is still to strip release builds.
--
Thiago Macieira - thiago.macieira (AT) intel.c
Qt 5)
2) never will we fix all bugs, it's just not practically possible given the
manpower and the number of submitters. It's only got worse because we no
longer have a dedicated support team for all of Qt, we've lost people very
recently and there's more attention than there u
s. Adding this new virtual within the same
patch series means a new, public symbol, which could get used in applications.
If there's a sensible implementation that does not require overriding the
virtual, then we should use it. Otherwise, I'd say go for it.
--
Thiago Macieira - thiago.maci
appreciated. Perhaps, I can help a little bit if I get some pointer.
Can you do what it says?
Could not determine the target architecture!
Turn on verbose messaging (-v) to see the final report.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technolo
seen it
>(It could(!) be caused by violating the mkspec-naming-schema, but not
> very likely)
It actually is :-/
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
y put into the development branch,
> but it is not yet in the stable or release due to its current quality.
> However, a new developer should not reinvent that due to a mistake.
I don't think it's a problem either. This developer may develop new features
on top of the stable rel
h bigger
and has a larger impact in the stabilisation process.
> > The intention is that new developers who
> > clone Qt repositories for the first time are presented with a stable
> > codebase they can begin working on, bugfixing and even developing new
> > features for.
> A
that they do what the
developers intended for it to do. Once it's ready for publication to a larger
audience, this audience can and will find new things to use the feature for,
probably resulting in bugs being found.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - In
On sexta-feira, 28 de setembro de 2012 13.07.16, Stephen Kelly wrote:
> On Friday, September 21, 2012 16:47:11 Thiago Macieira wrote:
> > This is long, so I'll give you my recommendation first. If you agree with
> > me, you don't have to read the rest. If you disa
27;s linux-g++-. I reserve the right to unintentionally break any
mkspec not following that rule. Therefore, please rename them all at the
earliest opportunity.
That said, one of Ossi's recent changes was to have the compiler name in a
different variable, so we avoid this problem completely.
On sexta-feira, 28 de setembro de 2012 15.14.32, Konstantin Tokarev wrote:
> 23.09.2012, 18:06, "Thiago Macieira" :
> > Because there is only one prefix for distributions: /usr. They do not like
> > installing elsewhere.
>
> E.g. Mandriva istalls Qt 4 into /usr/lib
hose problems in the future
but 3) I don't know if Ossi's solution is enough, so renaming is still
recommended
> (by the way: the change is more then just renaming folders)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
elines, which do not include nested namespaces. In fact, syncqt barely
supports namespaces at all.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 1
eof(T));
^
qvector.h:459:30: note: explicitly cast the pointer to silence
this warning
::memcpy(dst, srcBegin, (srcEnd - srcBegin) * sizeof(T));
^
(void*)
We followed clang's recommendation to static_cast to
ethod=entry&id 59
> 90
>
> I can't find an answer in the Qt docs nor can i lookup the tracker id
> since it just doesn't exist anymore.
QCollator will be public in Qt 5.1.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technolo
On segunda-feira, 1 de outubro de 2012 09.37.06, Stephen Kelly wrote:
> On Sunday, September 30, 2012 17:13:14 Thiago Macieira wrote:
> > We followed clang's recommendation to static_cast to void*. Clang can't
> > complain that we're doing exactly what it suggested
;t managed it in a while).
I mostly use it to re-post interesting information from the Qt Planet.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan
On segunda-feira, 1 de outubro de 2012 05.55.53, Thiago Macieira wrote:
> On segunda-feira, 1 de outubro de 2012 13.50.18, Stephen Kelly wrote:
> > http://twitter.com/qtproject
> > http://www.youtube.com/user/QtStudios
> > http://www.facebook.com/qtbynokia
> &
nce the license headers have already
> been updated in the 4.8 branch, and it (hopefully) already contains
> the aforementioned MinGW fix, I would recommend to release 4.8.4 as
> soon as possible, instead of 4.8.3-1...
--
Thiago Macieira - thiago.macieira (AT) intel.com
Soft
x
> 2. Include only the copyright changes and fix MinGW in the next patch
> release
> 3. Call it 4.8.4 and accept that it can not be fetched from the
> repository
4. Call it 4.8.4, apply the copyright change and the MinGW fix and merge it
back to the 4.8 branch.
--
Thiago Macieira -
dio XE)
IBM Purify
--
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-proje
On quinta-feira, 4 de outubro de 2012 13.38.46, Stephen Kelly wrote:
> git merge v4.8.4
Better yet:
git merge -s ours v4.8.4
No conflicts.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This i
the permission
to send merge commits to Gerrit. Only people in this group can:
https://codereview.qt-project.org/#admin,group,14
Ask one of them to do it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology
included in the 5.0 release can be released later, at a separate
time, when their maintainers decide the code is mature enough.
[*] Lars: that's the content of qtsdk.git today, the result of discussions in
the past weeks, so we took that as your implicit approval and starting po
On quinta-feira, 4 de outubro de 2012 06.14.05, Thiago Macieira wrote:
> All the modules in the Qt Essentials package have approval by the Chief
> Maintainer[*] to be released as Qt 5.0:
> all modules in the qtbase repository
> Qt Quick 1 and Qt Quick 2
>
versions again to commercial customers, so we added 4.3.6, 4.2.4,
4.1.3, and then the "n" releases of the other patch releases (4.1.1n), etc.
> The "-1" notation is typically used for package revision in linux
> distributions.
--
Thiago Macieira - thiago.macieira (AT) int
ate to the main branch (e.g. 4.8) to update the
> QT_VERSION to the next release (e.g. 4.8.5)
I agree with this workflow. It matches what I said last week about the Qt 5
security releases for past versions, but I hadn't included the security
releases for the *current* version.
--
Thia
on web
pages, WebKit should do the validation. If it doesn't do that, it's a security
issue.
> Small bug or something else?
If you find that it's a security issue, contact us at secur...@qt-project.org
so we can deal with it.
--
Thiago Macieira - t
was). The problem happened after the
fix, in getting it published.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
x27;re going to invoke ld directly, you need to ensure the
> appropriate flags are set so it includes the C++ runtime.
>
> Apparently the library you want is libsupc++.a and it'll be somewhere in
> your toolchain/sysroot directory.
libsupc++.a is included in libstdc++.so, which comes
On domingo, 7 de outubro de 2012 22.48.08, d3fault wrote:
> On Sun, Oct 7, 2012 at 10:00 PM, Thiago Macieira
>
> wrote:
> > For obvious reasons, the security list is not public and is not open for
> > subscription from other people. If you feel you have a reason to be in the
> Is this by design?
No.
Please try erasing include and re-generating it. syncqt & qmake don't always
recreate them properly if you don't run them in the right order (beats me what
the right order is).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Archit
On segunda-feira, 8 de outubro de 2012 02.36.09, d3fault wrote:
> On Mon, Oct 8, 2012 at 12:39 AM, Thiago Macieira
>
> wrote:
> > Full disclosure *after* we've analysed the bug and delivered a fix, if
> > necessary.
>
> Well I think we should change the po
you wanted, or use MNG or
animated GIF. I don't know what our support for APNG is at the moment.
[1] please do not capitalise qtbase: it's the name of the Git repository, not
the name of a module or product.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect -
On terça-feira, 9 de outubro de 2012 12.31.23, Marc Mutz wrote:
> On Wednesday September 26 2012, Thiago Macieira wrote:
> > But note that there's one stricter requirement: the forwards compatibility
> > that applies within a patch series. Adding this new virtual within th
th. What methods from
QAbstractSocket do you need which are also common (same signature) between
that and QLocalSocket?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message p
you write the documentation, please be clear that this is an "Apple's
idea of point", not what everyone else currently uses (1/72 of an inch).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This
ed for KDE in 2003 (KStreamSocket), which took a generic string as
address and worked with both TCP and Unix sockets. Even if we decide that's a
good design, we can't implement it now in Qt 5.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Sourc
calling the new symbol, whether it exists or not. That means
the change was not source-compatible.
> Now, what's the forward-compatibility policy on the 4.8 branch?
Any program compiled with Qt 4.8.x will run with Qt 4.8.y, whatever x and y
are (modulo bugs, of course).
--
Thiago Macieir
nd eventfd only supports a simple integer increment or semaphore
posting (its ideal usecase is waking up threads).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_
x27;s still one inch across, but filled with more pixels.
>
> (assuming that the screens have exactly 72 and 144 pixels per inch,
> respectively)
>
> Conclusion: the name is inaccurate. High-ppi (as in pixel) would be better,
> since point geometry does not change.
Android calls t
loping software with Qt to the inter...@qt-project.org
mailing list.
2) it looks like the ODBC driver was found and your ODBC library simply could
not connect to that database. Please consult your unixODBC documentation.
--
Thiago Macieira - thiago.macieira (AT) in
ocket on the loopbar device, while e.g. Unix domain sockets can be
> created such that only processes of the same user can attempt connections.
True. What's more, you can use SO_PEERCRED and file-descriptor passing on Unix
sockets, but you can't on TCP sockets.
--
Thiago Macieira - thiag
From: Knoll Lars
Para: Thiago Macieira
On Oct 4, 2012, at 3:18 PM, Thiago Macieira wrote:
> On quinta-feira, 4 de outubro de 2012 06.14.05, Thiago Macieira wrote:
>> All the modules in the Qt Essentials package have approval by the Chief
>> Maintainer[*] to be released as Qt 5.0:
&
the patch before the disclosure, then we can't add it to the main tree or to
Gerrit either...
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: Th
On quarta-feira, 10 de outubro de 2012 18.04.18, Oswald Buddenhagen wrote:
> On Fri, Sep 21, 2012 at 06:01:28PM +0200, Thiago Macieira wrote:
> > As for mkspecs, I believe they should be in share, since they are
> > technically- speaking arch-independent.
>
> except for qcon
uld be addressed by
> those concerned with it.
It belongs in Qt and people have already agreed to it. We need to fix it in Qt.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed mes
ect.org/33266
> though they might also be interpreted as good reasons to have a 4.9 release
Exceptions given on a case-by-case basis.
The above is much more than adding a symbol as an artifact of a change. It's
whole new API and features. It should not go into 4.8.
--
Thiago Maciei
On segunda-feira, 24 de setembro de 2012 15.07.06, Thiago Macieira wrote:
> import $prefix/imports $prefix/imports
> $prefix/imports
> QtQuick 1.[01] QtQuick 1.[01] QtQuick 2.0
Hmm... Qt Quick 1 in Qt 5 supports installing its f
current. Maybe I will
> have better luck this time. :)
Just ask on IRC how to get back. But you don't need to "get back", it's fine to
run later versions of code. I do that all the time.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel
ot; because it's based on the QML 2 engine. That
means it would apply to Cascades code using QML 2, not just Qt Quick 2.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: T
If we do that, we've solved the
majority of the problem anyway.
--
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, 11 de outubro de 2012 12.01.51, Oswald Buddenhagen wrote:
> fwiw, the default mkspec links would need to go to lib, too, obviously.
True.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Descript
ze in 4.8.
We could name it 4.9.0 if we wanted to, but it would probably open a bigger
can of worms.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description:
rsion the libraries. We already do that on Windows too, for
example.
--
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 your part, Ossi.
--
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.o
On quinta-feira, 11 de outubro de 2012 21.16.56, Oswald Buddenhagen wrote:
> On Thu, Oct 11, 2012 at 11:56:44AM -0700, Thiago Macieira wrote:
> > Considering all the changes I am proposing do NOT harm any of the
> > people that build from sources,
>
> they *do* harm. i positi
On quinta-feira, 11 de outubro de 2012 21.09.24, Oswald Buddenhagen wrote:
> On Thu, Oct 11, 2012 at 11:54:28AM -0700, Thiago Macieira wrote:
> > I'd simply version the libraries.
>
> yes. me too. i wouldn't rename them, though. ;)
>
> > We already do that on W
ebkit-gtk or mozjs.
--
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.o
he development mailing list, not interest.
--
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 sexta-feira, 12 de outubro de 2012 10.01.03, Lincoln Ramsay wrote:
> On 12/10/12 09:18, Thiago Macieira wrote:
> > The only tools that need renaming are the tools that are run by users but
> > are tied to a specific library version. That's basically qmake.
> >
>
as this change could also be done in 5.1, I'd only propose to ban
> _new_ _q_slots() from being added.
If we agree on how to use them, yes. The only solution we *can* use is
functors, which are hard to use.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Op
qtgraphicseffects
qttranslations
and their dependencies:
qtjsbackend
qtsvg
qtscript
qtxmlpatterns
On quarta-feira, 10 de outubro de 2012 07.33.24, Thiago Macieira wrote:
> Lars apparently sent to me directly and I forgot to ask him to resend h
On sexta-feira, 12 de outubro de 2012 16.01.58, Erik van Pienbroek wrote:
> Thiago Macieira schreef op do 11-10-2012 om 16:11 [-0700]:
> > On quinta-feira, 11 de outubro de 2012 21.16.56, Oswald Buddenhagen wrote:
> > > oh, i'm not worried about the work. saying no is
> > functors, which are hard to use.
>
> Not harder to use than Q_PRIVATE_SLOT, IMO. More annoying, yes, because of
> boilerplate code (of which Q_PRIVATE_SLOT also has some, mind). Real-life
> example:
[snip]
I'd rather explore options like what Olivier is proposing. The f
On sexta-feira, 12 de outubro de 2012 18.51.28, Sergio Ahumada wrote:
> Hi,
>
> On 10/12/2012 08:29 AM, Thiago Macieira wrote:
> > Since no one has spoken up, that means we have the official Qt 5.0 release
> > list.>
> > It will include the following Gi
ion. Is
> there a logical explanation for that? (I was expecting the opposite)
Check if that release build has debugging symbols enabled.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digita
ed modifying QLibraryInfo to add the new path but I somehow broke
qmake for some unknown 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.
___
erminated asynchronously, or if the handlers aren't run, all
bets are lost.
--
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 segunda-feira, 15 de outubro de 2012 07.54.42, Thiago Macieira wrote:
> On segunda-feira, 15 de outubro de 2012 07.55.56, Knoll Lars wrote:
> > > Note that I called it "qml2" because it's based on the QML 2 engine.
> > > That
> > > means it would ap
t's /usr/lib64/qt4/mkspecs on the
Fedora packages.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
D
1601 - 1700 of 6728 matches
Mail list logo