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>
index | next in thread | previous in thread | raw e-mail
On Wed, 4 Mar 2020 12:41:59 +1100 koobs@FreeBSD.org said
> On 4/03/2020 5:58 am, Chris wrote:
> > I'm dragging some code into the 21st century. I'm happy to
> > say the python37 AST now gives it a clean bill of health.
> > But I'm (currently) only able to build it by prepending
> > the python && python-version to the
> > #include <Python.h>
> > line.
> > USES= python:3.5+
> > doesn't seem to populate -I for my needs. If the user has
> > 3, or 4 versions it seems harder. Not to mention if malloc
> > option was added, which appends an m to ${PYTHON_SUFFIX}
> > How does everyone deal with this sort of thing?
> >
> > Thank you for all your time, and consideration.
> >
> > --Chris
> >
> >
>
> USES=localbase[:ldflags] or set them (CFLAGS+=, LDFLAGS+=) individually.
>
> If you have any other issues or need help, jump on #freebsd-python on
> freenode IRC
You're awesome koobs!
Your suggestion makes perfect sense.
I may have to start monitoring #freebsd-python
Thanks!
--Chris
FreeBSD 14.0-FUTURE #0.000 cray256
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?de1e40493e2bcb330c824762f30f7bd5>