On Wed, Dec 11, 2013 at 11:06 AM, Ken Bass <daytoo...@gmail.com> wrote: > I know that this subject has been asked and answered many times, and I have > been googling for several days to try to find an answer that works, but to > no avail. So, sorry in advance... >[...] > and the compile and like commands: > > gcc -I/usr/include/cairo -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 > -I/usr/include/freetype2 -I/usr/include/libpng15 -I/usr/include/libdrm > -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ > -I/usr/include/pango-1.0 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/harfbuzz -I/usr/include/atk-1.0 > -I/usr/include/at-spi2-atk/2.0 -O0 -g3 -Wall -c -fmessage-length=0 > -export-dynamic -o test.o ../test.c > > gcc -o test test.o -lcairo -lgdk-3 -lpangocairo-1.0 -lgdk_pixbuf-2.0 > -lcairo-gobject -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lgmodule-2.0 -lgtk-3 > -latk-1.0 -lgio-2.0 -lcairo -lgdk-x11-2.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 > -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lgdk-3 -lcairo-gobject -lgmodule-2.0 > -lgtk-3 -latk-1.0 -lgio-2.0
Since you are linking gdk-x11, I assume you are building for Linux. The documentation at https://developer.gnome.org/gtk3/stable/GtkBuilder.html#gtk-builder-connect-signals suggests that you should be linking against gmodule-export-2.0, which is a different thing than gmodule-2.0. And I think the --export-dynamic needs to be an option in the second gcc command, as the -Wl,--export-dynamic in the documentation instructs the compiler to use the export-dynamic option at link time. _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
