third_party_libnl/python
Michał Górny 425d3d6661 Use paths relative to srcdir in setup.py.
Currently, setup.py is created by configure in builddir while source
files (.py and .i) reside in srcdir. Adjust paths in setup.py
appropriately to make it possible to perform an out-of-source build.

This is far from perfect but it mostly works. Python files are copied
from srcdir, and swig *.i files are read from there. However, swig
output files are created in srcdir rather than builddir, and distutils
copies '..' literally when constructing '.o' paths. As a result,
'../python/foo.i' would end up being compiled to
'build/temp*/../python/foo.i'.

The alternative would be to copy '*.i' files to builddir before
proceeding with the build, either in Makefile or through creating
additional distutils command.
2014-05-25 12:51:32 +02:00
..
doc python: Include all files in distribution 2013-11-06 10:28:37 +01:00
examples python: Include all files in distribution 2013-11-06 10:28:37 +01:00
netlink python: fix wrongly passing argument to function in ObjIterator.next() 2014-04-09 09:22:47 +02:00
tests python: Include all files in distribution 2013-11-06 10:28:37 +01:00
.gitignore python: Include python/ in distribution and provide a README on how to build & install 2011-08-12 10:45:47 +02:00
Makefile.am python: Include all files in distribution 2013-11-06 10:28:37 +01:00
README python: Include python/ in distribution and provide a README on how to build & install 2011-08-12 10:45:47 +02:00
setup.py.in Use paths relative to srcdir in setup.py. 2014-05-25 12:51:32 +02:00

***************************************************************************

NOTE: The python wrapper is experimental and may or may not work.

***************************************************************************

For the brave:

  (requires an installed libnl)
  - $ python ./setup.py build
  - $ sudo python ./setup.py install