On Monday, February 11, 2013 17:03:55 Stephen Kelly wrote: > 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? > > > > Which would bring me to my next question: How do I find out the ARCHDATA > > dir from a cmake script then? (Yes, noob question.) > > It is not currently set by the cmake scripts because I did not know why > anyone would want it. > > What do you need it for, exactly?
To find out where Qt will look for QtQuick2 imports (that's $ARCHDATADIR/qml, defaulting to $PREFIX/qml, which leads to /usr/qml). I'd like to be able to install Plasma QtQuick2 imports into a path where they'll actually be found, that's the QML_INSTALL_DIR which the patch from this thread adds. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
