kconfig_compiler moved to libexec
faure at kde.org
Fri May 18 09:21:33 BST 2007
On Thursday 17 May 2007, Alexander Neundorf wrote:
> On Wednesday 16 May 2007 03:56, David Faure wrote:
> > On Tuesday 15 May 2007, Oswald Buddenhagen wrote:
> > > On Tue, May 15, 2007 at 12:44:15AM +0200, David Faure wrote:
> > > > Because kconfig_compiler moved from bin/ to lib/kde4/libexec,
> > >
> > > now, that confuses me a bit - this is a development tool, but not really
> > > a runtime helper (which libexec is for - executables with lib
> > > character). am i missing something?
> > Hmm, you are correct. I was given a list of conflicts between kdelibs3 and
> > kdelibs4, (committed to kdelibs/CONFLICTS) but that list contains all the
> > development tools, which are not a problem since only the development tools
> > for one of the two kde versions can be installed at a given time in a given
> > prefix (due to the .so symlinks).
> > Now what... should I revert the kconfig_compiler move?
> How about renaming it to kconfig_compiler4 ?
Not necessary since there's no way to install kdelibs3-dev and kdelibs4-dev (add one on distros which use .so version numbers ;)
concurrently, as said above.
Reverted. Those who updated since last monday should do this after updating kdelibs:
1) delete $KDEDIR/lib/kde4/libexec/kconfig_compiler
2) run this command from the parent directory of your build dirs
perl -pi -e 's,lib/kde4/libexec/kconfig_compiler,bin/kconfig_compiler,g' */CMakeCache.txt
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
More information about the kde-core-devel