Package gtkmm-3.0 was not found in the pkg-config search path
Trying to compile example gtkmm program here: https://developer.gnome.org/gtkmm-tutor ... le.html.en
pkg-config gtkmm-3.0 --cflags --libs produces the following output:
Package gtkmm-3.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gtkmm-3.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gtkmm-3.0' found
However I have installed: apt install libgtkmm-3.0-dev
find /usr -name "gtkmm*" produces
/usr/lib/x86_64-linux-gnu/pkgconfig/gtkmm-3.0.pc
/usr/lib/x86_64-linux-gnu/gtkmm-3.0
/usr/lib/x86_64-linux-gnu/gtkmm-3.0/include/gtkmmconfig.h
/usr/include/gtkmm-3.0
/usr/include/gtkmm-3.0/gtkmm
/usr/include/gtkmm-3.0/gtkmm.h
What's going on here? The compiler produces the error gtkmm.h file not found. Compile command is: g++ main.cpp `pkg-config gtkmm-3.0 --cflags --libs`
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Package gtkmm-3.0 was not found in the pkg-config search pat
-
- Posts: 35
- Joined: 2017-11-30 15:17
-
- Posts: 35
- Joined: 2017-11-30 15:17
Re: Package gtkmm-3.0 was not found in the pkg-config search
What am I supposed to do with that link?
-
- Posts: 35
- Joined: 2017-11-30 15:17
Re: Package gtkmm-3.0 was not found in the pkg-config search
In order to "fudge" this problem I had to set an environment variable.
export PKG_CONFIG_PATH="/usr/lib/x86_64-linux-gnu/pkgconfig;/usr/share/pkgconfig"
However I am fairly certain that this is something a bit out of the ordinary, and that I shouldn't have to be doing this. Why are those paths not set for pkg-config to search by default? From searching online this seems to be something that only Debian 9 users encounter as a problem?
export PKG_CONFIG_PATH="/usr/lib/x86_64-linux-gnu/pkgconfig;/usr/share/pkgconfig"
However I am fairly certain that this is something a bit out of the ordinary, and that I shouldn't have to be doing this. Why are those paths not set for pkg-config to search by default? From searching online this seems to be something that only Debian 9 users encounter as a problem?