Re: [e-users] ephysics and libbullet problems

2014-04-18 Thread Stefan Schmidt
Hello. On Fri, 2014-04-18 at 07:13, Carsten Haitzler wrote: > On Thu, 17 Apr 2014 14:15:57 +0200 Stefan Schmidt > said: > > > Hello. > > > > On Thu, 2014-04-17 at 20:52, Carsten Haitzler wrote: > > > On Thu, 17 Apr 2014 07:24:53 -0400 Will Hopper > > > said: > > > > > > > Thanks for the info

Re: [e-users] ephysics and libbullet problems

2014-04-18 Thread Stefan Schmidt
Hello. On Fri, 2014-04-18 at 09:10, David Seikel wrote: > On Fri, 18 Apr 2014 07:13:46 +0900 Carsten Haitzler (The Rasterman) > wrote: > > > On Thu, 17 Apr 2014 14:15:57 +0200 Stefan Schmidt > > said: > > > > > Hello. > > > > > > On Thu, 2014-04-17 at 20:52, Carsten Haitzler wrote: > > > > On

Re: [e-users] ephysics and libbullet problems

2014-04-17 Thread David Seikel
On Fri, 18 Apr 2014 07:13:46 +0900 Carsten Haitzler (The Rasterman) wrote: > On Thu, 17 Apr 2014 14:15:57 +0200 Stefan Schmidt > said: > > > Hello. > > > > On Thu, 2014-04-17 at 20:52, Carsten Haitzler wrote: > > > On Thu, 17 Apr 2014 07:24:53 -0400 Will Hopper > > > said: > > > > > > > Than

Re: [e-users] ephysics and libbullet problems

2014-04-17 Thread The Rasterman
On Thu, 17 Apr 2014 16:18:19 -0400 Will Hopper said: > Thanks for the info - and bullet *should* have those generic symlinks if > the minor version have compatible features, but it doesn't! the only real > file (other than docs) in the whole package is > /usr/lib/x86_64-linux-gnu/libBulletSoftB

Re: [e-users] ephysics and libbullet problems

2014-04-17 Thread The Rasterman
On Thu, 17 Apr 2014 14:15:57 +0200 Stefan Schmidt said: > Hello. > > On Thu, 2014-04-17 at 20:52, Carsten Haitzler wrote: > > On Thu, 17 Apr 2014 07:24:53 -0400 Will Hopper said: > > > > > Thanks for the info about compatible versions. I was guessing that it was > > > because the files were ca

Re: [e-users] ephysics and libbullet problems

2014-04-17 Thread Will Hopper
Thanks for the info - and bullet *should* have those generic symlinks if the minor version have compatible features, but it doesn't! the only real file (other than docs) in the whole package is /usr/lib/x86_64-linux-gnu/libBulletSoftBody.so.2.82. (and so on for libBulletCollision, etc). So, thats

Re: [e-users] ephysics and libbullet problems

2014-04-17 Thread Stefan Schmidt
Hello. On Thu, 2014-04-17 at 20:52, Carsten Haitzler wrote: > On Thu, 17 Apr 2014 07:24:53 -0400 Will Hopper said: > > > Thanks for the info about compatible versions. I was guessing that it was > > because the files were called libbulletsoftbody.so.2.81 and > > libbulletsoftbody.so.2.81 and tha

Re: [e-users] ephysics and libbullet problems

2014-04-17 Thread The Rasterman
On Thu, 17 Apr 2014 07:24:53 -0400 Will Hopper said: > Thanks for the info about compatible versions. I was guessing that it was > because the files were called libbulletsoftbody.so.2.81 and > libbulletsoftbody.so.2.81 and that the hard coded version number was > causing problems finding it. Anyw

Re: [e-users] ephysics and libbullet problems

2014-04-17 Thread Will Hopper
Thanks for the info about compatible versions. I was guessing that it was because the files were called libbulletsoftbody.so.2.81 and libbulletsoftbody.so.2.81 and that the hard coded version number was causing problems finding it. Anyway, I first looked around for the 2.81 debs online to downgrade

Re: [e-users] ephysics and libbullet problems

2014-04-16 Thread The Rasterman
On Wed, 16 Apr 2014 13:51:51 -0400 Will Hopper said: > Hi everyone, > > Without really paying attention, I recently upgraded the libbullet > libraries on my debian testing system (libbulletsoftbody, > libbulletcollision, etc) from 2.81 to 2.82, breaking efl's dependency on > those libs. It appea

[e-users] ephysics and libbullet problems

2014-04-16 Thread Will Hopper
Hi everyone, Without really paying attention, I recently upgraded the libbullet libraries on my debian testing system (libbulletsoftbody, libbulletcollision, etc) from 2.81 to 2.82, breaking efl's dependency on those libs. It appears the libbullet library files have a hard coded version number in