At 04:34 AM 5/22/2006, David Faure wrote: >I have seen this problem multiple times, but I'm not sure something can be >done about it... >Basically the first time "make" is run, if it triggers a cmake run, then the >new dependencies >are not taken into account. They are only when running make again. > >Example: branches/work/kdelibs4_snapshot was just updated with 2 weeks worth >of trunk/KDE/kdelibs changes, including the renaming of the >ksortablevaluelist.h header. Typing make gave: >make[2]: *** No rule to make target >`/d/kde/src/4/kdelibs4_snapshot/kdecore/ksortablevaluelist.h', needed by >`kdeui/tests/CMakeFiles/kcomboboxtest.dir/kcomboboxtest.o'. Stop. > >Typing make again gave: >[...] >Dependee "/d/kde/src/4/kdelibs4_snapshot/kdecore/ksortablevaluelist.h" does >not exist for depender >"kdeui/tests/CMakeFiles/kcompletiontest.dir/kcompletioncoretest.o". >[...] >and this time there was no problem. > >Is this a problem like "make launches cmake which regenerates makefiles but >then make >doesn't use the new makefiles"? iirc there are solutions to this problem in >general but I forgot >which, I think coolo knows more.
CMake should handle this it uses recursive make calls to make sure the makefiles are re-read. We will try to reproduce this and fix the problem. -Bill _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
