KBE 1.0 - Build enviroment for KDE

[Lukas Oboril]

Hi,

K(C)ommon Build Environment - contain all build tools which are needed
for building KDE from source code.

It includes the following tools:

        - pkgbuild 1.2.0
        - GNU make 3.81
        - GNU m4 1.4.10
        - GNU automake 1.9.6 and 1.10
        - GNU autoconf 2.61
        - GNU libtool 1.5.24
        - GNU gettext 0.16.1 (with libiconv support)
        - GNU libiconv 1.11 (with gettext support)
        - ncurses wide 5.6 (ncurses with wide character support)
        - GNU sed 4.1.5
        - GNU awk 3.1.6
        - GNU flex 2.5.33
        - GNU bison 2.3
        - subversion 1.4.5
        - Apache ant 1.7.0
        - GNU coreutils 6.9
        - cvs 1.12.13.1
        - GNU diffutils 2.8.1
        - cmake 2.4.7
        - vim 7.1
        - rsync 2.6.9
        - yasm 0.6.2

If you want a copy, you can fetch from this place
https://svn2.cvsdude.com/kdesolaris/trunk/KBE/

For instal type kbe-install
For uninstall type kbe-remove

Note: you don't need root access for installing the KBE or building
KDE anymore, but the build user needs to have the 'Software
Installation' profile. In a typical case, you just need to add

     user_name::::profiles=Software Installation

to /etc/user_attr.

You can choose destination install directory, but I strongly recommend
to stay with default selection which is /opt/kdebld.

Second recommendation is: set up directory where Sun Studio is
installed, don't leave /usr/bin/cc.

All provided tools are compiled and build on the destination machine
and everything is installed in /opt/kdebld directory.

After successful install you have to type . /opt/kdebld/bin/env.(c)sh
to proper set up environment (set PATH, CC, CXX and so on ...)

I believe that is far enough along to open up discussion and begin
getting feedback form all of you.

Looking forward to you comments!


Luc


--
Lukas 'Luc' Oboril
IRC nickname: luc^ at freenode


When dealing with people, let us remember we are not dealing with
creatures of logic. We are dealing with creatures of emotions,
creatures bristling with prejudices and motivated by pride and vanity.
  Dale Carnegie
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

On Tuesday 04 December 2007 21:55, Lukas Oboril wrote:
> It includes the following tools:

Is that list complete? I don't get it then .. I thought KBE was supposed to
address the dependencies in general? Why is CVS in there? Or ant?
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

On Tuesday 04 December 2007 21:55, Lukas Oboril wrote:
> You can choose destination install directory, but I strongly recommend
> to stay with default selection which is /opt/kdebld.

That doesn't match the naming scheme discussed way long ago, where I
think /opt/kde4.0 and /opt/qt4.3 were decided (I'm not actually sure where
the other dependencies were supposed to go, really ..
possibly /opt/kdesupport).
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

On Tuesday 04 December 2007 21:55, Lukas Oboril wrote:
> K(C)ommon Build Environment - contain all build tools which are needed
> for building KDE from source code.

And, since that might not have been obvious from my previous messages: yay!
Thanks for picking this up.
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Stefan Teleman-2]

On Dec 4, 2007 8:22 PM, Adriaan de Groot <groot@...> wrote:
> On Tuesday 04 December 2007 21:55, Lukas Oboril wrote:
> > You can choose destination install directory, but I strongly recommend
> > to stay with default selection which is /opt/kdebld.
>
> That doesn't match the naming scheme discussed way long ago, where I
> think /opt/kde4.0 and /opt/qt4.3 were decided (I'm not actually sure where
> the other dependencies were supposed to go, really ..
> possibly /opt/kdesupport).

/opt/kdebld is the install directory for the build system (KBE), not for KDE.

--Stefan

--
Stefan Teleman
KDE e.V.
stefan.teleman@...
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Lukas Oboril]

On Dec 5, 2007 2:22 AM, Adriaan de Groot <groot@...> wrote:
> On Tuesday 04 December 2007 21:55, Lukas Oboril wrote:
> > You can choose destination install directory, but I strongly recommend
> > to stay with default selection which is /opt/kdebld.
>
> That doesn't match the naming scheme discussed way long ago, where I
> think /opt/kde4.0 and /opt/qt4.3 were decided (I'm not actually sure where
> the other dependencies were supposed to go, really ..
> possibly /opt/kdesupport).

Hi Adriaan

I'm new in process, could you provide naming scheme ??

Luc
--
Lukas 'Luc' Oboril
IRC nickname: luc^ at freenode


When dealing with people, let us remember we are not dealing with
creatures of logic. We are dealing with creatures of emotions,
creatures bristling with prejudices and motivated by pride and vanity.
  Dale Carnegie
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Lukas Oboril]

On Dec 5, 2007 3:43 AM, Stefan Teleman <stefan.teleman@...> wrote:

> On Dec 4, 2007 8:22 PM, Adriaan de Groot <groot@...> wrote:
> > On Tuesday 04 December 2007 21:55, Lukas Oboril wrote:
> > > You can choose destination install directory, but I strongly recommend
> > > to stay with default selection which is /opt/kdebld.
> >
> > That doesn't match the naming scheme discussed way long ago, where I
> > think /opt/kde4.0 and /opt/qt4.3 were decided (I'm not actually sure where
> > the other dependencies were supposed to go, really ..
> > possibly /opt/kdesupport).
>
> /opt/kdebld is the install directory for the build system (KBE), not for KDE.
>
> --Stefan
>

Yes, KBE is only build system nothing more.



--
Lukas 'Luc' Oboril
IRC nickname: luc^ at freenode


When dealing with people, let us remember we are not dealing with
creatures of logic. We are dealing with creatures of emotions,
creatures bristling with prejudices and motivated by pride and vanity.
  Dale Carnegie
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

On Wednesday 05 December 2007, Lukas Oboril wrote:

> On Dec 5, 2007 3:43 AM, Stefan Teleman <stefan.teleman@...> wrote:
> > On Dec 4, 2007 8:22 PM, Adriaan de Groot <groot@...> wrote:
> > > On Tuesday 04 December 2007 21:55, Lukas Oboril wrote:
> > > > You can choose destination install directory, but I strongly
> > > > recommend to stay with default selection which is /opt/kdebld.
> > >
> > > That doesn't match the naming scheme discussed way long ago, where I
> >
> > /opt/kdebld is the install directory for the build system (KBE), not for
> > KDE.
>
> Yes, KBE is only build system nothing more.

Ah, ok! Then it's much clearer to me:

1) Install KBE so you have all the required build tools.
2) Install KDE dependencies (possibly using the existing build setup in
cvsdude, which is full of GNU makefiles and GNU sed constructs).
3) Build KDE itself.

I was confused by "KDE Build Environment" as if it was about building KDE
itself (and all of its dependencies). Now that that's cleared up, it makes a
lot more sense. Does the name "KDE Build Environment" really fit? I mean,
it's basically a whole bunch of modern build tools you would want anyway.
What about /opt/gnubuild ?

Is the intention to specfile the whole thing as one blob, or each part
individually?

--
These are your friends - Adem
    GPG: FEA2 A3FE Adriaan de Groot


___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Lukas Oboril]

> > Yes, KBE is only build system nothing more.
>
> Ah, ok! Then it's much clearer to me:
>
> 1) Install KBE so you have all the required build tools.
> 2) Install KDE dependencies (possibly using the existing build setup in
> cvsdude, which is full of GNU makefiles and GNU sed constructs).
> 3) Build KDE itself.
>
> I was confused by "KDE Build Environment" as if it was about building KDE
> itself (and all of its dependencies). Now that that's cleared up, it makes a
> lot more sense. Does the name "KDE Build Environment" really fit? I mean,
> it's basically a whole bunch of modern build tools you would want anyway.
> What about /opt/gnubuild ?

Yes it seems to be a better name, but not all of those tools are gnu,
therefore I chose kdebld name (it's based on CBE - common build
environment, which have Sun's Gnome guys and installed /opt/jdsbuild).
It just a name.

>
> Is the intention to specfile the whole thing as one blob, or each part
> individually?
>

Uff I'm sorry, but I don't understand clearly at this point. Do you
are talking about spec files ???

My plan is:  prepare spec file for all tools/libs in current svn (at
cvsdude). One spec file (stdcxx.spec) per tool/lib (Stdcxx). First i'm
preparing 32bit version and then second 64bit version. Now I have
64bit version for stdcxx and boost. These spec files are located in
SPECS directory.

Luc

P.S. Adriaan, please provide me the naming convenction.

--
Lukas 'Luc' Oboril
IRC nickname: luc^ at freenode


When dealing with people, let us remember we are not dealing with
creatures of logic. We are dealing with creatures of emotions,
creatures bristling with prejudices and motivated by pride and vanity.
  Dale Carnegie
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

On Wednesday 05 December 2007, Lukas Oboril wrote:

> > I was confused by "KDE Build Environment" as if it was about building KDE
> > itself (and all of its dependencies). Now that that's cleared up, it
> > makes a lot more sense. Does the name "KDE Build Environment" really fit?
> > I mean, it's basically a whole bunch of modern build tools you would want
> > anyway. What about /opt/gnubuild ?
>
> Yes it seems to be a better name, but not all of those tools are gnu,
> therefore I chose kdebld name (it's based on CBE - common build
> environment, which have Sun's Gnome guys and installed /opt/jdsbuild).
> It just a name.

So it is, so it is (just a name). So we've got all the build things over
in /opt/kdebld (or possibly /opt/kdebuild) and can work from there.

> > Is the intention to specfile the whole thing as one blob, or each part
> > individually?
>
> Uff I'm sorry, but I don't understand clearly at this point. Do you
> are talking about spec files ???

Yes, I meant "are all the components of KBE going to be packaged separately or
will they all be part of one big package?" I don't know the specs work
otherwise.

> My plan is:  prepare spec file for all tools/libs in current svn (at
> cvsdude). One spec file (stdcxx.spec) per tool/lib (Stdcxx). First i'm
> preparing 32bit version and then second 64bit version. Now I have
> 64bit version for stdcxx and boost. These spec files are located in
> SPECS directory.

You didn't list stdcxx earlier: so that is part of kdebld as well? My instinct
is to call that a KDE dependency, not part of the build system. So from here
forwards we could rely on the KBE being available in the rest of the build
setup (take a look in cvsdude Build/, which already held tools and patches
for a number of build tools and a bunch of dependencies).

> P.S. Adriaan, please provide me the naming convenction.

Gosh, that makes me sound so .. bossy. I'm mostly trying to coordinate between
historical decisions which people may be working towards and your work. In
many ways I'd say: *you* are doing stuff, so *you* get to decide.

If I recall correctly, we were going to:

- Install dependencies in /opt/kdesupport, including libstdcxx
- Install Qt in /opt/qt-<version>
- Install KDE in /opt/kde-<version>

But that can be found somewhere in the archives of kde-solaris (or in Stefan's
memory, I'm sure).

--
These are your friends - Adem
    GPG: FEA2 A3FE Adriaan de Groot


___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Shawn Walker-3]

On Dec 5, 2007 8:33 AM, Adriaan de Groot <groot@...> wrote:
> If I recall correctly, we were going to:
>
> - Install dependencies in /opt/kdesupport, including libstdcxx
> - Install Qt in /opt/qt-<version>
> - Install KDE in /opt/kde-<version>
>
> But that can be found somewhere in the archives of kde-solaris (or in Stefan's
> memory, I'm sure).

Personally, I can't support that since all of our C++ things will be
compiled against stdcxx and that makes them incompatible with anything
compiled with the standard C++ library supplied with Solaris.

As a result, I wouldn't want our version of Qt or to be located in
/opt/qt-X since that makes it too easy to conflict with our special
build.

I still think the best option is to do something like:

/opt/kdesupport/qt/4.x
/opt/kdesupport/qt/3.x
/opt/kde/4.x
/opt/kde/3.x
/opt/stdcxx/x.x/

--
Shawn Walker, Software and Systems Analyst
http://binarycrusader.blogspot.com/

"To err is human -- and to blame it on a computer is even more so." -
Robert Orben
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Lukas Oboril]

Hi,

On Dec 5, 2007 3:33 PM, Adriaan de Groot <groot@...> wrote:

> On Wednesday 05 December 2007, Lukas Oboril wrote:
> > > I was confused by "KDE Build Environment" as if it was about building KDE
> > > itself (and all of its dependencies). Now that that's cleared up, it
> > > makes a lot more sense. Does the name "KDE Build Environment" really fit?
> > > I mean, it's basically a whole bunch of modern build tools you would want
> > > anyway. What about /opt/gnubuild ?
> >
> > Yes it seems to be a better name, but not all of those tools are gnu,
> > therefore I chose kdebld name (it's based on CBE - common build
> > environment, which have Sun's Gnome guys and installed /opt/jdsbuild).
> > It just a name.
>
> So it is, so it is (just a name). So we've got all the build things over
> in /opt/kdebld (or possibly /opt/kdebuild) and can work from there.
>

yes.

> > > Is the intention to specfile the whole thing as one blob, or each part
> > > individually?
> >
> > Uff I'm sorry, but I don't understand clearly at this point. Do you
> > are talking about spec files ???
>
> Yes, I meant "are all the components of KBE going to be packaged separately or
> will they all be part of one big package?" I don't know the specs work
> otherwise.
>

Do you know RPM (Redhat Package Manager) package from linux ??? Rpm
packages are prepared by rpmbuild tool from particular spec files (It
could called as "Makefile for rpmbuild"). Guys from Sun made port of
this tool and called it pkgbuild. This Pkgbuild tool create SVR4
package and use quite same spec files as use rpmbuild.

Please look at ... http://pkgbuild.sourceforge.net/

> > My plan is:  prepare spec file for all tools/libs in current svn (at
> > cvsdude). One spec file (stdcxx.spec) per tool/lib (Stdcxx). First i'm
> > preparing 32bit version and then second 64bit version. Now I have
> > 64bit version for stdcxx and boost. These spec files are located in
> > SPECS directory.
>
> You didn't list stdcxx earlier: so that is part of kdebld as well? My instinct
> is to call that a KDE dependency, not part of the build system. So from here
> forwards we could rely on the KBE being available in the rest of the build
> setup (take a look in cvsdude Build/, which already held tools and patches
> for a number of build tools and a bunch of dependencies).

You mix two things together.

1. KBE - Kde build environment - "just build environment" nothing more
- This is a pack of build tools which are needed for _building_ KDE a
their dependencies. KBE live in /opt/kdebld . You can install it by
simple type command -> kbe-install, nothing more isn't need for
install KBE. KBE contains those tools which I mentioned above, on the
top of this thread. After install you can setup your build
environments by /opt/kdebld/bin/env.sh (or /opt/kdebld/bin/env.csh).
These script set up PATH, CC, CXX and so on.

https://svn2.cvsdude.com/kdesolaris/trunk/KBE/


2. SPEC FILES - these spec files will be created for all tools or libs
which are needed for _running_ KDE. None build tools are there. This
directory contains at this moment few spec files.

stdcxx(64).spec > Apache/Rogue wave standart c++ library > done
boost(64).spec > Boost > done
libotf.spec > LibOtf > done
a52dec.spec > A52dec > done
gnump(64).spec > preparing
faac.spec > preparing
flac.spec > preparing

https://svn2.cvsdude.com/kdesolaris/trunk/SPECS/


>
> > P.S. Adriaan, please provide me the naming convenction.
>
> Gosh, that makes me sound so .. bossy. I'm mostly trying to coordinate between
> historical decisions which people may be working towards and your work. In
> many ways I'd say: *you* are doing stuff, so *you* get to decide.
>

I decided ... few weeks ago ...
https://svn2.cvsdude.com/kdesolaris/trunk/SPECS/include/paths.inc

You didn't agree with me :), then I asked you what is the right decision :)

> If I recall correctly, we were going to:
>
> - Install dependencies in /opt/kdesupport, including libstdcxx

I don't understand why this name - kdesupport. I would rather prefer
some more generic name then kdesupport is.

> - Install Qt in /opt/qt-<version>

partial OK, do you think /opt/qt-4.3.2 ??? or /opt/qt4 < I think it's
enough. In other view Stefan is preparing include QT3 and QT4 in to
Solaris as /usr/qt3 and /usr/qt-4.2.3

> - Install KDE in /opt/kde-<version>

same as for qt. I think /opt/kde4 is enough, but you agreed those
paths, I will be accept those paths.


One of advantages spec files (pkgtool) is: the paths can be changed
generally for all spec files from one point.

>
> But that can be found somewhere in the archives of kde-solaris (or in Stefan's
> memory, I'm sure).
>
>
> --
> These are your friends - Adem
>     GPG: FEA2 A3FE Adriaan de Groot
>

Have a nice day

--
Lukas 'Luc' Oboril
IRC nickname: luc^ at freenode


When dealing with people, let us remember we are not dealing with
creatures of logic. We are dealing with creatures of emotions,
creatures bristling with prejudices and motivated by pride and vanity.
  Dale Carnegie
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Lukas Oboril]

On Dec 5, 2007 3:47 PM, Shawn Walker <swalker@...> wrote:

> On Dec 5, 2007 8:33 AM, Adriaan de Groot <groot@...> wrote:
> > If I recall correctly, we were going to:
> >
> > - Install dependencies in /opt/kdesupport, including libstdcxx
> > - Install Qt in /opt/qt-<version>
> > - Install KDE in /opt/kde-<version>
> >
> > But that can be found somewhere in the archives of kde-solaris (or in Stefan's
> > memory, I'm sure).
>
> Personally, I can't support that since all of our C++ things will be
> compiled against stdcxx and that makes them incompatible with anything
> compiled with the standard C++ library supplied with Solaris.
>
> As a result, I wouldn't want our version of Qt or to be located in
> /opt/qt-X since that makes it too easy to conflict with our special
> build.
>

This is the reason why I chose spec files.

You can redefine paths here ....
https://svn2.cvsdude.com/kdesolaris/trunk/SPECS/include/paths.inc a
then you can build all spec files with new (your defined) paths.


Here is snap from libotf.spec

#
# spec file for package FOSSlibotf
#
# includes module(s): libotf
#
%include paths.inc
%include libotf_flags.inc

..... cuted ....

%define _prefix %{_foss_prefix}

...  cuted ....

./configure --prefix=%{_prefix} --with-x --x-includes=/usr/X11/include
--x-libraries=/usr/X11/lib

And if look into paths.inc then you can see ...

... cuted ...

%define _foss_prefix /opt/foss

... cuted ...

If you change %define _foss_prefix to /opt/kdesupport, everything goes
to /opt/kdesupport. It's easy.


> I still think the best option is to do something like:
>
> /opt/kdesupport/qt/4.x
> /opt/kdesupport/qt/3.x
> /opt/kde/4.x
> /opt/kde/3.x
> /opt/stdcxx/x.x/

Stdcxx could be under /opt/kdesupport/ too.

>

As I said paths can be changed generally from one place.


Have a nice day

--
Lukas 'Luc' Oboril
IRC nickname: luc^ at freenode


When dealing with people, let us remember we are not dealing with
creatures of logic. We are dealing with creatures of emotions,
creatures bristling with prejudices and motivated by pride and vanity.
  Dale Carnegie
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[Stefan Teleman-2]

On Dec 5, 2007 9:33 AM, Adriaan de Groot <groot@...> wrote:

> > Yes it seems to be a better name, but not all of those tools are gnu,
> > therefore I chose kdebld name (it's based on CBE - common build
> > environment, which have Sun's Gnome guys and installed /opt/jdsbuild).
> > It just a name.
>
> So it is, so it is (just a name). So we've got all the build things over
> in /opt/kdebld (or possibly /opt/kdebuild) and can work from there.
>
> > > Is the intention to specfile the whole thing as one blob, or each part
> > > individually?
> >
> > Uff I'm sorry, but I don't understand clearly at this point. Do you
> > are talking about spec files ???
>
> Yes, I meant "are all the components of KBE going to be packaged separately or
> will they all be part of one big package?" I don't know the specs work
> otherwise.

I think KBE should be a blob. I'm guessing the "Developer Experience"
expectation is to be able to install KBE as a package, and then start
building KDE + dependencies.

> > My plan is:  prepare spec file for all tools/libs in current svn (at
> > cvsdude). One spec file (stdcxx.spec) per tool/lib (Stdcxx). First i'm
> > preparing 32bit version and then second 64bit version. Now I have
> > 64bit version for stdcxx and boost. These spec files are located in
> > SPECS directory.
>
> You didn't list stdcxx earlier: so that is part of kdebld as well? My instinct
> is to call that a KDE dependency, not part of the build system. So from here
> forwards we could rely on the KBE being available in the rest of the build
> setup (take a look in cvsdude Build/, which already held tools and patches
> for a number of build tools and a bunch of dependencies).
>
> > P.S. Adriaan, please provide me the naming convenction.

> If I recall correctly, we were going to:
>
> - Install dependencies in /opt/kdesupport, including libstdcxx
> - Install Qt in /opt/qt-<version>
> - Install KDE in /opt/kde-<version>

I think there's a bit of confusion here between where our KDE packages
are installed, and what KBE does.

KBE doesn' restrict the location of the install to a specific
directory: the installation location can be specified in the spec
files.

Ade is right about the Standard KDE Location (which is
/opt/kde-<version> and /opt/qt-<version>.

I'm not too crazy about /opt/kdesupport mostly because it doesn't
sound too intuitive to me (in my mind anything with the word "support"
in it is a phone number you call to complain when something isn't
working :-).

Maybe /opt/kdelocal or /opt/kderuntime or /opt/kdesolaris ?

--Stefan

--
Stefan Teleman
KDE e.V.
stefan.teleman@...
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

On Thursday 06 December 2007, Stefan Teleman wrote:
> I'm not too crazy about /opt/kdesupport mostly because it doesn't
> sound too intuitive to me (in my mind anything with the word "support"
> in it is a phone number you call to complain when something isn't
> working :-).
>
> Maybe /opt/kdelocal or /opt/kderuntime or /opt/kdesolaris ?

It's just because we have a SVN module named like that with all kinds of
additional libraries that aren't part of KDE proper, but are dependencies.

Heck, we *could* put everything that KDE4 needs under /opt/kde-4.x, including
Qt and all the other dependencies. Keeps it all out of the way, and should
someone else want to build Qt with a different C++ standard library they can
put it in the more obvious /opt/qt-foo location.

--
These are your friends - Adem
    GPG: FEA2 A3FE Adriaan de Groot


___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

On Thursday 06 December 2007, Lukas Oboril wrote:
> > So it is, so it is (just a name). So we've got all the build things over
> > in /opt/kdebld (or possibly /opt/kdebuild) and can work from there.
>
> yes.

Can we get an option to put stuff in a different prefix? The KDE4 build
machine doesn't give us write access to /opt (I can arrange that, given time,
but it's kind of annoying).

--
These are your friends - Adem
    GPG: FEA2 A3FE Adriaan de Groot


___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.