To perform the signal autoconnection, libglade uses the dynamic linker.
It uses the gmodule wrapper, that relies on the fact that if you dlopen()
the file NULL, you should get a pointer to your application's symbol
table.
Now some systems require a special flag in order to make an application's
internal symbols available. For linux gcc, this is the -rdynamic linker
flag. I don't know what flag is required for solaris machines, but it
would be a good idea to find out what the flag is, and make sure you are
using it.
If you are using the gtk-config script to get the compiler/linker flags
and it isn't setting the correct flag, I recommend you bring it up on
gtk-list (for linux, gtk-config --libs includes the -rdynamic flag) so
that it can be fixed.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Thu, 29 Jul 1999, James Macnicol wrote:
> Is anyone successfully using libglade's autoconnect functionality
> on a Solaris machine? I can get it to autoconnect to things in the GTK+
> library (e.g. gtk_main_quit()), but it doesn't want to connect to symbols
> in my executable. I can use nm to find the symbols (i.e. they're not static
> or anything like that). Does anyone have any ideas as to what I'm doing
> wrong? I've played around with the g_module stuff and I can't even get it
> to return a pointer to main() :-(
>
>
> Thanks.
>
>
> --
> James Macnicol
> [EMAIL PROTECTED]
>
> +---------------------------------------------------------------------+
> To unsubscribe from this list, send a message to [EMAIL PROTECTED]
> with the line "unsubscribe glade-devel" in the body of the message.
>
+---------------------------------------------------------------------+
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the line "unsubscribe glade-devel" in the body of the message.
