These are my experiences trying to install the Bullet 2.6.2 SDK on a windows XP machine using the cygwin bash prompt.
Following the bullet user manual, I tried to install bullet using ./configure and jam.
I compiled jam and put it into /usr/local/bin. I made Cygwin use the DOS text file type because the scripts in the bullet zip file have CR-LF instead of just LF.
There is no "configure" in the the zip file so I had to run ./autogen.sh
**** When I ran ./autogen.sh I got this error
$ ./autogen.sh
configure.ac:72: error: possibly undefined macro: _AC_SRCPATHS
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
**** The new version of autoconf changed the name to _AC_SRCDIRS. Fixing that,
$ ./autogen.sh
$ ./configure
configure: error: cannot find install-sh or install.sh in mk/autoconf "."/mk/autoconf
**** To add the missing install.sh file, I ran
$ automake --add-missing
configure.ac: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.ac: You should verify that configure.ac invokes AM_INIT_AUTOMAKE,
configure.ac: that aclocal.m4 is present in the top-level directory,
configure.ac: and that aclocal.m4 was recently regenerated (using aclocal).
configure.ac: installing `mk/autoconf/install-sh'
configure.ac: installing `mk/autoconf/missing'
automake-1.9: no `Makefile.am' found for any configure output
automake-1.9: Did you forget AC_CONFIG_FILES([Makefile]) in configure.ac?
**** Now ./configure works
$ ./configure
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking for gcc... gcc
checking for C compiler default output file name... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking if gcc accepts -pipe... -pipe
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to treat C++ warnings as errors... -Werror
checking how to enable C++ PIC generation... no
checking if -shared is accepted... -shared
checking if -soname is accepted... yes
checking for ranlib... ranlib
checking for dlltool... dlltool
checking for dllwrap... dllwrap
checking for windres... windres
checking for strings... strings
checking for objcopy... objcopy
checking for libtool... libtool
checking for libtool... /usr/bin/libtool
checking classification of /usr/bin/libtool... gnu
checking for libtool... /bin/libtool
checking classification of /bin/libtool... gnu
checking how to create a directory... mkdir
checking how to create a directory tree... mkdir -p
checking for install... install
checking for doxygen... doxygen
checking for dot... no
checking for perl5... no
checking for perl... perl
checking for perl5... (cached) perl
checking for TemplateToolkit... no
checking for ttree... no
checking how to disable C++ exceptions... -fno-exceptions
checking for pow in -lm... yes
checking for cosf in -lm... yes
checking for cosf in -lmx... no
checking for dlopen in -ldl... yes
checking for gethostbyname in -lnsl... no
checking for pthread... yes
checking for pthread recursive mutexes... PTHREAD_MUTEX_RECURSIVE
checking how to run the C preprocessor... gcc -E
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking whether -R must be followed by a space... neither works
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for int32... no
checking for windows.h... yes
checking for OpenGL... yes
checking for GLU... yes
checking for GLUT... yes
checking build mode... optimize
configure: creating ./config.status
config.status: creating Jamfile
config.status: creating bullet.pc
config.status: creating config.h
config.status: executing Jamconfig commands
configure:
Please note that this project uses Jam as its build tool,
therefore you must type 'jam' to build the project.
Jam home: http://www.perforce.com/jam/jam.html
Jam source: ftp://ftp.perforce.com/jam/
**** Running jam now
$ jam
warning: unknown rule IncludeDir
warning: unknown rule IncludeDir
warning: unknown rule IncludeDir
warning: unknown rule CleanDir
warning: unknown rule CleanDir
warning: unknown rule Help
warning: unknown rule Help
warning: unknown rule ApplicationIconDefault
warning: unknown rule MsvcGenSubDir
warning: unknown rule MsvcGenSubDir
warning: unknown rule MsvcGenSubDir
warning: unknown rule MsvcGenSubDir
warning: unknown rule MsvcGenSubDir
warning: unknown rule MsvcGenSubDir
warning: unknown rule MsvcGenSubDir
warning: unknown rule MsvcGenTemplateDir
warning: unknown rule MsvcGenWorkspace
warning: unknown rule MsvcGenWorkspace
warning: unknown rule MsvcGenConfig
warning: unknown rule MsvcGenConfig
warning: unknown rule MsvcGenConfig
warning: unknown rule MsvcGenConfig
warning: unknown rule MsvcGenConfig
warning: unknown rule MsvcGenConfig
warning: unknown rule MsvcGenConfig
warning: unknown rule MsvcGenConfig
warning: unknown rule MsvcGenConfig
warning: unknown rule MsvcGenConfig
src/Jamfile: No such file or directory
Extras/Jamfile: No such file or directory
Demos/Jamfile: No such file or directory
warning: unknown rule DoInstall
...found 7 target(s)...
**** I'm stuck for the moment. Anyone? I'd like to use Jam. This could be a cygwin problem only. Or it could happen on linux too; I'm not sure. The msvc project files work great, however.
--David
