[ODE] Autotools added to UNSTABLE
Gary R. Van Sickle
g.r.vansickle at worldnet.att.net
Mon Apr 11 23:01:07 MST 2005
Excellent Rodrigo! I'll take a look at this as soon as I can. For those
who may not know much about autotools, Rodrigo has just improved the ODE
package's cross-platformness by about a billion percent.
Gary R. Van Sickle
> -----Original Message-----
> From: ode-bounces at q12.org [mailto:ode-bounces at q12.org] On
> Behalf Of Rodrigo Hernandez
> Sent: Monday, April 11, 2005 8:51 PM
> To: ode at q12.org
> Subject: [ODE] Autotools added to UNSTABLE
> Hello All,
> I have added autotools support to UNSTABLE, this in no way
> affects the current build system, for now it is just a new
> option to build ODE.
> I have successfully tested the procedure on MinGW, Cygwin and
> Linux (Fedora Core 3), so, I would like to ask those who have
> 64bit CPUs and Mac computers to test the procedure and to
> find what tweaking needs to be done.
> Here is the text I added to INSTALL, please let me know what
> do you think :):
> ODE NOW HAS AUTOTOOLS SUPPORT!!!!
> if you want to build ODE with autotools follow these steps,
> if not skip
> (0) if you are building from CVS you must bootstrap the process first
> by running:
> $ sh autogen.sh
> you may see some "underquoted definition" warnings
> depending on your
> platform, these are (for now) harmless warnings regarding scripts
> from other m4 installed packages.
> (1) The default build process builds ODE with single
> precision, no trimesh
> support, and debug enabled (leaves OPCODE out), if this
> is what you want,
> simply run:
> $ ./configure
> double precision is enabled with the argument
> opcode support is enabled with the --with-opcode
> argument, and finally,
> a release build is enabled with --enable-release.
> So, if you want to build ODE with trimesh support, you would run:
> $ ./configure --with-opcode
> if you want to build ODE with trimesh support and double
> $ ./configure --with-double-precision --with-opcode
> etc, each of these arguments are independent of each other.
> (2) Run:
> $ make
> (3) To install the library run:
> $ make install
> Autotools Notes:
> 1. Currently because of the nuisances of the Windows DLL system shared
> libraries are disabled, so autotools will build a static
> library only,
> on non Windows systems, you can get a shared library by adding the
> argument --enable-shared to the configure script.
> 2. the autotools build process creates and installs a
> 'ode-config' script
> similar to that of gtk, useful for passing cflags and libs
> to your projects,
> run ode-config from a command prompt to find out how it works.
> 3. The initial autotools build support was written by
> Rodrigo Hernandez (kwizatz at aeongames.com) feel free to
> contact me,
> if you have any questions regarging the ODE autotools scripts.
> ODE mailing list
> ODE at q12.org
More information about the ODE