Re: Pulling in python from a buildlink3.mk file

[Martijn van Buul <pino%dohd.org@localhost>]

* 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. 

tinkerbell(0):~% pkg_info -L libsigrokdecode
Information for libsigrokdecode-0.4.0nb20160123:

Files:
/usr/pkg/include/libsigrokdecode/libsigrokdecode.h
/usr/pkg/include/libsigrokdecode/version.h
/usr/pkg/lib/libsigrokdecode.la
/usr/pkg/lib/libsigrokdecode.a
/usr/pkg/lib/libsigrokdecode.so
/usr/pkg/lib/libsigrokdecode.so.2
/usr/pkg/lib/libsigrokdecode.so.2.0.0
/usr/pkg/lib/pkgconfig/libsigrokdecode.pc
/usr/pkg/share/libsigrokdecode/decoders/adns5020/__init__.py
/usr/pkg/share/libsigrokdecode/decoders/adns5020/pd.py
[... skip 125 .py files...]
/usr/pkg/share/libsigrokdecode/decoders/z80/__init__.py
/usr/pkg/share/libsigrokdecode/decoders/z80/pd.py
/usr/pkg/share/libsigrokdecode/decoders/z80/tables.py

tinkerbell(0):~% 

Personally, I feel that the entire package goes against the grain of how 
python is supposed to be used. You typically don't embed python in your
application, you bind your application to python instead :)

-- 
Martijn van Buul - pino%dohd.org@localhost