summaryrefslogtreecommitdiff
path: root/src/examples/eio/Makefile.am
diff options
context:
space:
mode:
authorStefan Schmidt <s.schmidt@samsung.com>2015-02-25 14:05:42 +0100
committerStefan Schmidt <s.schmidt@samsung.com>2015-02-25 16:43:35 +0100
commitc5879dab4d0a1e6d0b6e0510e28ddd933ec207fb (patch)
tree2f2799abda669923bac4a4b872a53c7a62ba3054 /src/examples/eio/Makefile.am
parent1e83761810e337eac94bb94f39053f511b0a1083 (diff)
build: Unify use of $(MKDIR_P) for creating a dir within the build system
While we used different variation of mkdir -p all over we also had spots where we did not use the option. This is one step in trying to make our build system ready for parallel install. Using something like -j 10 even for the install should help to speed up our jenkins jobs as well as distcheck.
Diffstat (limited to 'src/examples/eio/Makefile.am')
-rw-r--r--src/examples/eio/Makefile.am2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/examples/eio/Makefile.am b/src/examples/eio/Makefile.am
index ea34e81384..50d6dbc108 100644
--- a/src/examples/eio/Makefile.am
+++ b/src/examples/eio/Makefile.am
@@ -49,7 +49,7 @@ clean-local:
49 rm -f $(EXTRA_PROGRAMS) 49 rm -f $(EXTRA_PROGRAMS)
50 50
51install-examples: 51install-examples:
52 mkdir -p $(datadir)/eio/examples 52 $(MKDIR_P) $(datadir)/eio/examples
53 cd $(srcdir) && $(install_sh_DATA) -c $(SRCS) $(DATA_FILES) $(datadir)/eio/examples 53 cd $(srcdir) && $(install_sh_DATA) -c $(SRCS) $(DATA_FILES) $(datadir)/eio/examples
54 54
55uninstall-local: 55uninstall-local: