Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
07-07-2006, 11:31 PM
|
#1
|
Senior Member
Registered: Feb 2006
Location: Seattle, WA: USA
Distribution: Slackware 11.0
Posts: 1,191
Rep:
|
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
|
|
|
07-09-2006, 06:53 AM
|
#2
|
Member
Registered: Nov 2003
Posts: 360
Rep:
|
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.
|
|
|
07-09-2006, 12:43 PM
|
#3
|
Senior Member
Registered: Feb 2006
Location: Seattle, WA: USA
Distribution: Slackware 11.0
Posts: 1,191
Original Poster
Rep:
|
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
|
|
|
07-09-2006, 12:46 PM
|
#4
|
Member
Registered: Nov 2003
Posts: 360
Rep:
|
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 ...
|
|
|
07-09-2006, 06:21 PM
|
#5
|
Senior Member
Registered: Feb 2006
Location: Seattle, WA: USA
Distribution: Slackware 11.0
Posts: 1,191
Original Poster
Rep:
|
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
|
|
|
All times are GMT -5. The time now is 08:55 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|