I'm creating a separate package for KAlarm, and want to default its
installation path to the KDE installation directory. In CMakeLists.txt I've
got:
find_package(KDE4 4.1.0 REQUIRED)
if (CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT)
set(CMAKE_INSTALL_PREFIX "${KDE4_INSTALL_DIR}" CACHE PATH "In
On 04.06.09 23:49:14, David Jarvie wrote:
> I'm creating a separate package for KAlarm, and want to default its
> installation path to the KDE installation directory. In CMakeLists.txt I've
> got:
>
> find_package(KDE4 4.1.0 REQUIRED)
> if (CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT)
>set(C
On Friday 05 June 2009, Andreas Pakulat wrote:
> However I don't think defaulting to the kde install prefix is a good
> idea
I disagree. Back in the kde3 days I made the autoconf stuff do exactly that.
"checking where to install... /d/kde/inst/kde3 (as returned by kde-config) "
This is because ot
On Friday 5 June 2009 9:20, David Faure wrote:
> On Friday 05 June 2009, Andreas Pakulat wrote:
>> However I don't think defaulting to the kde install prefix is a good
>> idea
>
> I disagree. Back in the kde3 days I made the autoconf stuff do exactly
> that.
> "checking where to install... /d/kde/i
On 05.06.09 10:20:25, David Faure wrote:
> On Friday 05 June 2009, Andreas Pakulat wrote:
> > However I don't think defaulting to the kde install prefix is a good
> > idea
>
> I disagree. Back in the kde3 days I made the autoconf stuff do exactly that.
> "checking where to install... /d/kde/inst/k
On Friday 5 June 2009 11:42, Andreas Pakulat wrote:
> On 05.06.09 10:20:25, David Faure wrote:
>> You need to set $KDEDIRS somewhere that kde startup will read, and rerun
>> kbuildsycoca4, when you use another prefix than your KDE install prefix.
>> So in general it's much easier to install every k
On 05.06.09 14:44:36, David Jarvie wrote:
> On Friday 5 June 2009 11:42, Andreas Pakulat wrote:
> > On 05.06.09 10:20:25, David Faure wrote:
> >> You need to set $KDEDIRS somewhere that kde startup will read, and rerun
> >> kbuildsycoca4, when you use another prefix than your KDE install prefix.
>
On Friday 05 June 2009, Andreas Pakulat wrote:
> How come they know how to checkout from svn and use
> cmake in the first place if they haven't read some kind of tutorial?
Who said anything about svn? People download and compile tarballs.
--
David Faure, fa...@kde.org, sponsored by Qt Software
On 05.06.09 18:12:53, David Faure wrote:
> On Friday 05 June 2009, Andreas Pakulat wrote:
> > How come they know how to checkout from svn and use
> > cmake in the first place if they haven't read some kind of tutorial?
>
> Who said anything about svn? People download and compile tarballs.
Same d
> > > will screw their /usr directory.
> >
> > How? Typically "make install" as user is not able to write into
> > root-owned /usr. So it has to be intentionnal, anyway, in that setup.
/usr/local is root owned too. At least here. So many tutorials say
"sudo make install"
When the user sees the d
On 05.06.09 19:42:12, Michael Jansen wrote:
> > > > will screw their /usr directory.
> > >
> > > How? Typically "make install" as user is not able to write into
> > > root-owned /usr. So it has to be intentionnal, anyway, in that setup.
>
> /usr/local is root owned too. At least here. So many tuto
On Friday 05 June 2009 12:12:53 David Faure wrote:
> On Friday 05 June 2009, Andreas Pakulat wrote:
> > How come they know how to checkout from svn and use
> > cmake in the first place if they haven't read some kind of tutorial?
>
> Who said anything about svn? People download and compile tarballs.
On Friday 05 June 2009, Michael Pyne wrote:
> In addition there are build scripts available to do the hard work of checking
> out, building, and installing KDE, such as kdesvn-build.
Doesn't help for compiling a random app downloaded from e.g. kde-apps.org.
--
David Faure, fa...@kde.org, sponso
On Fri, Jun 05, 2009 at 10:20:25AM +0200, David Faure wrote:
> On Friday 05 June 2009, Andreas Pakulat wrote:
> > However I don't think defaulting to the kde install prefix is a good
> > idea
>
> I disagree. Back in the kde3 days I made the autoconf stuff do exactly that.
> "checking where to inst
Oswald Buddenhagen wrote:
>that's a sign that the plugin system needs to be fixed, not that
>the build system should be screwed up to compensate for it.
>specifically, installing kde to another prefix than qt and still having
>qt see kde plugins works just fine. copying that behavior sounds like a
On Sat, Jun 06, 2009 at 10:59:40AM +0200, Thiago Macieira wrote:
> Oswald Buddenhagen wrote:
> >that's a sign that the plugin system needs to be fixed, not that
> >the build system should be screwed up to compensate for it.
> >specifically, installing kde to another prefix than qt and still having
On 06.06.09 11:15:11, Oswald Buddenhagen wrote:
> On Sat, Jun 06, 2009 at 10:59:40AM +0200, Thiago Macieira wrote:
> > Oswald Buddenhagen wrote:
> > >that's a sign that the plugin system needs to be fixed, not that
> > >the build system should be screwed up to compensate for it.
> > >specifically,
On Saturday 06 of June 2009 11:56:53 Andreas Pakulat wrote:
> On 06.06.09 11:15:11, Oswald Buddenhagen wrote:
> > On Sat, Jun 06, 2009 at 10:59:40AM +0200, Thiago Macieira wrote:
> > > Oswald Buddenhagen wrote:
> > > >that's a sign that the plugin system needs to be fixed, not that
> > > >the build
2009/6/6 Maciej Mrozowski :
> Either this or something else seems to not be the case anyway, as - in my case
> in Gentoo - when we keep 3rd party applications in /usr and - having KDE4
> installed in different prefix - I needed to explicitly instruct those 3rd
> party applications (via prefixes=/u
Andreas Pakulat wrote:
> On 05.06.09 19:42:12, Michael Jansen wrote:
> will screw their /usr directory.
How? Typically "make install" as user is not able to write into
root-owned /usr. So it has to be intentionnal, anyway, in that setup.
>> /usr/local is root owned too. At least here.
On Friday 05 June 2009, Andreas Pakulat wrote:
> On 04.06.09 23:49:14, David Jarvie wrote:
> > I'm creating a separate package for KAlarm, and want to default its
> > installation path to the KDE installation directory. In CMakeLists.txt
> > I've got:
> >
> > find_package(KDE4 4.1.0 REQUIRED)
> > i
21 matches
Mail list logo
