On segunda-feira, 15 de outubro de 2012 18.24.25, Oswald Buddenhagen wrote:
> hmm, yeah, we could do that, indeed. just write the spec names out to
> qconfig.cpp, like the paths, etc. this would allow us to remove some
> obscure code which even deviates between platforms.
> the problem being that
On Mon, Oct 15, 2012 at 06:03:46PM +0200, Stephen Kelly wrote:
> On Thursday, October 11, 2012 12:01:51 Oswald Buddenhagen wrote:
> > fwiw, the default mkspec links would need to go to lib, too, obviously.
>
> Or the default mkspec should be removed entirely.
>
> The default can be hardcoded in
On Thursday, October 11, 2012 12:01:51 Oswald Buddenhagen wrote:
> fwiw, the default mkspec links would need to go to lib, too, obviously.
Or the default mkspec should be removed entirely.
The default can be hardcoded in qmake, or am I missing something? It wouldn't
make sense to compile 3rd pa
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: T
On Wed, Oct 10, 2012 at 10:39:35AM -0700, Thiago Macieira wrote:
> 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
> > > technicall
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 t
On 21 Sep 2012, at 6:01 PM, ext Thiago Macieira wrote:
> pkgconfig/ - versioned .pc files
> qt5/ - arch-specific support files:
> bin/ or libexec/
>- executables not run by the user, like syncqt, lrelease,
> lupdate
> imports/
>
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 the whole party.
___
Development mailing
On segunda-feira, 24 de setembro de 2012 14.12.59, Knoll Lars wrote:
> You will need to adapt the pro file to some extent anyway when moving to Qt
> 5, since a lot of the magic on how to build and package modules has
> changed.
That's true for Qt modules, but not for third-party applications. Besi
On Sep 24, 2012, at 2:51 PM, Thiago Macieira
wrote:
> On segunda-feira, 24 de setembro de 2012 12.38.51, Knoll Lars wrote:
>>> The Qt 4 plugins live in the Qt4 prefix. Existing practice is that it's
>>> /usr/lib$SUFFIX/qt4/{plugins,imports}. So we don't clash with those.
>>>
>>> Technically spe
On segunda-feira, 24 de setembro de 2012 12.38.51, Knoll Lars wrote:
> > The Qt 4 plugins live in the Qt4 prefix. Existing practice is that it's
> > /usr/lib$SUFFIX/qt4/{plugins,imports}. So we don't clash with those.
> >
> > Technically speaking, since we're changing to qt5 anyway, we could change
On Sep 24, 2012, at 1:57 PM, Thiago Macieira
wrote:
> On segunda-feira, 24 de setembro de 2012 11.44.51, Knoll Lars wrote:
We already had a solution here (discussed that with Brisbane some months
ago). QML2 is the default, so it goes into imports/. For QML1 we have a
Quick1/ subf
On segunda-feira, 24 de setembro de 2012 11.44.51, Knoll Lars wrote:
> >> We already had a solution here (discussed that with Brisbane some months
> >> ago). QML2 is the default, so it goes into imports/. For QML1 we have a
> >> Quick1/ subfolder in imports.
> >
> > That's not acceptable. The QtQui
On Sep 24, 2012, at 12:43 PM, Thiago Macieira
wrote:
> 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 mot
On Monday, September 24, 2012 12:26:47 Thiago Macieira wrote:
> The FindQt5.cmake script coming
> from CMake itself or ECM should be there, though.
Not really. There is no FindQt5.cmake.
Even if there was, distributing it with Qt would be like hiding the treasure
map with the treasure. That's
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
> achieve? Just stating tha
On Mon, Sep 24, 2012 at 12:20 PM, Knoll Lars wrote:
>> imports/
>>- QtDeclarative imports
>> qml2/
>>- QML2 (including QtQuick2) arch-specific imports
>
> We already had a solution here (discussed that with Brisbane some months
> ago). Q
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)
> > pkgconfig/ -
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 Qt
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
achieve? Just stating that this is how the file hierarchy is supposed to be is
a bit weird. Is this a
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)
> pkgconfig/ - versioned .pc files
CMake files also go under lib/
Thanks,
--
Stephen Kelly | S
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 or Qt5Core/
>
> Oops, this won't work, as it breaks source-compatibility
On segunda-feira, 24 de setembro de 2012 07.08.58, Koehne Kai wrote:
> Note that didn't have any .qml files defining libraries in stock Qt 4.x: All
> the plugins are libraries here. Now for Qt 5 there are indeed some .qml
> files installed in the directory (I counted 42) ... I see that it would be
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On
> Behalf Of Thiago Macieira
> Sent: Friday, September 21, 2012 6:01 PM
> To: development@qt-project.org
> Subjec
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/
> - QtDeclarative imp
On Friday, September 21, 2012 06:01:28 PM Thiago Macieira wrote:
> The Qt 5 file hierarchy upon installation should be:
>
> bin/ - executables run by the user
> - unversioned applications, like assistant, linguist, qdbus,
> qdbusviewer
> - versi
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/
qt5/
QtCo
The Qt 5 file hierarchy upon installation should be:
bin/- executables run by the user
- unversioned applications, like assistant, linguist, qdbus,
qdbusviewer
- versioned applications, like qmake[35], qdoc5, qmlviewer5,
28 matches
Mail list logo
