Re: I want to fix a bug in GTK and need some guidance
Thanks for the help! I used JHBuild to build all the stack, and managed to recreate the bug and see it in gdb. Hope I'll fix it soon! On Tue, Jan 24, 2012 at 12:52 PM, Tomeu Vizoso wrote: > On Tue, Jan 24, 2012 at 11:30, wrote: >> Hi Noam, >> >> On 24 January 2012 10:12, Noam Yorav-Raphael wrote: >>> Can someone guide me on how to compile GTK with debugging enabled, and >>> how to compile a C program that would use the GTK I compiled, so I can >>> run it under gdb and try to fix the bug? >> >> It's pretty easy. Download the gtk sources, untar, and compile to a >> local prefix. Something like: >> >> tar xf gtk+-x.x.x >> cd gtk+-x.x.x >> CFLAGS=-g ./configure --prefix=/home/noam/mygtk >> >> You'll need to have the -dev packages for the gtk stack installed so >> that all the headers for all the prerequisites are available, but you >> probably have those already. Once it configures cleanly try: >> >> make >> make install >> >> Now get your build environment to see your new gtk before the system >> one. You need to set PKG_CONFIG_PATH to >> /home/noam/mygtk/lib/pkg-config. >> >> Finally, compile your test program and it'll see your private gtk >> >> gcc -g test.c `pkg-config gtk+-2.0 --cflags --libs` >> >> You can run into trouble if the gtk you build needs a more recent >> cairo / glib / pango / whatever than you have on your system. You'll >> find yourself installing more and yet more libraries to get a working >> gtk stack and then maintaining that pyramid of hand-built packages >> becomes a terrible pain. >> >> Use jhbuild to fix this. It's a Python program which will download, >> configure and install the entire gtk stack from git for you to a >> private prefix, and keep everything updated for you as well. >> >> https://live.gnome.org/Jhbuild >> >> It does take a little fiddling to get it working but it's probably >> worth it if you want to build the very latest code. Plus since >> everything is in git it'll format any bug fixes you make nicely ready >> to be passed upstream. > > I would suggest git over tarballs because when you submit patches you > want to target the top of a branch, not a random past release. JHBuild > will do that for you. > > Also, this may help: https://live.gnome.org/GnomeLove/SubmittingPatches > > Regards, > > Tomeu > >> John >> ___ >> gtk-devel-list mailing list >> gtk-devel-list@gnome.org >> http://mail.gnome.org/mailman/listinfo/gtk-devel-list ___ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list
Re: I want to fix a bug in GTK and need some guidance
On Tue, Jan 24, 2012 at 11:30, wrote: > Hi Noam, > > On 24 January 2012 10:12, Noam Yorav-Raphael wrote: >> Can someone guide me on how to compile GTK with debugging enabled, and >> how to compile a C program that would use the GTK I compiled, so I can >> run it under gdb and try to fix the bug? > > It's pretty easy. Download the gtk sources, untar, and compile to a > local prefix. Something like: > > tar xf gtk+-x.x.x > cd gtk+-x.x.x > CFLAGS=-g ./configure --prefix=/home/noam/mygtk > > You'll need to have the -dev packages for the gtk stack installed so > that all the headers for all the prerequisites are available, but you > probably have those already. Once it configures cleanly try: > > make > make install > > Now get your build environment to see your new gtk before the system > one. You need to set PKG_CONFIG_PATH to > /home/noam/mygtk/lib/pkg-config. > > Finally, compile your test program and it'll see your private gtk > > gcc -g test.c `pkg-config gtk+-2.0 --cflags --libs` > > You can run into trouble if the gtk you build needs a more recent > cairo / glib / pango / whatever than you have on your system. You'll > find yourself installing more and yet more libraries to get a working > gtk stack and then maintaining that pyramid of hand-built packages > becomes a terrible pain. > > Use jhbuild to fix this. It's a Python program which will download, > configure and install the entire gtk stack from git for you to a > private prefix, and keep everything updated for you as well. > > https://live.gnome.org/Jhbuild > > It does take a little fiddling to get it working but it's probably > worth it if you want to build the very latest code. Plus since > everything is in git it'll format any bug fixes you make nicely ready > to be passed upstream. I would suggest git over tarballs because when you submit patches you want to target the top of a branch, not a random past release. JHBuild will do that for you. Also, this may help: https://live.gnome.org/GnomeLove/SubmittingPatches Regards, Tomeu > John > ___ > gtk-devel-list mailing list > gtk-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/gtk-devel-list ___ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list
Re: I want to fix a bug in GTK and need some guidance
Hi Noam, On 24 January 2012 10:12, Noam Yorav-Raphael wrote: > Can someone guide me on how to compile GTK with debugging enabled, and > how to compile a C program that would use the GTK I compiled, so I can > run it under gdb and try to fix the bug? It's pretty easy. Download the gtk sources, untar, and compile to a local prefix. Something like: tar xf gtk+-x.x.x cd gtk+-x.x.x CFLAGS=-g ./configure --prefix=/home/noam/mygtk You'll need to have the -dev packages for the gtk stack installed so that all the headers for all the prerequisites are available, but you probably have those already. Once it configures cleanly try: make make install Now get your build environment to see your new gtk before the system one. You need to set PKG_CONFIG_PATH to /home/noam/mygtk/lib/pkg-config. Finally, compile your test program and it'll see your private gtk gcc -g test.c `pkg-config gtk+-2.0 --cflags --libs` You can run into trouble if the gtk you build needs a more recent cairo / glib / pango / whatever than you have on your system. You'll find yourself installing more and yet more libraries to get a working gtk stack and then maintaining that pyramid of hand-built packages becomes a terrible pain. Use jhbuild to fix this. It's a Python program which will download, configure and install the entire gtk stack from git for you to a private prefix, and keep everything updated for you as well. https://live.gnome.org/Jhbuild It does take a little fiddling to get it working but it's probably worth it if you want to build the very latest code. Plus since everything is in git it'll format any bug fixes you make nicely ready to be passed upstream. John ___ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list
I want to fix a bug in GTK and need some guidance
Hello, My name is Noam Yorav-Raphael. I wrote the DreamPie Python shell, and a bug in GTK ( https://bugzilla.gnome.org/show_bug.cgi?id=611069 ) causes it to crash in some situations. I'd like to fix that bug. I have some experience in writing in C and using gdb, and I'm using Ubuntu 11.10. However, I don't have experience in using autotools and programming GTK in C. Can someone guide me on how to compile GTK with debugging enabled, and how to compile a C program that would use the GTK I compiled, so I can run it under gdb and try to fix the bug? I think I could handle translating the Python program which demonstrates the bug into C. Also, the bug is present in both GTK 3.2.0 and 2.24.6. I'd like it to be fixed in GTK 2, since migrating my application to GTK 3 will mean porting my application to GI which will mean that it will stop working on older systems. I guess it would be trivial to port the fix between the two versions. Thank you very much, Noam ___ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list
Re: I want to fix a bug!
On Wed, 2008-07-30 at 21:09 +0100, Simos Xenitellis wrote: > Hello, > > The "Command Centre" for bugs in the GTK+ library is at > http://bugzilla.gnome.org/browse.cgi?product=gtk%2B And the easier ones, under gnome-love: http://bugzilla.gnome.org/buglist.cgi?query=keyword%3Agnome-love+product%3Agtk%2B+ Usually with instructions on how to fix the problem. Enjoy! ___ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list
Re: I want to fix a bug!
Hello, The "Command Centre" for bugs in the GTK+ library is at http://bugzilla.gnome.org/browse.cgi?product=gtk%2B >From that page you can view bugs by a. component b. milestone c. priority d. severity and more. You can pick easy bugs (severity: minor or trivial), or hard bugs (high priority and severity). Simos On Wed, Jul 30, 2008 at 7:14 PM, Patrick Hallinan <[EMAIL PROTECTED]> wrote: > Hi, > > With help, I got http://svn.gnome.org/svn/gtk+/trunk/ building with > jhbuild. Now I need a bug to work on. I'm a decent C programmer and > I've done a little gtk+ programming but I don't necessarily understand > all the interactions/assumption of gtk+. Any suggestions? > > Pat. > > ___ > gtk-devel-list mailing list > gtk-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/gtk-devel-list > ___ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list
I want to fix a bug!
Hi, With help, I got http://svn.gnome.org/svn/gtk+/trunk/ building with jhbuild. Now I need a bug to work on. I'm a decent C programmer and I've done a little gtk+ programming but I don't necessarily understand all the interactions/assumption of gtk+. Any suggestions? Pat. ___ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list
