Re: glibmm building and sigc++ problem
- From: Chris Vine <chris cvine freeserve co uk>
- To: gtkmm-list gnome org
- Cc:
- Subject: Re: glibmm building and sigc++ problem
- Date: Mon, 3 Oct 2005 21:58:14 +0100
On Monday 03 October 2005 02:07, tj wrote:
> Still doesn't work. The problem might be that the libs for sigc++ are
> named libsigc-2.0.0.0 under the build directory
> libsigc++-2.0.16./sigc++/.libs from libsigc++-2.0.16.tar.gz Which then
> is installed as such in /usr/local/lib.
>
> So why is glibmm looking for libsigc++ when the sigc++ distro installs
> it as libsigc?
>
> tj
>
> Paul Davis wrote:
> > TJ,
> >
> > pkg-config needs a path to the lib directory where sigc++ was
> > installed. Pretty much what happened is when you installed those
> > packages from tarball they got put into /usr/local/include and
> > /usr/local/lib ( not /usr/include and /usr/lib ) which is standard
> > behavior for building software.
> >
> > pkg-config needs to see /usr/local/lib/pkgconfig so that it can find
> > the neccessary package information. You can add paths to search by
> > exporting a PKG_CONFIG_PATH that lists directories to search.
> >
> > ie something like export PKG_CONFIG_PATH=/usr/local/ If I recall
> > correctly.
> >
> > To test it and see if its working, try using:
> > pkg-config sigc++-2.0 --cflags --libs
> >
> > That should print out the neccessary stuff for linking against sigc.
> >
> > You'll come to find pkg-config is a very very nice utility for
> > building software if you use it alot. Hope that helps.
> >
> > Paul
[snip]
If it is a PKG_CONFIG_PATH problem (that is, it has not being set to look
in /usr/local) then you need to set it to /usr/local/lib/pkgconfig with this:
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH
The library is called libsigc++, the binary code is (with dynamic linkage)
installed as libsigc-2.0.so.0.0.0, in pkg-config the library flags are stored
in sigc++-2.0.pc (that is, pkg-config views the library name as sigc++-2.0).
Odd naming certainly, but that does not appear to be your problem. It is
much more likely that you have not set PKG_CONFIG_PATH correctly.
Chris.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]