Re: [Pyode-user] Debian packaging available for PyODE

[Jean de L. <jla...@gm...>]

That's great Josh! I meant to do it a while ago, but never completely
got around to doing it (/me slaps /me).
I stumbled across a problem when I started looking into it: the Debian
ODE package has trimeshes disabled because OPCODE has some problems on
certain arches. I thus had to rebuild the debian ODE package for
myself and have PyODE build off that... What have you done about this?
Have you disabled trimeshes in your package? If yes, would it be
vaguely possible to provide a libode package with OPCODE and trimeshes
enabled, along with the appropriate PyODE package? Yeah I know,
"give'em the hand and they'll want the whole arm" ;)
It'd also be really nice to have this package included in Debian...
have you looked into that possibility?

Thanks a lot for your work!
John

On 12/2/05, Josh Triplett <jo...@ps...> wrote:
> [Please CC me on replies, as I'm not subscribed to the list.]
>
> Hello,
>
> I've created Debian packages for PyODE 1.1.0; you can find them at
> <http://psas.pdx.edu/~josh/pyode>.  (Not apt-gettable, as that isn't a
> permanent repository.)  These packages are built against latest Debian
> unstable, and include packages for both python 2.3 and 2.4.
>
> In order to build with GCC 4.0, I remove the pre-generated pyrex output
> files and force setup.py to rebuild them, as Debian's pyrex packages
> include a patch to fix the generated code so GCC 4.0 can compile it.
> You might want to generate the release tarballs with a similarly patched
> pyrex, to fix this issue for other users.  It would also be helpful to
> have an option for setup.py to always rebuild the output files.
>
> I also had to patch the paths in setup.py, since looking in "../ode" for
> ODE source will not work.  On Debian at least, the include files are in
> /usr/include, the libraries are in /usr/lib, and the user-settings file
> is available at /usr/include/ode/config/user-settings, so I changed
> ODE_BASE to "/usr", and changed the file location to
> os.path.join(ODE_BASE, "include", "ode", "config", "user-settings").  It
> would be helpful if the default ODE_BASE was "/usr" on non-Windows
> systems, since those systems would usually want to use a system-wide
> ODE.  I don't know whether the user-settings path will work on all
> systems; in particular, the path will differ if grabbing it out of an
> ODE source directory.  Some possible solutions for that would be to move
> the path to the user-settings file into the system-specific section (if
> it is the same on all non-Windows systems) or trying several different
> paths (ODE_BASE/include/ode/config/user-settings,
> ODE_BASE/config/user-settings, etc) and using the first working path.
>
> Thank you for PyODE.  I hope you find these packages useful.
>
> - Josh Triplett
>
>
>