Re: [anjuta-devel] symbol-db progress

[Abderrahim Kitouni <a kitouni gmail com>]

Hello,

              في ث، 08-02-2011 عند 19:48 +0100 ، كتب Sébastien Granjoux:
> Hi Abderrahim,
>
> Le 06/02/2011 22:30, Abderrahim Kitouni a écrit :
> > Well, it seems the project manager is also loading only C headers. I
> > would like it not to load C files in a Vala-only project, since they
> > would be useless and would only clutter the project view.
>
> The project backend add all C header files as children of the 
> corresponding package. I think it doesn't really clutter the project 
> view as the children are not expanded by default. Anyway, if it's 
> completely useless for vala, we can remove them, do you want this ?
Yes, they are useless (but maybe it's not worth the effort to remove
them)


> Is there some other files for vala header ? If yes how could I get them ?
valac looks for PKG.vapi (where PKG is the pkg-config package name), in
vala/vapi and vala-VERSION/vapi directories in system data dirs. (not
really easy, and although nice to have, if we can get something
interesting in the symbol browser, it may be enough).

> Then the issue is to recognize a vala project from a C project, but it 
> could probably be done checking some macros in configure.in. Is 
> autotools project commonly used for vala project ?
As Jens noted, most vala projects use either autotools or waf, but only
autotools is interesting for anjuta.

The only way I can see to identify a "pure Vala" project is to see if
all source files have a vala extension, so it's not really easy. (there
is AM_PROG_VALAC, but 1) it can be replaced by a AC_PATH_PROGS 2) it
only means that the project uses Vala, not that it is pure Vala).

I'd rather wait for the symbol-db issue to be fixed, and then see what
we could do.



Regards,
Abderrahim