[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Do not distribute files in python_PYTHON primary?

From: Nate Bargmann
Subject: Do not distribute files in python_PYTHON primary?
Date: Mon, 19 Nov 2012 10:55:53 -0600
User-agent: Mutt/1.5.21 (2010-09-15)

The library project I am maintaining has various language bindings
generated by the Swig package.  Each of the language bindings are
enabled by an Automake conditional.  As there were various files being
generated no matter if a language binding was enabled or not, I've set
about trying to correct that behavior.

In the Python block the uses the python_PYTHON primary.
However, this seems to force the file listed with that primary to be a
distributed source file.  However, this file should not be generated
until the optional Python binding is built along with the rest of the
library.  Distributing it is incorrect in our case as the file is
useless without the built library.  However, not using the python_PYTHON
primary results in an unusable installation when the binding is built
and installed (or I'd have to do that manually, I suppose).

Is there a way to use the python_PYTHON primary but not distribute the
file(s) in its list?

I can supply the fragments if needed.

- Nate


"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]