LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-07-2006, 11:31 PM   #1
drkstr
Senior Member
 
Registered: Feb 2006
Location: Seattle, WA: USA
Distribution: Slackware 11.0
Posts: 1,191

Rep: Reputation: 45
build kdm seperate from kdebase


Debian has a sperate package for kdm without having to install the entire kde base system. Has anyone had any luck building kdm buy itself in Slack? I've tried building kdebase with --without-PACKAGE for every directory in kdebase to see if it would only build kdm, but it didn't work. I also tried running './configure' from the kdebase root directory, then 'cd kdm ; make' but I get:
Code:
o -MD -MP -MF ".deps/krootimage.Tpo" -c -o krootimage.o krootimage.cpp; \
then mv -f ".deps/krootimage.Tpo" ".deps/krootimage.Po"; else rm -f ".deps/krootimage.Tpo"; exit 1; fi
make[2]: *** No rule to make target `../../kcontrol/background/libbgnd.la', needed by `krootimage'.  Stop.
make[2]: Leaving directory `/home/drkstr/pkg/src/kdebase-3.4.2/kdm/kfrontend'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/drkstr/pkg/src/kdebase-3.4.2/kdm/kfrontend'
make: *** [all-recursive] Error 1
I need some features in KDM that aren't in XDM, but I don't have the space for the entire KDE system (entire slack install needs to be < 700 MB ). Any ideas?

thanks!
...aaron
 
Old 07-09-2006, 06:53 AM   #2
nykey
Member
 
Registered: Nov 2003
Posts: 360

Rep: Reputation: 30
Hi. I've found this on the BLFS Development book, maybe this is what you're asking for ?

Quote:
Tip

All the KDE packages are comprised of various components. The default is to install most of the components. If specific components are to be eliminated, the official way is to set the variable DO_NOT_COMPILE. This comes in handy when there are problems compiling a particular component.
DO_NOT_COMPILE="component1 component2" \
./configure --prefix=$KDE_PREFIX ...
The core KDE packages also honor this variable, but omitting components from the core packages is not advisable since it may result in an incomplete KDE installation.

Note

In each of the packages, one other option to configure can be added: --enable-final. This option can speed up the build process, but requires a lot of memory. If you have less than 256MB of RAM, this option may cause swapping and significantly slow compilation.
Better look it yourself at THIS LINK. Hope this helps. GL.
 
Old 07-09-2006, 12:43 PM   #3
drkstr
Senior Member
 
Registered: Feb 2006
Location: Seattle, WA: USA
Distribution: Slackware 11.0
Posts: 1,191

Original Poster
Rep: Reputation: 45
Thanks nykey!

I've tried using the --without-PACKAGE switch with ./configure but did not have any success. I'm not sure what the difference is (if any), but I will try it that way to see if it is different.

regards,
...aaron
 
Old 07-09-2006, 12:46 PM   #4
nykey
Member
 
Registered: Nov 2003
Posts: 360

Rep: Reputation: 30
It's worth giving it a shot, and please replay if suceeded or not. Anyway, as it says there, the KDE core packages honor that variable, so ...
 
Old 07-09-2006, 06:21 PM   #5
drkstr
Senior Member
 
Registered: Feb 2006
Location: Seattle, WA: USA
Distribution: Slackware 11.0
Posts: 1,191

Original Poster
Rep: Reputation: 45
Well thanks for the suggestion, this is much more elegant then cd'ing to the directory you want to build, then running make from there. With your method, you can choose to build a package and it's dependencies as well. The problem I ran into is the same as when I initial tried running make from the kdm directory (I needed to build other parts of kdebase to build kdm). I started eliminating more and more stuff from $DO_NOT_COMPILE and before long I was building the entire kdebase system. This is a problem with the way kdm is built, not your solution to build the individual package.

Stupid me though, I never thought to build the entire kdebase, but only install kdm.

These commands from the kdebase root directory is what finally did it.
Code:
./configure --prefix /usr/X11/
make
cd kdm
make install DESTDIR=/<temporary build dir>
cd ../kdmlib
make install DESTDIR=/<temporary build dir>
I then turned my temporary build directory into a Slackware package using 'makepkg' and presto! I have a kdm Slackware package. Hope it works!

regards,
...aaron
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Adding kdm to init.d so LFS boots to kdm StevePhM Linux From Scratch 4 08-08-2005 10:49 PM
kdebase-3.3.0 still won't build. craigs1987 Linux - Software 1 10-02-2004 08:26 AM
Why won't kdebase-3.3.0 build? craigs1987 Linux - Software 1 10-01-2004 06:07 PM
Build problems with kdebase-3.3.0 source. craigs1987 Linux - Software 1 09-23-2004 01:40 AM
Cant run X/KDM after new kernel build, even on old kernel bbska Slackware 2 02-25-2004 11:23 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:55 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration