library porting question - optional python bindings

Fernando Herrero Carrón elferdo at
Tue Mar 1 06:59:40 UTC 2016

El 1 mar. 2016 3:38 a. m., "Chris Inacio" <nacho319 at> escribió:
> All,
> I'm trying to build a port definition for a library/application that can
> optionally include Python bindings.  The library/application generally
> depends on other C libraries to exist (ZMQ v3, Protobufs-C) and if you
> enable Python support, then you need a Python interpreter plus
> Python-protobufs & python zmq.
> Putting an OPTION of Python in the port file is easy.  Including the
> optional Python dependencies (and presumably targets - but I'm not that
> yet) seems to be a lot more complicated.  I haven't found anything that
> would tell me how I'm supposed to do that.  I have found that I'm supposed
> to add pyXX prefixes to the python targets.
> Does anyone know of a similar application/library that I can go look at?
> Is there any documentation on how to solve this?
> thanks,
> Chris Inacio
> _______________________________________________
> freebsd-ports at mailing list
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at"

multimedia/ffmpeg will optionally include ports providing libraries. There
does not seem any implemented in an interpreted language, though I vaguely
remember one option pulling in ruby (probably by transition).

The idea is that you can depend on a specific file and the port that
provides it with the syntax: file_to_depend_on:providing_port.

I hope that helps.


More information about the freebsd-ports mailing list