KDE 4 build scripts

Woodsman · 03-13-2013, 06:51 PM

Eric,

How do I build only one component of a package? I'd like to help test some patches. I don't want to build the entire package set for that. I only want to rebuild the affected component package. I saw the note at the top of the KDE.SlackBuild script, but I'm uncertain if more is needed.

Second, for users who build their own packages and want to help with testing, could a command line parameter be added to the build scripts to not strip the debugging symbols from the final package?

I'd like to capture some backtraces but can't do that right now. I can manually edit the build scripts for myself, but I'm hoping a command line parameter could be added to make that easier for everybody. Plus then I'd be sure I'm using the same build scripts as you and Pat.

Possibly something like this:

Code:

if [ "${STRIP_BIN:-yes}" = "yes" ]
  # Strip binaries:
  strip_binaries $PKG
fi

That would work with the main build script, but the individual build script for the dependency packages would need separate attention.

Side comment: I often thought that all Slackware build scripts should contain something like that. Of course, the default would be to strip but with the option some users could rebuild any package when wanting to help with debugging. Just an idea.

Thanks!

volkerdi · 03-13-2013, 09:07 PM

Quote:

Originally Posted by Woodsman

Eric,

How do I build only one component of a package? I'd like to help test some patches. I don't want to build the entire package set for that. I only want to rebuild the affected component package. I saw the note at the top of the KDE.SlackBuild script, but I'm uncertain if more is needed.

./KDE.SlackBuild <module>:<package>

e.g.:

./KDE.SlackBuild kdeedu:blinken

Quote:

Second, for users who build their own packages and want to help with testing, could a command line parameter be added to the build scripts to not strip the debugging symbols from the final package?

I'd like to capture some backtraces but can't do that right now. I can manually edit the build scripts for myself, but I'm hoping a command line parameter could be added to make that easier for everybody. Plus then I'd be sure I'm using the same build scripts as you and Pat.

Possibly something like this:

Code:

if [ "${STRIP_BIN:-yes}" = "yes" ]
  # Strip binaries:
  strip_binaries $PKG
fi

That would work with the main build script, but the individual build script for the dependency packages would need separate attention.

Side comment: I often thought that all Slackware build scripts should contain something like that. Of course, the default would be to strip but with the option some users could rebuild any package when wanting to help with debugging. Just an idea.

Thanks!

As it is, I don't think commenting out a few lines is a high barrier for entry compared with knowing what to do with the debugging output. Unless the plan was to just mail it to us.

Woodsman · 03-13-2013, 09:16 PM

The backtraces likely would not be much useful to you but are pretty much expected and often demanded when posting bug reports to the KDE folks.