Rule of thumb is: any Python file that is greater than 100kb
(or adds a dependency with which it adds more than 100 kb)
should be a pretty useful/commonly used lib to stay in `python-light`.
An example, is the Python IO lib, which summarized (Python source +
binary module) is over 200kb.
Also moved some files that should have been put into previously
existing packages before, and re-organized the packages a bit.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
Update to r182-experimental (071481e626) broke YUV
capture mode in input_uvc. This patch fixes it.
Tested on ar71xx with Logitech C170
Signed-off-by: Mantas Pucka <mantas@8devices.com>
input_uvc was broken with new kernel update
patch source: https://github.com/oliv3r/mjpg-streamer
Tested on ar71xx with Logitech C170
Signed-off-by: Mantas Pucka <mantas@8devices.com>
Seems removing the PyPackage rule and/or adding dummy install rule
causes some issues inside the build-system, where the libpython2.7.so.1.0
is not seen by packages that depend on python.
Even though that libpython2.7.so.1.0 file is installed properly by `python-base`.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
Calling `PyPackage` will install some default install rules for
python packages that are not required for the `python` package specifically
are not required.
That will lead to some conflicts with `python-light` because the
`/usr/lib/python2.7/site-packages` folder (+contents) will be
available in both packages.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
The pkgconfig file is generated at make-time, leading to absolute /usr/include & /usr/lib search paths.
The patch lets autoconf handle pkgconfig file subst, like other packages do.
Signed-off-by: Nicolas Thill <nico@openwrt.org>
When cross-compiling, we do not need to add runtime lib dirs.
Also, the cross compilers that are used on OpenWRT do not support
the '-R' option, which causes build failures.
These build failures existed before, but were not noticed,
because it fails only on some setups.
This is because Python's `setup.py` does a lot of voo-doo
automagic that needs handling for some cross-compilation cases.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>