On segunda-feira, 11 de fevereiro de 2013 12.21.48, Sebastian Kügler wrote: > On Monday, February 11, 2013 10:49:08 Sebastian Kügler wrote: > > On Sunday, February 10, 2013 14:33:49 Thiago Macieira wrote: > > > On domingo, 10 de fevereiro de 2013 21.22.05, Sebastian Kügler wrote: > > > > Apparently not. I've looked at where the example imports from the Qt > > > > codebase install these things, and that is indeed $PREFIX/qml, not > > > > inside > > > > the plugin directory. This location is also where these imports are > > > > being > > > > found automatically, i.e. without specifying additional import pathes > > > > (which we have to do for Plasma in kdelibs 4). > > > > > > Technically, it's $ARCHDATADIR/qml. The Qt build makes > > > ARCHDATADIR=PREFIX > > > by default. > > > > > > > > > > > > But everyone installing Qt to PREFIX=/usr should set it > > > ARCHDATADIR=$LIBDIR/qt5. > > > > So that means that qtquick2 imports should go there, and that we should > > advise people in our build instructions to build with > > --archdatadir=$LIBDIR/qt5?
If we advise --prefix=/usr, we should advise --archdatadir too, otherwise Qt's
build starts installing crap in /usr like /usr/plugins, /usr/mkspecs, /usr/qml
and /usr/imports. All four are controlled by the archdatadir option.
> > Which would bring me to my next question: How do I find out the ARCHDATA
> > dir from a cmake script then? (Yes, noob question.)
I don't know. The info is hardcoded in qmake. Maybe cmake should keep a
similar list of paths?
A quick check shows that the cmake generated files are completely wrong already
for when someone plays with the dir options. They don't take --bindir into
account, for example.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect - Intel Open Source Technology Center
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
