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
Hi,
Am 03.06.2009 um 16:19 schrieb Benjamin Reed:
> I'm taking another run at building KDE/Mac native installer packages,
> and this time I'm using the official Qt4 install packages, which put
> QtUiTools in /usr/include and /usr/lib.
Isn't that a bug in the official Qt4 package?
Why is this stu
12 matches
Mail list logo
