>>> Hannu Koivisto <azure@...> seems to think that:
>Last year I asked if one could specify a directory instead of a
>file as :file argument to ede-cpp-root-project in case the top
>level project directory has no files. You, Eric, told that it
>might work if I specified "." without the trailing slash. However,
>at least currently an attempt to give "z:/." as the :file argument
>results to "ede-cpp-root-project: :file for ede-cpp-root must be a
I see that now, as the :file argument gets expanded, which would make
the . go away completely.
>I have to say I find that :file argument extremely unintuitive to
>begin with. If it can be anything and doesn't really matter, as
>the manual says, and its purpose is really to specify the root
>_directory_ of the project, why on earth is it a file, then, and
>not a directory (maybe named :root-directory or something)?
EDE keys its detection of projects off of files. For projects that
auto-detect, this makes sense since the only indication is the file
ede-cpp-root is a wrapper over the basic EDE structure so you can make
an Emacs project that is not detectable on the file system. It needs
to provide some sort of "file" that can be used. Other project types
would use a :file that might be Makefile.am, or something like that.
It is certainly possible to create some new slot that could be used to
derive a :file from. The Emacs project type uses a file not in the
root directory, for example. It has just not been a high priority for
me to figure out.
Basically, ede-cpp-root derives from a class that provides a :file
slot and needs it filled out.
Eric Ludlam: eric@...
Siege: http://www.siege-engine.com Emacs: http://cedet.sourceforge.net