>>> Joseph Kiniry <kiniry@...> seems to think that:
>I listen to this list and when I see new features discussed that I'd
>like to use or investigate, I update my snapshot of the Cedet
>Unfortunately, nearly every time I do this, compilation of the system
>fails due to a Makefile being out-of-date wrt its Project.ede file.
>After I futz around a bit, hand-loading ede and hand-rebuilding various
>Makefiles in some order, eventually everything works out, but this is
>What is the correct procedure for performing a cvs update and re-build
>of the Cedet repository?
[ ... ]
I usually check in both a Makefile and a Project.ede file.
It should always be OK to touch the Makefile to avoid the dependency.
I think this is because Project.ede comes after Makefile
alphabetically. If the project were stored in the file EDE.Project,
perhaps it might not be a problem?
I had a side project to somehow auto generate the Makefile from
Project.ede from the Makefile, but it was a bit too tricky for a short
I suppose I could keycode a UID into the Project.ede file each time
it is written and the Makefile could test that before complaining. Hmm.
Eric Ludlam: zappo@..., eric@...
Home: http://www.ludlam.net Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: http://www.gnu.org