From 'python setup.py build':
> src/_ns_backend_gdk.c:17:25: pygtk/pygtk.h: No such file or
> directory
> However, ...
> [rshepard@...696... ~]$ locate pygtk.h
> /usr/local/pygtk-2.8.6/gtk/pygtk.h
> /usr/local/include/pygtk-2.0/pygtk/pygtk.h
> Do I need to add /usr/local/include/pygtk-2.0/ somewhere
> in setup.py?
In your build environment, see if these directories show up with
> pkg-config --cflags-only-I pygtk-2.0
That is what mpl uses to find your pygtk headers. If not, set your
PKG_CONFIG_PATH environment variable accordingly, and make sure there
is a pygtk-2.0.pc file in that directory. On my system it is in
/usr/lib/pkgconfig/pygtk-2.0.pc
and yours will probably be /usr/local/lib/pkgconfig
It looks like you did a local install of pygtk, but did not update the
pkg-config path to point to it.
JDH
In your build environment, see if these directories show up with
> pkg-config --cflags-only-I pygtk-2.0
John,
Nobody's home.
That is what mpl uses to find your pygtk headers. If not, set your
PKG_CONFIG_PATH environment variable accordingly, and make sure there is a
pygtk-2.0.pc file in that directory. On my system it is in
/usr/lib/pkgconfig/pygtk-2.0.pc
and yours will probably be /usr/local/lib/pkgconfig
Yes. That's just where it is.
It looks like you did a local install of pygtk, but did not update the
pkg-config path to point to it.
Since I work on the main server/workstation, 'local' is a relative term.
Regardless, I added 'export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig/' to
.bash_profile and sourced that file. Did the same for root's .bash_profile.
Now it's building.
Many thanks,
Rich
···
On Thu, 11 Jan 2007, John Hunter wrote:
--
Richard B. Shepard, Ph.D. | The Environmental Permitting
Applied Ecosystem Services, Inc. | Accelerator(TM)
<http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863