[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Pulling in python from a buildlink3.mk file
On Tue, Jan 26, 2016 at 07:37:58AM +0000, Martijn van Buul wrote:
> * Thomas Klausner:
> > Btw, buildlink3.mk files are not appropriate for (most) python
> > packages because they don't installed header files and libraries that
> > are looked for with a compiler.
> I'm open to suggestions, but this is an oddball python package. It's
> not an egg, it's not a python binding for an existing C library; it's a
> C library which happens to use python internally as an extension
> language. So it *does* ship a headerfile, a shared library and a pkg-config
> file. Along with a bunch of python files, but that's almost an
> implementation detail. If it was rewritten to use lua (for example),
> that wouldn't change the API.
In that case, don't mess with the Python version?
Main Index |
Thread Index |