Re: [gobo-eiffel-develop] geant file for libexml

[Eric B. <er...@go...>]

Andreas Leitner wrote:
> 
> Yes, but this design assumes we do not get another option. For example
> the xml examples can be compiled with or without expat. Other such
> options will surely come with time. Now do I need for each option touch
> misc/eiffel.eant and add rules (which would clutter it up) that only
> make sense for some projects.

No, don't add anything to misc/eiffel.eant, just add a new
.eant file in misc (say misc/cc.eant) that inherits from
misc/eiffel.eant and adds the various C compilation rules
parameterized with geant's local variables (in the same way
the 'compile_<compiler>' targets in misc/eiffel.eant are
parameterized).

> That was my first approach, meanwhile I put this clause out again,
> because IMO it is a little ugly. So I added a remark to put a symlink
> from "studio" to "bench".

It's your point of view, but I find my solution less ugly,
and no need to modify the ISE installation (remember that
Gobo should ideally work out of the box).

> Aehm, sorry, that was a little unclear. What I meant to say was that
> makefiles do only tasks they have to do. Based on dependency analysis -
> using timestamp checks etc.

A similar mechanism will probably be partially implemented
in geant. Sven already started to look at how it could be
designed.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com