Date: Thu, 01 Sep 2005 20:29:15 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: ali <aafshar@gmail.com> Cc: gnome@FreeBsd.org Subject: Re: vte widget port and Python extensions Message-ID: <1125620955.66801.5.camel@shumai.marcuscom.com> In-Reply-To: <1125498610l.5442l.9l@hari> References: <1125144872l.5442l.7l@hari> <1125287476.1079.18.camel@shumai.marcuscom.com> <1125498610l.5442l.9l@hari>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-feKulDkuQzHzjb+JbnDY
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Wed, 2005-08-31 at 14:30 +0000, ali wrote:
> On 29/08/05 04:51:16, Joe Marcus Clarke wrote:
> > On Sat, 2005-08-27 at 12:14 +0000, ali wrote:
> > > Hi,
> > >
> > > Thank-you for maintaining this port. I recently had a slight problem
> >=20
> > > installing the Python extensions.
> > >
> > > I set the --enable-python configure argument in the Makefile, and
> > made
> > > the port and installed it. Unfortunately the Python extension cannot
> > be
> > > used because Python can't find the library.
> > >
> > > The Python extension was installed to:
> > >
> > > /usr/X11R6/lib/python2.4/site-packages/gtk-2.0/vtemodule.so
> > >
> > > where the other GTK2 C Python extensions are installed to:
> > >
> > > /usr/local/lib/python2.4/site-packages/gtk-2.0/
> > >
> > > and moving the file to that location allows Python to find it.
> > >
> > > (I guess there may be a reason to put this in the /usr/X11R6 tree
> > > instead of the /usr/local tree.)
> > >
> > > I would love to fix this and send you a patch but I am very
> > > inexperienced with ports and BSD, I shall do anything I can to help
> >=20
> > > though.
> >=20
> > In order for the extensions to work, the port will need to be hacked
> > to
> > install the Python bits under LOCALBASE (much the way net/gaim
> > installs
> > its Perl bits). You could probably use gaim as sort of a model.
>=20
> Well, I have found where the variable is set, and I have a working =20
> Makefile that uses the WITH_PYTHON variable to decide whether to =20
> compile the Python extensions. I am an utter newbie in these things, so =20
> my apologies if something is wrong.
The is very wrong. Setting @pyexecdir@ in the port's Makefile will have
no effect. You'll want to either patch the right Makefile.in in the
distribution, or convert this into a REINPLACE regexp. For example:
@${REINPLACE_CMD} -e 's|@pyexecdir@|${PYTHON_SITELIBDIR}|g' \
${WRKSRC}/path/to/Makefile.in
You will also need to update the pkg-plist with the files that get
installed by enabling Python support.
Joe
>=20
> I have attached a patch for the Makefile.
>=20
> Yours,
>=20
> Ali
--=20
PGP Key : http://www.marcuscom.com/pgp.asc
--=-feKulDkuQzHzjb+JbnDY
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)
iD8DBQBDF5zbb2iPiv4Uz4cRAjqiAJ4rBjL6vleMDCZrVEoq1cZto+dEeACfaEz0
MiaWYP5Y+6PDbIYR/kYCV2g=
=QA50
-----END PGP SIGNATURE-----
--=-feKulDkuQzHzjb+JbnDY--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1125620955.66801.5.camel>