File: Makefile.am

package info (click to toggle)
systemtap 3.1-2
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 32,860 kB
  • ctags: 12,513
  • sloc: cpp: 58,610; ansic: 58,189; exp: 37,322; sh: 10,633; xml: 7,771; perl: 2,252; python: 2,066; tcl: 1,305; makefile: 969; lisp: 105; java: 100; awk: 94; asm: 91; sed: 16
file content (67 lines) | stat: -rw-r--r-- 2,296 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
# Makefile.am --- automake input file

AUTOMAKE_OPTIONS = subdir-objects

# Note that we have to use 'abs_builddir' here since we change
# directories back to the source directory when building the python
# extension.
AM_CPPFLAGS = -I$(srcdir)/../includes
AM_CPPFLAGS += -I$(abs_builddir)/../includes/sys

# Any script in the following variable will get byte-compiled at
# install time.
pkglibexecpython_PYTHON =

pkglibexecpython_DATA =

pkglibexecpythondir = $(pkglibexecdir)/python

if HAVE_PYTHON_PROBES

# Why aren't we putting stap-resolve-module-function.py into
# pkglibexecpython_PYTHON? stap-resolve-module-function.py is a
# python script, but it will be run by the translator as either a
# python version 2 or python version 3 script. So, it doesn't need to
# be executable (since we'll be calling "python
# stap-resolve-module-function.py ARGS" or "python3
# stap-resolve-module-function.y ARGS."
pkglibexecpython_DATA += stap-resolve-module-function.py

all-local:
if HAVE_PYTHON2_PROBES
	(cd $(srcdir); CFLAGS="$(AM_CPPFLAGS)" $(PYTHON) setup.py build \
         --build-base $(shell readlink -f $(builddir))/py2build \
         --verbose)
endif
if HAVE_PYTHON3_PROBES
	(cd $(srcdir); CFLAGS="$(AM_CPPFLAGS)" $(PYTHON3) setup.py build \
         --build-base $(shell readlink -f $(builddir))/py3build \
         --verbose)
endif


# Note that we're rebuilding here, then installing. This is necessary
# since only the build command has the '--build-base' directory option
# and we need to keep separate build directories for python 2 and 3.
install-exec-local:
if HAVE_PYTHON2_PROBES
	(cd $(srcdir); CFLAGS="$(AM_CPPFLAGS)" $(PYTHON) setup.py build \
         --build-base $(shell readlink -f $(builddir))/py2build \
	 install --prefix $(DESTDIR)$(prefix) \
	 --single-version-externally-managed \
	 --record $(shell readlink -f $(builddir))/py2build/install_files.txt \
         --verbose)
endif
if HAVE_PYTHON3_PROBES
	(cd $(srcdir); CFLAGS="$(AM_CPPFLAGS)" $(PYTHON3) setup.py build \
         --build-base $(shell readlink -f $(builddir))/py3build \
	 install --prefix $(DESTDIR)$(prefix) \
	 --single-version-externally-managed \
	 --record $(shell readlink -f $(builddir))/py3build/install_files.txt \
         --verbose)
endif

clean-local:
	rm -rf py2build py3build

endif