selinux/sepolgen/tests/Makefile

PYTHON ?= python

clean:
	rm -f *~ *.pyc
	rm -f parser.out parsetab.py
	rm -f out.txt
	rm -f module_compile_test.pp
	rm -f output

test:
	$(PYTHON) run-tests.py
Use $(PYTHON) instead of "python" in every Makefile This fixes the build with "make PYTHON=python2" on systems where python is python3. For PYLIBVER and PYTHONLIBDIR definitions, I tested Python 2.5, 2.6, 2.7, 3.3 and 3.4. For each of them, these commands print the expected result: python -c 'import sys;print("python%d.%d" % sys.version_info[0:2])'" python -c "from distutils.sysconfig import *;print(get_python_lib(1))" Acked-by: Steve Lawrence <slawrence@tresys.com> 2014-09-10 19:01:28 +00:00			`PYTHON ?= python`

initial import from svn trunk revision 2950 2008-08-19 19:30:36 +00:00			`clean:`
			`rm -f ~ .pyc`
			`rm -f parser.out parsetab.py`
			`rm -f out.txt`
			`rm -f module_compile_test.pp`
			`rm -f output`

			`test:`
Use $(PYTHON) instead of "python" in every Makefile This fixes the build with "make PYTHON=python2" on systems where python is python3. For PYLIBVER and PYTHONLIBDIR definitions, I tested Python 2.5, 2.6, 2.7, 3.3 and 3.4. For each of them, these commands print the expected result: python -c 'import sys;print("python%d.%d" % sys.version_info[0:2])'" python -c "from distutils.sysconfig import *;print(get_python_lib(1))" Acked-by: Steve Lawrence <slawrence@tresys.com> 2014-09-10 19:01:28 +00:00			`$(PYTHON) run-tests.py`