KBE 1.0 - Build enviroment for KDE

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:  ht
tps://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

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:  ht
tps://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

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:  ht
tps://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

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:  ht
tps://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

On Dec 4, 2007 8:22 PM, Adriaan de Groot <grootkde.org> 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.telemangmail.com
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  ht
tps://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

On Dec 5, 2007 2:22 AM, Adriaan de Groot <grootkde.org> 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:  ht
tps://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

On Dec 5, 2007 3:43 AM, Stefan Teleman
<stefan.telemangmail.com> wrote:
> On Dec 4, 2007 8:22 PM, Adriaan de Groot <grootkde.org> 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:  ht
tps://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

On Wednesday 05 December 2007, Lukas Oboril wrote:
> On Dec 5, 2007 3:43 AM, Stefan Teleman
<stefan.telemangmail.com> wrote:
> > On Dec 4, 2007 8:22 PM, Adriaan de Groot
<grootkde.org> 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:  ht
tps://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

> > 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:  ht
tps://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

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:  ht
tps://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.