[ODE] some quick notes on 0.6...

[erwin@erwincoumans.com]

Good point, but both svn repositories are on sourceforge, so it shouldn't 
happen too often that one is available and the other isn't. 

If svn:externals give problems, we can copy the Bullet collision files files 
into the ODE repo (it just means manual merging hassle for changes on both 
sides). 

There is a lot of technical details to document about the integration, in a 
nutshell: projects that don't use the upcoming persistent_space won't depend 
on Bullet. 

I added some more details in the ODE Wiki here:
http://opende.sourceforge.net/wiki/index.php/GJK_collision 

Erwin 

Rodrigo Hernandez writes: 

> 
> I don't really get how the feature works, I am thinking that it links a 
> directory to a different repository and
> gets the files from that repository automaticaly on checkout, is that 
> right? 
> 
> I have no objection either, just wanted to point out that compilation 
> shouldn't break if the
> external was unavailable (of course by disabling GJK), which is the way I 
> understand you're doing it. 
> 
> Cheers! 
> 
> Jason Perkins wrote: 
> 
>> On 6/22/06, Erwin Coumans <erwin at erwincoumans.com> wrote:
>>   
>> 
>>> Do people have objections against svn:externals property pointing to 
>>> another
>>> sourceforge repository?
>>>     
>>> 
>> 
>> I don't...I use that feature myself to include ode in my own project. 
>> 
>> Jason
>> _______________________________________________
>> ODE mailing list
>> ODE at q12.org
>> http://q12.org/mailman/listinfo/ode 
>> 
>>   
>> 
>