Hi Luigi, > I'm not sure about this. KDocTools relies on QStandardPaths to find resources > in common paths; our Windows developers hacked QStandardPaths. > > You can take a look in the discussion of the RR I mentioned many times: > https://git.reviewboard.kde.org/r/115752/ yep, I know this one and tried get it to work in a similar fashion, but to no avail. :(
> which points to the discussion in > https://git.reviewboard.kde.org/r/115210/ This is new to me, but I figure the SHARE_INSTALL_PREFIX is specific to a Windows install, right? > Again, the directory set which should be considered by QStandardPaths requires > input from MacOSX developers. I suspect that KDocTools is the first place > where this issue is visible, but it will popup elsewhere. I saw only now that Harald has some new solution atm [1] which includes custom settings for: - DocBookXML_CURRENTDTD_DIR - DocBookXSL_DIR as well as a patch for KF5DocToolsConfig.cmake.in but I haven’t tried anything of it yet, because I’ve got no clue as to how much of it is specific for a Homebrew setup (especially the DocBookX* vars). But the setting of KDOCTOOLS_CUSTOMIZATION_DIR looks promising: --- diff --git a/KF5DocToolsConfig.cmake.in b/KF5DocToolsConfig.cmake.in ... -set(KDOCTOOLS_DATA_INSTALL_DIR "${PACKAGE_PREFIX_DIR}/@DATA_INSTALL_DIR@") +if (APPLE) + set(KDOCTOOLS_DATA_INSTALL_DIR "@DATA_INSTALL_DIR@") +else() + set(KDOCTOOLS_DATA_INSTALL_DIR "${PACKAGE_PREFIX_DIR}/@DATA_INSTALL_DIR@") +endif() set(KDOCTOOLS_CUSTOMIZATION_DIR "${KDOCTOOLS_DATA_INSTALL_DIR}/kdoctools5/customization”) --- Will deal with that next week. :) Greets, Marko [1] https://github.com/haraldF/homebrew-kf5/blob/master/kf5-kdoctools.rb _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
