Source not regenerated after new kconfig_compiler executable

[David Faure]

On Wednesday 23 May 2007, Alexander Neundorf wrote:
> On Tuesday 22 May 2007 14:59, David Faure wrote:
> > On Tuesday 22 May 2007, Christian Ehrlicher wrote:
> > > Hi,
> > >
> > > Don't know if it's intended or a bug in the dependency chain. The output
> > > from kconfig_compiler is not regenerated after I installed a new
> > > kconfig_compiler executable. Therefore I still got warnings about
> > > kstaticdeleter until I delete the sources by myself :)
> >
> > Yeah but would you really want to see all kconfig_compiler-generated files
> > re-created every time kdelibs is reinstalled - even though in 99% of the
> > cases
> >
> > >from now on, the logic inside kconfig_compiler won't have changed?
> >
> > (but it will have been relinked because kdecore changed).
> >
> > Maybe we need to install a cmake file with the version number of
> > kconfig_compiler, in order to trigger a recompilation only when the version
> > of kconfig_compiler is newer than the version that was used to generate the
> > current generated files...
> 
> Adding the dependency to the installed kconfig_compiler shouldn't be a  
> problem, if we really want that.
> But I'm not sure we actually want it, as Christian and Matt also suggest.

Yes, which is why I'm talking about making the rule compare hand-adjusted version numbers,
not just a timestamp-based dependency.


-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).