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

[Andreas L. <no...@sb...>]

On Mon, 2001-10-22 at 10:29, Eric Bezault wrote:
> Andreas Leitner wrote:
> > 
> > So if we start with:
> > 
> > compile_ise
> > compile_se
> > compile_hact
> > compile_ve
> 
> Note that I use these above for ease of calling. We
> could have things like that:
> 
>   geant --define="GOBO_EIFFEL=ise" compile
> 
> instead of:
> 
>   geant compile_ise
> 
> but I thought that the short-cut was easier to use
> (even though more cumbersome to write).

Sure, a --define is ok with me. Some kind of autoconf tool could still
generate the correct geant call based on a configuration.eant file then.

> What's wrong with:
> 
>   geant --define="expat=true debug=true posix=true" compile
> 
> ? Once again having many 'compile_*' tasks was just to make
> the geant command-line easier to type, but if we want to
> make build files easier to write we can use the above
> command-line syntax instead.

I am cool with --define, I was just afraid that compile_* would be the
_only_ way for passing options to geant.
 
> > This also much more reflects the usage. I do not switch from debug
> > builds to release builds on every compile.
> 
> I do. I try to run tests every so often to check that
> the Gobo classes are still consistent, and I try to do
> that in all compilation modes.
> 
> > Well, but you assume that all linux users have the latest beta. Earlier
> > versions do have the old path.
> 
> It is very hard to support several Eiffel compilers, so as
> a rule of thumb we should only support one version per
> compiler. So either we decide to support ISE 4.5 or 5.0.
> Then it's up to the users to patch whatever needs to be
> patched in order to make Gobo work if they don't use the
> supported compiler version. In our case we are still in
> development phase (i.e. the version in CVS is not an
> official release of Gobo), so the rule does not need to
> be as strict, but official Gobo releases should definitely
> support only publicly available Eiffel compilers. Beta
> versions of SmallEiffel can be considered publicly available,
> but not those of ISE. Anyway I hope that ISE 5.1 will be
> officially released before we have an official version
> of Gobo, so this discussion is probably already obsolete ;-)

Yep, that's why I made a symlink on my installation and used the path
with bench in the build file. Once Eiffel 5.1 is out, I can rename the
file. If that is ok with you, otherwise, I go and change it back to the
variable solution.

Andreas