libglade r543 - in trunk: . doc glade

[murrayc svn gnome org]

Author: murrayc
Date: Mon Aug 18 07:02:45 2008
New Revision: 543
URL: http://svn.gnome.org/viewvc/libglade?rev=543&view=rev

Log:
2008-06-11  Murray Cumming  <murrayc murrayc com>

* doc/libglade-docs.xml: Mention the gmodule-export-2.0 pkg-config 
check for autoconnecting signals. 
* glade/glade-xml.c: (glade_xml_signal_autoconnect): Menton it in the 
reference documentation too.
Fixes bug #446175.


Modified:
   trunk/ChangeLog
   trunk/doc/libglade-docs.xml
   trunk/glade/glade-xml.c

Modified: trunk/doc/libglade-docs.xml
==============================================================================
--- trunk/doc/libglade-docs.xml	(original)
+++ trunk/doc/libglade-docs.xml	Mon Aug 18 07:02:45 2008
@@ -144,10 +144,8 @@
 	flags, and libtool will convert it to the correct
 	format.</para>
 
-	<para>Many people did not see this problem on GNU/Linux with
-	GTK+ 1.2, because the <command>gtk-config</command> script
-	adds the correct flag on that platform.  Such programs would
-	sometimes break when run on alternative platforms.</para>
+	<para>The easiest way to get the correct extra flags is to check 
+	for gmodule-export-2.0 with pkg-config.</para> 
       </note>
 
       <para>To compile the program, we would use the following:</para>

Modified: trunk/glade/glade-xml.c
==============================================================================
--- trunk/glade/glade-xml.c	(original)
+++ trunk/glade/glade-xml.c	Mon Aug 18 07:02:45 2008
@@ -350,6 +350,10 @@
  * the signal handler names given in the interface description with
  * symbols in the application and connects the signals.
  * 
+ * You should add gmodule-export-2.0 to your pkg-config checks to ensure 
+ * that your application's executable exports the signal handlers. This is not 
+ * necessary if the signal handlers are in a shared library.
+ *
  * Note that this function will not work correctly if gmodule is not
  * supported on the platform.
  */