[ODE] ODE with Borland C++ Builder 6 ?

[Amund Børsand]

Thanks, almost works.. :)

geom.cpp, line 1913: Destructor name must match class name
  gr->parts.~dArray();

Didn't know what to do with that, so I commented it out. Then everything
else seems to work except:

[Linker fatal error] Fatal: Illegal option 11

Don't know what THAT means.. :(


Niko Nevatie <nnevatie at welho.com> skreiv:

> Yes, it is possible - I'm running ODE with BCB 6.0 Pro. I did not use 
> the makefiles or the config utility. Just copy the 
> contrib\msvc7\ode_default\config.h file to your ode\include directory. 
> Then you have to make some extra definitions; I think that the following 
> should do the trick (add these to the project conditional definitions):
> 
> WIN32;MSVC;dSINGLE;fabsf=fabs;sinf=sin;cosf=cos
> 
> After that, add ode\include to your project include path.
> Then add all .cpp and .c files to the project (I didn't use tricollider 
> at all, so I skipped the related files). You have to leave a few .cpp 
> files out (I guess stack.cpp and scratchbook.cpp...). Finally try to 
> compile the project. If something fails, let me know - I think I didn't 
> remember everything here. Also, Opcode is much more difficult to compile 
> with BCB 6.0, I've done that too, but it takes some work to modify the 
> source.
> 
> Good luck!
> Cheers
> 
> Amund Børsand wrote:
> 
> >Hi, I'm wondering if it's possible to use ODE with Borland C++ Builder 6?
> >I'm making an editor with interface, I've included the ODE headers and
> >so far so good, but when I'm trying to call some of the ODE functions I
> >get a linker error, undefined reference to.. etc. I've tried linking in
> >libode.a, but first of all I'm not really sure where to do it, and
> >second I don't really have the option to add .a-files. I'm guessing
> >Borland isn't really binary compatible with GCC/MingW/DevCpp (which is
> >what I've compiled ODE with), and when I'm trying to rund Borland's make
> >on ODE I get this:
> >
> >C:\ODE\ode-2003-11-19>make
> >MAKE Version 5.2  Copyright (c) 1987, 2000 Borland
> >Error makefile 25: Command syntax error
> >Error makefile 27: Command syntax error
> >Error makefile 32: Command syntax error
> >Error makefile 33: Command syntax error
> >Error makefile 34: Command syntax error
> >Error makefile 35: Command syntax error
> >Error makefile 36: Command syntax error
> >Error makefile 38: Command syntax error
> >Error makefile 39: Command syntax error
> >Error makefile 40: Command syntax error
> >Error makefile 41: Command syntax error
> >Error makefile 42: Command syntax error
> >Error makefile 75: Command syntax error
> >Error makefile 76: Command syntax error
> >Error makefile 77: Command syntax error
> >Error makefile 78: Command syntax error
> >Error makefile 83: Command syntax error
> >Error makefile 91: Command syntax error
> >Error makefile 94: Command syntax error
> >Error makefile 96: Command syntax error
> >Error makefile 98: Command syntax error
> >Error makefile 101: Command syntax error
> >Error makefile 103: Command syntax error
> >Error makefile 126: Command syntax error
> >
> >.. und so weiter.
> >
> >Any ideas? Or do I have to ditch the whole GUI I'm just starting to feel
> >happy with.. ?
> >
> >Also, I have similar problems with Opcode, GCC complains about
> >asm-statements in the code, Borland won't compile it either, and I just
> >don't have MSVC. Tips here?
> >
> >  
> >
> 
> 

-- 
Amund Børsand <amund £ offroad . no>