Re: [evolution-patches] Getting e-d-s working with gnome-build

[David Malcolm <dmalcolm redhat com>]

On Sun, 2005-06-05 at 00:37 +0200, Philip Van Hoof wrote:
> 
> Hi there,
> 
> 
> This rather strange patch will remove the fact that all the
> "targetdir" variables are declared in the configure.in file. 
> 
> You see the thing is, these days some IDE's will try to parse the
> Makefile.am files. Gnome-build (which you can find in cvs.gnome.org)
> is such a parser being used by a popular development environment
> (Anjuta 2.0). Gnome-build, however, won't succeed in parsing a
> Makefile.am where the target isn't complete (for example where the
> targetdir variable isn't specified). Therefore , and since Anjuta uses
> gnome-build, e-d-s can't be used with a IDE like Anjuta 2.0.
> 
> This patch will modify that. It will put the targetdir variables in
> the Makefile.am's. Since the locations depend on variables like
> API_VERSION they shouldn't be changed manually anyhow. They aren't
> locations that change often or frequently. And not much developers
> want to specify the location would the build-environment instruct the
> pre-compiler to alter filepaths if a developer would do this.
> 
> So I don't see any good reason for putting it in the configure.in
> file. And since doing that does cause that some useful tools, like
> gnome-build, get confused; I'd prefer it to be like most
> Makefile.am/configure.in combinations.
> 
> I also attached a screenshot which shows that after you apply this
> patch, the gnome-build test application will successfully load e-d-s
> by parsing it's Makefile.am infrastructure.

The screenshot looks cool.

> 
> Making it possible to develop the different Evolution components using
> IDE's like Eclipse (Some Eclipse developers are planning to start
> using gnome-build in the CDT plugin of Eclipse -- I talked to Andrew
> and Ben  on GUADEC about this --), will make it more easy for
> newcomers to join the Evolution project. It's my opinion that
> therefore, we shouldn't ignore the different development tools and
> environments (like Eclipse, Anjuta, etcetera).

I'm hoping to get this running for Eclipse at some point.

However, maybe it would be better to patch gnome-build instead, so that
it can handle situations of this kind?  You'll need to give the
Makefile.am parser information on the content of configure.in

Has this been discussed on the gnome-devtools list?