* Alexander Neundorf <neundorf@xxxxxxxxxxxxx> schrieb: > > That's why I prefer an purely descriptive paragidm (= subset of > > delcarative, but practically no logic): a buildfile should only > > describe the package's structure (eg.: "i have some executable foo > > which consists of source [...] and imports libs [...]), so the > > buildtool (and user's config) can cope with it all. > > This was also the plan for cmake when it was started. But it turned > out that this is not enough, and for more complex projects some > programming logic is required. So cmake turned from quite declarative > to quite imperative over time. And so you just open the Pandorra's Box again ;-o As soon as you try to build some one-fits-all-solution, you'll sooner or later run into similar problems as autoconf has. I won't to that w/ my TreeBuild. It is intentionally limited on easily structured packages. People should either structure their packages properly use something else ;-P cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/ --------------------------------------------------------------------- Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ --------------------------------------------------------------------- -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
