[ODE] Difference in collision behavior of Trimesh between LinuxandWIndows

[Rodrigo Hernandez]

 From the syntax of your prompt I think you are running the commands 
form a cmd window,
is this so? sorry, I should have been a bit more specific, try running 
the whole proccess from a MSYS window, a shortcut to it should be on 
your start button->Programs->MinGW->msys

Once inside bash, your c drive would be under /c, so cross your fingers, 
cd to /c/ode-0.5, sh autogen.sh, ./configure --prefix=/MinGW, make. :)

Cheers!

nospam at hardgeus.com wrote:
> The saga continues.  I have the latest source from subversion.  I have
> installed msys, installed the binary automake 1.8.2, the binary autoconf
> 2.59.  When I run them with --version, they report the proper versions.
>
> I ran the autogen.sh and it seemed to be fine.  Configure reports:
>
> Configuration:
>   Target system type:      i686-pc-mingw32
>   Build  system type:      i686-pc-mingw32
>   Host   system type:      i686-pc-mingw32
>   Use double precision:    no
>   Use OPCODE:              yes
>   Use gyroscopic term:     yes
>   Is this a Pentium:       yes
>   Is the CPU x86-64:       no
>   Is this a release build: no
>   Headers will be installed in /usr/local/include/ode
>   Libraries will be installed in /usr/local/lib
>
> When I then run make, I get:
> (NOTE: I called my directory ode-0.5 to keep my paths from breaking...it's
> the correct subversion dir)
>
>
> C:\ode-0.5>make
> Making all in include
> make[1]: Entering directory `/c/ode-0.5/include'
> Making all in ode
> make[2]: Entering directory `/c/ode-0.5/include/ode'
> make  all-am
> make[3]: Entering directory `/c/ode-0.5/include/ode'
> make[3]: Leaving directory `/c/ode-0.5/include/ode'
> make[2]: Leaving directory `/c/ode-0.5/include/ode'
> make[2]: Entering directory `/c/ode-0.5/include'
> make[2]: Nothing to be done for `all-am'.
> make[2]: Leaving directory `/c/ode-0.5/include'
> make[1]: Leaving directory `/c/ode-0.5/include'
> Making all in drawstuff
> make[1]: Entering directory `/c/ode-0.5/drawstuff'
> Making all in src
> make[2]: Entering directory `/c/ode-0.5/drawstuff/src'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory `/c/ode-0.5/drawstuff/src'
> Making all in dstest
> make[2]: Entering directory `/c/ode-0.5/drawstuff/dstest'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory `/c/ode-0.5/drawstuff/dstest'
> make[2]: Entering directory `/c/ode-0.5/drawstuff'
> make[2]: Nothing to be done for `all-am'.
> make[2]: Leaving directory `/c/ode-0.5/drawstuff'
> make[1]: Leaving directory `/c/ode-0.5/drawstuff'
> Making all in ode
> make[1]: Entering directory `/c/ode-0.5/ode'
> Making all in src
> make[2]: Entering directory `/c/ode-0.5/ode/src'
> Makefile:50: *** commands commence before first target.  Stop.
> make[2]: Leaving directory `/c/ode-0.5/ode/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/c/ode-0.5/ode'
> make: *** [all-recursive] Error 1
>
>
>
>
>
>   
>> nospam at hardgeus.com wrote:
>>     
>>> Well 0.5 is the version that's in Gentoo's portage, so I wanted to use
>>> the
>>> same version on Windows that I'm using in Linux to avoid the exact type
>>> of
>>> problem I'm having right now (different behaviors on Linux and Windows).
>>> Also, given that 0.5 is marked as the last stable release, I figured
>>> it'd
>>> be...stable? ;)   I actually have tried pulling from subversion, but the
>>> build process seems different and I can't seem to build it without
>>> autotools.  There is no makefile there by default, nor a user-settings
>>> file.  I don't have bash on my Windows box, so I can't run the
>>> autogen.sh
>>> file.
>>>
>>> Do I need bash and/or Autotools on Windows to build the SVN code?
>>>
>>>
>>>       
>> Yes, just get MSYS from http://www.mingw.org/download.shtml, you will
>> need MSYS. msysDTK, autoconf and automake (binaries),
>> once you install MSYS and msysDTK, unpack the autotools packages on
>> c:\msys\1.0 rather than c:\MinGW.
>>
>> Cheers!
>>
>>
>>     
>
>
>