On Mon, Oct 04, 2004 at 11:37:33AM -0700, Linda J. Laubenheimer wrote:
*Headdesk* So that's why it won't compile with glib2 and gtk2. It always ended up linking against libmodule 1.2, libglib 1.2, etc.,
Yes. Despite the names, gtk+-1 and gtk+-2 are different libraries. You can't build against one and link against the other, any more than you can build a KDE app and expect it to link against GNOME.
Oh, well, no Dillo on my thin box.
Why not? Gtk+-2 is designed to work alongside gtk+-1 with no problems. I have had them both installed for a couple of years, running dillo and other gtk+-1 and gtk+-2 applications. It's all worked out of the box with no problems.
If you have to install two versions of a library, you've done something wrong.
I agree, but that doesn't apply here. Gtk+-1 and gtk+-2 are *different* libraries. Since no application built against one of them will even look at the other there's no problem. Version hell only happens when an application can link against more than one library on your system and runs the risk of picking the wrong one. The design of Gtk+-2 ensures that this won't happen.
I'm not a C programmer, otherwise I'd fix it and send it to you.
Believe me, there's nothing to fix. Just install both gtk+-1 and gtk+-2 and live happily ever after. I did! Jeremy