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 libraries-only .dmg installs to system-wide locations and,
therefore, must follow your recommendation.
Does it do that already?
--
Thiago Macieira
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 (assistant-adp).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel
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 is non-standard.
CMake uses 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 dynamic linker only cares
about
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:
QtCore5 or QtCore-5 or QtCore.5
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 libqual or lib/arch/)
./ - versioned libraries (.a, .so, .la, .prl)
pkgconfig
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 thiago.macie...@intel.com
wrote:
The Qt 5 file hierarchy upon installation should be:
can you maybe come put up some motivations here and what you're trying
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 dirs.
Me too.
--
Thiago Macieira
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 thiago.macie...@intel.com
wrote:
This is the right mailing list :-)
The Qt Developers Conference Call for Papers is still open. If you haven't
yet, please
in
QStandardPaths. It already has the necessary logic.
Let's leave this out of 5.0, to simplify things.
Ok.
--
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
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) intel.com
Software Architect
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 - Intel Open
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.macieira (AT) intel.com
Software
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 better.
I've done
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 used to.
--
Thiago Macieira - thiago.macieira
.
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.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
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 Technology Center
Intel Sweden AB - Registration Number: 556189
develop new features
on top of the stable release (I used to do that in Qt 4), but should pay
attention to the development branch. Qt is big, but it's not hard to pay
attention to the areas one is developing on.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source
feature complete and does at least
what it intended to do.
--
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
. 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 - Intel Open Source Technology Center
Intel Sweden AB
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 disagree, you have to read my
arguments
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. Depending on the
mkspec was fragile.
--
Thiago Macieira - thiago.macieira
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
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista
, 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, 164 40 Kista, Stockholm, Sweden
signature.asc
Description
- srcBegin) * sizeof(T));
^
(void*)
We followed clang's recommendation to static_cast to void*. Clang can't
complain that we're doing exactly what it suggested we do.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source
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 we do.
Could you say more about
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 15, 164 40 Kista, Stockholm, Sweden
signature.asc
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
http://www.linkedin.com/groupInvitation
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
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
, apply the copyright change and the MinGW fix and merge it
back to the 4.8 branch.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
)
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-project.org
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
:
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 Center
signature.asc
Description: This is a digitally signed message part
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 point.
--
Thiago Macieira - thiago.macieira
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
Qt WebKit
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) intel.com
Software Architect - Intel Open
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.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software
, contact us at secur...@qt-project.org
so we can 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
is to assess issues being reported and determine whether or not
an urgent fix is required.
As for the CRIME vulnerability, we had it fixed before the details were made
public (by way of guessing what the issue was). The problem happened after the
fix, in getting it published.
--
Thiago Macieira
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 with most GCC
installations.
--
Thiago Macieira
On domingo, 7 de outubro de 2012 22.48.08, d3fault wrote:
On Sun, Oct 7, 2012 at 10:00 PM, Thiago Macieira
thiago.macie...@intel.com 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
?
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 Architect - Intel Open Source Technology Center
signature.asc
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 - Intel Open Source Technology Center
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 the
same
patch series means
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 part
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 is a digitally signed message part
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 Source Technology Center
signature.asc
Description: This is a digitally signed message part
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 Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source
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.
___
Development mailing list
Development@qt-project.org
http
: the name is inaccurate. High-ppi (as in pixel) would be better,
since point geometry does not change.
Android calls them device-dependent pixels (ddp).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
to that database. Please consult your unixODBC documentation.
--
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
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 - thiago.macieira (AT) intel.com
: Knoll Lars lars.kn...@digia.com
Para: Thiago Macieira thiago.macie...@intel.com
On Oct 4, 2012, at 3:18 PM, Thiago Macieira thiago.macie...@intel.com 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
, 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: This is a digitally signed message part.
___
Development
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 qconfig.pri, which spoils
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 message part.
___
Development mailing list
Development@qt
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 Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology
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 files
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 Open Source Technology Center
signature.asc
Description: This is a digitally signed
. 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: This is a digitally signed message part
of
supporting the users will fall on us, not on them. Who do you think staffs #qt
on Freenode?
The other thing is, we still need to rename the libraries. Otherwise, we can't
install both sets of *.so files to /usr/lib. If we do that, we've solved the
majority of the problem anyway.
--
Thiago
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
Description
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: This is a digitally signed message part.
___
Development
, 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.
___
Development mailing list
Development@qt-project.org
http
device developers, the packagers and a
handful of KDE developers.
The vast majority will get it pre-built.
Considering all the changes I am proposing do NOT harm any of the people that
build from sources, why should we NOT do them? Other than that it requires
work on your part, Ossi.
--
Thiago
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 positively do *not* want to use
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 Windows too, for example.
only because
.
--
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
.
--
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 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.
If we had a generic build tool
.
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 Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
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 here
, all need to keep a pointer to the original object, which
QObjectPrivate already carries.
--
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 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 Git repositories:
qtbase
qtwebkit
. 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 digitally signed message part
far. Another option would be to call the directory 'modules'.
We could call it simply qml, that's fine too.
modules is way, way too generic. Or did you mean qmlmodules ?
PS: I tried modifying QLibraryInfo to add the new path but I somehow broke
qmake for some unknown reason...
--
Thiago
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.
___
Development mailing list
Development@qt
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 apply to Cascades code using QML 2, not just Qt Quick 2
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.
___
Development mailing list
Development@qt-project.org
http
changes already ready and
uploaded to Gerrit.
Let's go for qml then.
Will do. I need help from Ossi to figure out how I broke qmake, because it's
not evident.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
with no autoproxy. We
could cache the host's IP addresses and discard the cache if they have changed
too. Since we'll do that only once every 10 minutes, the overhead will be
minimal.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
second freeze, since both methods fail if
you are on a network with no autoproxy.
We need to be calling WinHttpGetProxyForUrl or
WinHttpDetectAutoProxyConfigUrl in a thread, like we do for name
resolutions.
Sounds good. I'd recommend reusing the hostinfo thread pool for that too.
--
Thiago Macieira
to see if it works. I'll get to it
later this week.
--
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
defaults to $prefix/lib/qt5/qml on all
systems.
--
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
...
from a quick survey i don't have the impression that many people grasp that
this thread is very much relevant for them.]
I had stopped reading the other thread, but this now interests me so its
helpful to do so. Thanks!
On Thu, Oct 11, 2012 at 04:11:10PM -0700, Thiago Macieira wrote
reactive and let's just fix this problem once and for
all.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
inclined to do
former option. That means we're going to require the second, moving the burden
to the plugin developers.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
besides
Current in Mac frameworks.
The only thing that would be solved is how Linux distributors can install
multiple (major) versions of Qt simultaneously.
Right.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
On sexta-feira, 19 de outubro de 2012 01.03.29, André Pönitz wrote:
On Thu, Oct 18, 2012 at 08:30:03AM -0700, Thiago Macieira wrote:
lconvert- lconvert5
lrelease- lrelease5
lupdate - lupdate5
Sorry, I don't get the joke.
Because it was no joke. It's serious
On quinta-feira, 18 de outubro de 2012 08.30.03, Thiago Macieira wrote:
xmlpatterns - xmlpatterns5
xmlpatternsvalidator - xmlpatternsvalidator5
I've changed my mind on those two and dropped the patches that dealt with
them.
Those two are end-user applications and retain full
.
The problem does exist, but so does the solution and it's already in place.
Therefore we don't need to do anything.
That's why designer is not getting renamed. The Qt 5 version simply replaces
the Qt 4 one and, provided the plugins are upgraded too, no functionality is
lost.
--
Thiago Macieira
On sexta-feira, 19 de outubro de 2012 01.57.16, André Pönitz wrote:
On Thu, Oct 18, 2012 at 04:10:16PM -0700, Thiago Macieira wrote:
On sexta-feira, 19 de outubro de 2012 01.03.29, André Pönitz wrote:
On Thu, Oct 18, 2012 at 08:30:03AM -0700, Thiago Macieira wrote:
lconvert
On sexta-feira, 19 de outubro de 2012 10.17.39, Lincoln Ramsay wrote:
On 19/10/12 01:30, Thiago Macieira wrote:
After all of my patches are integrated, here are the changes that will
happen:
- bin:
The following tools have been renamed:
So... You just don't care about the calls from
will never be for Qt 5. Whether it's for Qt 3 or for Qt 4,
it's undefined. That mess is already present and we can't fix it anymore.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed
everything more obscure for the common case.
Agreed.
So on both Mac and Windows, Qt libraries are always installed on their own
prefixes. There's no global install. That means there's no conflict of names
either, in either libraries or tooling.
--
Thiago Macieira - thiago.macieira (AT) intel.com
On sexta-feira, 19 de outubro de 2012 11.54.36, Joerg Bornemann wrote:
On 18/10/2012 19:09, Thiago Macieira wrote:
Let me be very clear: the distributions aren't fixing the distribution's
problem. They'd be fixing *ours*.
Putting every binary into one directory excludes installing
component sets ...
Ok, I haven't (un)done the change yet, so I'm holding back on it now.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
mind either way. I've done it the way I did because:
[qml1plugindump had already been renamed]
and I simply followed the logic that was already there.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
, to %{CurrentProject:QT_INSTALL_LIBEXEC}/lrelease.
In any case, I think that lrelease and lupdate being run directly is the wrong
solution. They should be run by the Makefile, by having a correct .prf that
gets processed and adds the correct rules.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software
that affect the existing
setups? How does that tutorials, etc.?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
701 - 800 of 6027 matches
Mail list logo
