On Thursday 15 December 2011, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > On Wednesday 14 December 2011, Stephen Kelly wrote:
> >> David Faure wrote:
> >> > On Tuesday 13 December 2011 21:23:52 Alexander Neundorf wrote:
> >> >> Somewhat similar, do we still have the plan to provide like a
On Wednesday 14 December 2011, Stephen Kelly wrote:
> David Faure wrote:
> > On Tuesday 13 December 2011 21:23:52 Alexander Neundorf wrote:
> >> Somewhat similar, do we still have the plan to provide like a wrapper
> >> FindKF5.cmake/KF5Config.cmake, which will include all libraries making
> >> up
David Faure wrote:
> On Tuesday 13 December 2011 21:23:52 Alexander Neundorf wrote:
>> Somewhat similar, do we still have the plan to provide like a wrapper
>> FindKF5.cmake/KF5Config.cmake, which will include all libraries making up
>> KF5 ?
>> If so, which library/package should install that ?
On Tuesday 13 December 2011 21:23:52 Alexander Neundorf wrote:
> Somewhat similar, do we still have the plan to provide like a wrapper
> FindKF5.cmake/KF5Config.cmake, which will include all libraries making up
> KF5 ?
> If so, which library/package should install that ?
> Who will install the fi
On Sunday 11 December 2011, David Faure wrote:
> On Sunday 11 December 2011 18:16:08 Alexander Neundorf wrote:
> > So what the kconfig library would provide would be a variable which
> > contains a standard relative directory for installing those files
>
> Yes, this is what I meant. Not an absolu
On Sunday 11 December 2011 18:16:08 Alexander Neundorf wrote:
> So what the kconfig library would provide would be a variable which contains
> a standard relative directory for installing those files
Yes, this is what I meant. Not an absolute path, of course.
> and if the
> current CMAKE_INSTALL
On Friday 09 December 2011, David Faure wrote:
> On Thursday 08 December 2011 22:33:29 Alexander Neundorf wrote:
> > BIN_INSTALL_DIR (default is prefix/bin)
>
> Should we drop that one and use CMAKE_INSTALL_BINDIR?
> Wouldn't that make things more "standard"?
> I see what you're saying by "minimi
On Thursday 08 December 2011 22:33:29 Alexander Neundorf wrote:
> BIN_INSTALL_DIR (default is prefix/bin)
Should we drop that one and use CMAKE_INSTALL_BINDIR?
Wouldn't that make things more "standard"?
I see what you're saying by "minimizing the porting effort", but that can be
scripted easily,
Hi,
in kdelibs4, every application using FindKDE4.cmake gets the following set of
variables, which should be used as install destination with the install()
command:
BIN_INSTALL_DIR (default is prefix/bin)
BUNDLE_INSTALL_DIR (default is /Applications/KDE4 )
SBIN_INSTALL_DIR (default is prefix/
