[ODE] configure improvements

[Bram Stolk]

Rodrigo Hernandez wrote:
> Using the config script would require ODE to be already installed, so we 
> get a catch 22 situation.

Also if we have 2 configure.in files? One for lib, one for examples,
a la plib?
(The ../../drawstuff/texture spec could be moved from the lib to the app)

> Instead we could define the string on config.h and leave 
> "../../drawstuff/textures" as default when no config.h is provided.

The cleanest solution could be making the textures an install target,
and put them in $prefix/share/ode

At compile time, we will now the install targets, so we know where
to look for them.

If we want to know at run-time, not compile-time, we could use
the ode-config script, but only with 2 configure.in's I figure.

If we go for 2 configure.in files, we would have the benefit
of providing a good example on how to properly use ode in other
autoconf based applications.

    Bram


> Bram Stolk wrote:
> 
>> To really clean up the autoconf/automake interface, we could
>> opt for the approach used in the plib project:
>> seperate configure.in files for the lib, and the examples.
>>
>> If we went this route, we could do it properly, using sutff
>> like:
>>
>> CXXFLAGS = `ode-config --cflags`
>>
>> 'make install' creates a file $prefix/bin/ode-config which
>> should be used by applications using ode. It's much like
>> fltk-config mechanism.
>> Currently, this mechanism is unused in ode.
>> We should consider using it.
>>
>>  
>>