If you want to use wxGTK you want to use only wx-config to setup your cflags and linker flags.You must not use pkg-config for gtk+ if you're not explicitly calling gtk+ functions.The version of wxGTK knows which version of gtk+ needs to be linked and loaded and it will do this automatically...If you need to call gtk+ api functions you need to set your gtk+ compiler/linker options to match the settings of your wxgtk build.

Thank you, oBFusCATed! At this point, I don't see any need to make calls directly to GTK+, so I will use wx-config as you suggest.

However, I have one more question. Are you suggesting that there is a wx configuration file that I should update, if I want to use gtk+3.0, or is it an internal file specific for the version of wxSmith and that I should just use it however it is configured?

If you want to use wxGTK you want to use only wx-config to setup your cflags and linker flags.You must not use pkg-config for gtk+ if you're not explicitly calling gtk+ functions.The version of wxGTK knows which version of gtk+ needs to be linked and loaded and it will do this automatically...If you need to call gtk+ api functions you need to set your gtk+ compiler/linker options to match the settings of your wxgtk build.

The source code is not needed for correct operation. But installing it might help with debugging what is going on.My guess is that you have assertions enabled and you're hitting on. Start the program in terminal and you'll probably see which one it is.

Thanks for the quick reply! After enabling more debugging, I see that GTK is trying to use both versions 2 and 3!

[debug](Graphs:28558): Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supportedIs there a way to specify which version to use?I'm leery of uninstalling GTK+2.0 since that was on my system initially and I don't want to chance breaking something else.

UPDATE: I just looked through my CodeBlocks linker settings and see that I've added:

The source code is not needed for correct operation. But installing it might help with debugging what is going on.My guess is that you have assertions enabled and you're hitting on. Start the program in terminal and you'll probably see which one it is.