Re: Need some tips on wrapping a development version of library
- From: Murray Cumming <murrayc murrayc com>
- To: Krzesimir Nowak <qdlacz gmail com>
- Cc: gtkmm-list gnome org
- Subject: Re: Need some tips on wrapping a development version of library
- Date: Mon, 16 Mar 2009 17:00:45 +0100
On Mon, 2009-03-16 at 15:11 +0100, Krzesimir Nowak wrote:
> Hi,
>
> I'm trying to wrap a 0.19 version of vte, but this situation is rather generic.
>
> I have a 0.17 version of vte installed on my system (Debian) and now I
> need to compile my wrapper on later version. So I compiled vte-0.19
> and installed it in /home/kudi/usr instead of /usr/local or /usr. So
> to check if this even compiles I'm executing configure that way:
> ./configure --prefix=/home/kudi/usr LIBVTEMM_CFLAGS="`pkg-config
> --cflags gtkmm-2.4` -I/home/kudi/usr/include"
> LIBVTEMM_LIBS="`pkg-config --libs gtkmm-2.4` -Wl,-rpath
> -Wl,/home/kudi/usr/lib -lvte". With this everything goes nice until
> examples compilation - here I have undefined references to new API.
> How do set up your environment, when it comes to wrap a development
> version of a C library? I'd rather like to avoid messing with /usr and
> with build system (temporal changes in configure.ac or Makefile.am).
jhbuild does this. When it is set up, "jhbuild shell" puts you in the
parallel environment.
--
murrayc murrayc com
www.murrayc.com
www.openismus.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]