On Friday 27 February 2015 22:55:18 Alex Merry wrote:
On Friday 27 February 2015 13:29:59 Jeremy Whiting wrote:
On Fri, Feb 27, 2015 at 4:05 AM, Alex Merry alex.me...@kde.org wrote:
4. Use the PATH_VARS to ecm_configure_package_config_file().
ecm_configure_package_config_file()
Alex,
On Fri, Feb 27, 2015 at 4:05 AM, Alex Merry alex.me...@kde.org wrote:
On Wednesday 25 February 2015 19:10:08 Jeremy Whiting wrote:
One issue I found however is that some frameworks (maybe all?) have a
KF5FooConfig.cmake.in with ${PACKAGE_PREFIX_PATH}/@KDE_INSTALL_DATADIR@
in
them
On Wednesday 25 February 2015 19:10:08 Jeremy Whiting wrote:
One issue I found however is that some frameworks (maybe all?) have a
KF5FooConfig.cmake.in with ${PACKAGE_PREFIX_PATH}/@KDE_INSTALL_DATADIR@ in
them to specify where to find the data files. On my OS X install that was
getting filled
On Friday 27 February 2015 13:29:59 Jeremy Whiting wrote:
3. Use absolute paths for KDE_INSTALL_DATADIR everywhere and remove
${PACKAGE_PREFIX_PATH} completely.
There is KDE_INSTALL_FULL_DATADIR, which is absolute. However, that
removes
the relocatability of the package that
On Thu, Feb 26, 2015 at 3:10 AM, Jeremy Whiting jpwhit...@kde.org wrote:
Hello core developers,
In the past few months some effort has been made to get the frameworks (kf5)
to work on other platforms such as OS X and Windows. Together with Marko I
focused primarily on OS X since there was
