Source not regenerated after new kconfig_compiler executable
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 :) Christian signature.asc Description: OpenPGP digital signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Source not regenerated after new kconfig_compiler executable
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... -- David Faure, [EMAIL PROTECTED], sponsored by Trolltech to work on KDE, Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org). ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Source not regenerated after new kconfig_compiler executable
David Faure schrieb: 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). Don't know - but it's maybe a more generic question. Should a generated file get regenerated when the generator is updated. 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... I think a 'rm -fr build-dir' is easier :) Christian signature.asc Description: OpenPGP digital signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Source not regenerated after new kconfig_compiler executable
On May 22, 2007, at 2:13 PM, Christian Ehrlicher wrote: David Faure schrieb: 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). Don't know - but it's maybe a more generic question. Should a generated file get regenerated when the generator is updated. I'd say the answer to that question is no. Otherwise, you'll be regenerating all your generated files for every build. 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... I think a 'rm -fr build-dir' is easier :) Christian Agreed. :) Matt ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Source not regenerated after new kconfig_compiler executable
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. Bye Alex ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
