Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 03 Mar 2020 18:39:01 -0800
From:      Chris <portmaster@BSDforge.com>
To:        <koobs@FreeBSD.org>
Cc:        freebsd-python <freebsd-python@freebsd.org>
Subject:   Re: Including the correct (python version) include path
Message-ID:  <de1e40493e2bcb330c824762f30f7bd5@udns.ultimatedns.net>
In-Reply-To: <c3e1ec86-023f-32bb-5360-3d31ae63a7c2@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 4 Mar 2020 12:41:59 +1100 koobs@FreeBSD=2Eorg said

> On 4/03/2020 5:58 am, Chris wrote:
> > I'm dragging some code into the 21st century=2E I'm happy to
> > say the python37 AST now gives it a clean bill of health=2E
> > But I'm (currently) only able to build it by prepending
> > the python && python-version to the
> > #include <Python=2Eh>
> > line=2E
> > USES=3D python:3=2E5+
> > doesn't seem to populate -I for my needs=2E If the user has
> > 3, or 4 versions it seems harder=2E Not to mention if malloc
> > option was added, which appends an m to ${PYTHON_SUFFIX}
> > How does everyone deal with this sort of thing?
> >=20
> > Thank you for all your time, and consideration=2E
> >=20
> > --Chris
> >=20
> >=20
>=20
> USES=3Dlocalbase[:ldflags] or set them (CFLAGS+=3D, LDFLAGS+=3D) individu=
ally=2E
>=20
> If you have any other issues or need help, jump on #freebsd-python on=20
> freenode IRC
You're awesome koobs!
Your suggestion makes perfect sense=2E
I may have to start monitoring #freebsd-python

Thanks!

--Chris
FreeBSD 14=2E0-FUTURE #0=2E000 cray256





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?de1e40493e2bcb330c824762f30f7bd5>