[Differential] [Commented On] D2854: New: ECMAddQCH, for generating qch & doxygen tag files

[shumski (Hrvoje Senjan)]

shumski added inline comments.

INLINE COMMENTS

> kossebau wrote in KDEInstallDirs.cmake:534
> But that is the same for the current QTPLUGINDIR, QTQUICKIMPORTSDIR, & QMLDIR, no? They also only get set to the Qt system paths if KDE_INSTALL_USE_QT_SYS_PATHS=ON, otherwise get set to something based on general LIBDIR.
> (I would have liked to put the setting of QTQCHDIR next to these other ones, but at that time DATAROOTDIR is not yet defined, so had to create a separate if-else)
> And especially if installing multiple versions of the same dir (e.g. for different projects or as developer of the lib), it will be needed to optionally not install into the Qt system path, but point all the tools via ENV variables or other ways to the matching plugins or documentation.

Right. But if you install a framework to same prefix as Qt, you get free recognition of plugins, qml imports, etc... This is valid for both /usr and custom prefix installs.
I guess what i want to say is that there is IMHO no reason this should also not work for QCH docs.

REVISION DETAIL
  https://phabricator.kde.org/D2854

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: kossebau, staniek, #frameworks
Cc: shumski, kfunk, staniek, winterz, ochurlaud, #kdevelop
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20161130/abe42819/attachment.html>