I assume that you refer to the Bugzilla comment https://bugzilla.gnome.org/show_bug.cgi?id=653579#c5
To use the version of gtkmm that you have built and installed with 'jhbuild build', you can start a new shell with 'jhbuild shell'. See http://developer.gnome.org/jhbuild/unstable/command-reference.html#command-reference-shell It adds and modifies a lot of environment variables. I'm not sure which ones are really important. Anyway, if you compile, link, and run your application in a shell that 'jhbuild shell' has created, you will use the version of gtkmm that jhbuild has built. tis 2011-08-16 klockan 16:03 +0200 skrev Glus Xof: > Hi guys, > > After the Mr Cumming's response in Buzilla, yesterday, I'm analysing > my Gtkmm installation... > > While I'm working in a Debian GNU/Linux system, the shared libraries > are already installed by package manager... > > On the other hand & for getting the last version, I build Gtkmm (in my > /home folder) using jhbuild & git. > > My hypothese is that my app, according to the newest jhbuild & git > version (and after setting the PKG_CONFIG_PATH envent var) compiles > well, but breaks because it runs according to the content of the older > deb package version. > > If so (if I well realized the problem), how can I solve and finish the > installation ? > (Must copy -or delete- something to /usr/lib.. ?, must set an extra var ?, > ...) > > Glus > _______________________________________________ > gtkmm-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gtkmm-list _______________________________________________ gtkmm-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtkmm-list
