|
From: Patrick H. <pa...@13...> - 2003-05-21 16:50:09
|
Okay, Ben got a build process in place for the GMTL Python bindings, so I
have removed all the GMTL-related code from PyJuggler. I don't know if
PyGMTL has been tested in its new home, but I presume that will happen
shortly if it has not already.
Since the use of GMTL from Python has changed from this:
from PyJuggler import gmtl
to this:
import gmtl
I incremented the PyJuggler version number to 0.5.0. I presume that
PyGMTL will have its own version number now, probably starting at 0.1.0.
In any event, there is no longer a need for the "freeze" on the PyGMTL I
requested yesterday. Feel free to hack away. :)
-Patrick
Patrick Hartling wrote:
> At Ben's request, I have imported the current version of the Python
> bindings for GMTL (which I propose to call PyGMTL or "pig metal").
> These come straight from PyJuggler as of today. Right now, there is no
> way to compile the code, but Ben has volunteered to write a build
> process. Once that is done, I'll remove all the GMTL-related code from
> PyJuggler and update its build to depend on an installed version of
> PyGMTL. Until that time, however, I would appreciate it if no one made
> any changes to the code currently in GGT/modules/GMTL/python. Any
> commits will take the modified file(s) off the vendor branch. If that
> happens and I need to import a newer version of the bindings code from
> PyJuggler, it will be a pain to do so.
>
> -Patrick
>
>
--
Patrick L. Hartling | Research Assistant, VRAC
pa...@13... | 2274 Howe Hall Room 2624
PGP: http://www.137.org/patrick/pgp.txt | T: +1.515.294.4916
http://www.137.org/patrick/ | http://www.vrac.iastate.edu/
|