Building KDE 4.8.5 from Slackware sources - few remarks
Hi,
I'm currently building KDE 4.8.5 from the Sources found on the Slackware DVD. If you wonder why I would do such a thing: I'd like to tweak the KDE desktop like Tomas M. from Slax did: only build needed apps, and don't build those I never intend to use. Plus, build in a few enhancements. First things first, one dragon at a time. The master KDE.SlackBuild allows either building all KDE packages in one go, or build modules individually by passing them as an argument. All modules are listed in the script, around the line 420: Code:
KDEMODS=" \ Code:
# ./KDE.SlackBuild kdelibs
Is this intended or just a minor bug in the build script? Cheers, Niki |
Hello,
This is documented in the SlackBuild: Code:
# Yes, we know kde-workspace is built twice. kdebase needs the SeB |
Yes, I know kdebase is built twice. But here, the package is compiled twice immediately after the first build. That's something else. I'm talking about the package construction with makepkg immediately after the first build.
|
It's a side effect of having "kdelibs" both as the name of a module sub-package (inside modules/kdelibs) and as the module name itself (modules/kdelibs). This should be optimized at some point. But it does not hurt, so the priority is low...
Eric |
Quote:
|
Thanks for the clarification. Now I've found some other curiosity that's bugging me. Here goes.
The master KDE.SlackBuild calls a series of custom cmake scripts: Code:
# Run cmake, using custom cmake script if needed: Code:
# ./KDE.SlackBuild kdelibs But the same thing seems to fail with cmake/kdebase. Meaning I can add whatever I want at the top of cmake/kdebase and then run this: Code:
# ./KDE.SlackBuild/kdebase So I have to conclude cmake/kdebase is ignored by the master script. Which is a pity, because that's precisely where I would have put my customizations, like specifying which apps to build and which to leave out (like Konqueror for example). Any idea what's wrong here? |
OK, I'll answer that myself, I think I just found out. If there's no file in the cmake directory corresponding to the exact module name (like kde-baseapps) and not the mere "big" package name (like kdebase), then the default 'cmake' file is included.
Now here's the solution to the problem: Code:
# cd cmake Code:
cat CMakeLists.txt | \ |
BTW, I'd be curious to know what XAP stuff is exactly needed for various KDE packages to either build or run.
|
Quote:
Code:
The following OPTIONAL packages could NOT be located on your system. If any required software is missing, you will not even get past the "cmake" step of the module. Eric |
I would be grateful if the OP would post a copy of these customized scripts! :) I started tinkering with the same idea --- to create a custom package set with only the desired elements. I've been busy and never got very far.
|
Quote:
Eric |
Quote:
|
Quote:
|
Okay, thanks. My big bump right now is I can't figure out how to build Qt4 with the QT_NO_TOOLTIP option. The build always fails. :(
|
Well, just ignore the tooltips. Or as some yoga teacher once said to me: don't think about that pink elephant. :D
|
Quote:
|
Quote:
|
Here's another curiosity. The KDE-specific desktop menu entry files in /usr/share/applications/kde4 all have rwxr-xr-x (755) permissions, instead of "plain" 644. Of course, it's just a minor weirdness, but I thought I'd report it anyway.
|
Quote:
|
OK, now I have a more serious problem. The 'kdemultimedia' package can be built against ffmpeg. But when doing so, I get the following error.
Code:
... |
All times are GMT -5. The time now is 02:37 AM. |