On Tue, 2003-10-14 at 18:07, alejandro david weil wrote:
> On Tue October 14 2003 00:05, Malcolm Tredinnick wrote:
> > On Tue, 2003-10-14 at 10:45, alejandro david weil wrote:
> > > first: if i want to reuse objects returned by it, then, I should use the
> > > .defs and .override definitions that pygtk's codegen builds? Is there
> > > another, more.. manual way to do?
> > I don't understand this question. Where do you want to reuse the
> > "objects" (and what objects are you talking about)? Maybe an example
> > would be good.
>
> I mean classes. Only thing I want from librsvg is a function, that reads a
> .svg file an returns a Pixbuf, and I want the Pixbuf created to be of the same
> class that python-gtk2 uses for Pixbufs.
Oh, I see what you want now. The method mentioned in the FAQ about
including other .def files is really the recommended way to do this.
Look at something like the gnome-python/gnome bindings from CVS or a
source tarball (e.g nautilus.override or something similar) to see how
it includes classes from other modules. The required header files will
be installed somewhere under ${prefix}/include/ is you have the
appropriate *-devel packages installed (depends on your distribution).
> > > second: where should I take the pygtk's codegen from? I used the one from
> > > my debian's python-gtk2 source packages, but have had lots of problems
> > > (for example, doesn't have autoget.sh, to automake/confs problems..).. so
> > > i wanted to checkout, if there exists some stable version?
> > Whatever comes with the pygtk sources is really the "official" version
> > and it works well for its purpose (generating the gnome-python
> > bindings).
>
> > Periodically I think that it may not be crazy to release it as a
> > separate package, since the .defs format is good for many language
> > bindings (it is used by a couple of others) and is relatively simple to
> > create for extra packages. I have an unreleased thing at the moment I am
> > working on where I used the .defs format to create the Python bindings.
> > But I have the same problem you do -- it creates an implicit pygtk
> > dependency for a package that doesn't use pygtk.
>
> Mmmh.. the module I made, doesn't seems to import pygtk, is this enough?:
I don't think you are responding to the comment I wrote. :-)
I was talking about the possibility of releasing the codegen stuff as
its own package. Currently to *build* something using codegen, you need
to have the pygtk-devel package installed.
[...]
> > > third: is something like that avaible? where?
> > CVS or a released pygtk tarball.
>
> Well, at least, binary packages from debian:
> ii python2.3-gnom 2.0.0-5 Python bindings for GNOME 2
> ii python2.3-gtk2 2.0.0-2 Python bindings for the GTK+ widget set
> Seems to doesn't have codegen installed :-(
You possibly need the development package for pygtk as well. I am not
familiar enough with Debian's packaging scheme to know for sure.
The codegen stuff comes will then be installed in
${prefix}/share/pygtk/codegen by default. That is why I was mentioning
above that it may be an idea at some point to ship codegen as its own
package so that people can install it without necessarily needing the
pygtk sources.
Cheers,
Malcolm
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
