Thanks! I will try it out soon.
I agree about the directory issue. We can move the existing tests
into a subdirectory too, and have a sequence of parellel directories.
In cit-gnustep, you specified a file w/ a require. This should be
provided in the load-path. In anycase, if the path is required, you
can use `expand-file-name' to append a base directory to something
more specific. It is more reliable.
It might also be wise to add an attribution and copyright notice to
>>> bardelli.marco@... (Marco <Bj> Bardelli) seems to think that:
>i checked in a simple test for `ede-gnustep.el'.
>It's quite decent, but some strange things happens;
>I don't understand how `ede-auto-add-method' works.
>I can't use the same dir "/tmp/CEDET_INTEG" because
>two different project types conflicts, when in `ede-new' it checks
>:class-sym. I don't know to solve this w/o modity ede.el .
>we'll think how to permit inter-mix of different project types.
>at now we can't:
>because ede-proj-project and ede-step-project are not of the same class,
>either make don't reject this situation.
>I followed the structure of cedet-integ-test (w/o to use srecode :( ),
>and to change dir to /tmp/CEDET_INTEG_ede_GSMake i find-file,
>but during execution via ./cit-test.sh the testing instance of emacs
>ask for add README :( .
>anyway ... please test it.
[ ... ]
Eric Ludlam: eric@...
Siege: http://www.siege-engine.com Emacs: http://cedet.sourceforge.net