[pygtk] Packing concept

2001-03-31 Thread Andre Luis Lopes

Hi all

   I already tried to start learning Gtk some time ago using C, but as I saw 
that there is PyGtk and I'm not as experienced with C, I have started 
learning it. But I never could understand that packing concept.

   I'm really learning PyGtk very quickly. However, there is yet some 
concepts wich I couldn't understand. Could someone try to explain me how the 
packing concept works with Gtk ?

   I know that there is some explanation about this in the Gtk tutorial on 
the Gtk website, but could someone show me an example on how it works ?

-- 
André Luís Lopes
andrelop at ig dot com dot br
___
pygtk mailing list   [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk



[pygtk] PyGtk Documentation

2001-03-31 Thread André Luís Lopes

Hi all

  I'm trying to start learning PyGtk, but it seems that there isn't too much 
documentation looking as a step by step tutorial for dummies like me. 

   I already have tried to start learning by reading some sources but I think 
that with some step by step kind of docs I will be learning better and easier.

  Someone could point me where could I found this kind of documentation ?

-- 
André Luís Lopes
andrelop at ig dot com dot br
___
pygtk mailing list   [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk



Re: [pygtk] new pygtk for gtk 2.0 snapshot

2001-03-31 Thread James Henstridge

On Fri, 30 Mar 2001, Skip Montanaro wrote:

> 
> James> I just put up a new snapshot of devel pygtk at:
> James>   http://www.gnome.org/~james/pygtk2-SNAP-20010330.tar.gz
> 
> James> It requires python >= 2.0 and recent CVS checkouts of glib, pango
> James> and gtk+ to compile.  It is not fully up to date with all the API
> James> additions/changes, but it compiles and runs.
> 
> *sigh*...
> 
> I realize the gnome folks are trying to do me a favor by making it harder
> for me to build glib, pango and gtk+ so that it is correspondingly harder to
> shoot myself in the foot, but I'd like to experiment with James's new
> release and find it frustrating that I should need to know the ins and outs
> of autoconf and/or automake.  Would someone please tell me how to create
> ./configure?  I tried "autoconf" in the glib dir and got a configure script,
> but also this error (and a bunch of warnings about AC_TRY_RUN):

I have never tried building gtk on win32, so probably won't be able to
help that much.  From posts to gtk-devel-list, it sounds like you need CVS
libtool in order to compile it on win32.  I don't know about the other
details.

It probably has build problems on x11 too, because the gtk-2.0.m4 autoconf
macro I was using is broken (it uses gtk-config-2.0 macro, which doesn't
exist anymore -- there is a bug in bugzilla about this).

As far as pygtk goes, you probably want to use the snapshot tarball,
rather than CVS, as the tarball is built with the CVS version of automake
(needed for python support).

James.

___
pygtk mailing list   [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk



Re: [pygtk] new pygtk for gtk 2.0 snapshot

2001-03-31 Thread Roberto J.


--- Skip Montanaro <[EMAIL PROTECTED]> escreveu: > 
> 
> I realize the gnome folks are trying to do me a
> favor by making it harder
> for me to build glib, pango and gtk+ so that it is
> correspondingly harder to
> shoot myself in the foot, but I'd like to experiment
> with James's new
> release and find it frustrating that I should need
> to know the ins and outs
> of autoconf and/or automake.  Would someone please
> tell me how to create
> ./configure?  I tried "autoconf" in the glib dir and
> got a configure script,
> but also this error (and a bunch of warnings about
> AC_TRY_RUN):
> 
> autoconf: Undefined macros:
> configure.in:201:AC_LIBTOOL_WIN32_DLL
> 
> I get the same error when running autoconf on gtk+. 
> No error when running
> in the pango dir, but in all three directories, when
> I run the generated
> configure script I get:
> 
> ./configure: line 602: syntax error near
> unexpected token `AM_INIT_AUTOMAKE($PACKAGE,'
> ./configure: line 602:
> `AM_INIT_AUTOMAKE($PACKAGE, $VERSION, no-define)'
> 
> Every other package I've ever pulled by CVS that
> uses GNU configure to
> generate config.h has come with a working configure
> script.  Why can't these
> packages?
> 
> If it makes any difference, I have autoconf 2.14.1
> and automake 1.4.

HI,

-Try this:

~# ./autogen.sh

~# make

~# make install

-Note that others dependencies could exist, requerided
to build those cvs packages.


s,
roberto




 Roberto J. Teixeira Junior - krivilli
'-'
' http://alsabrazil.sourceforge.net   '
' [EMAIL PROTECTED]   '
'-'

http://www.alsa-project.org


O YAHOO! GEOCITIES CHEGOU AO BRASIL!
Crie sua home page com tudo em português - http://br.geocities.com
___
pygtk mailing list   [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk