Makefile: Avoid shell expansion, for Windows users.

Reported by Steve.
pinard · May 9, 2012 · 0b0080f · 0b0080f
1 parent 0e80f95
commit 0b0080f
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/Makefile b/Makefile
@@ -10,7 +10,7 @@ PYSETUP = $(PYTHON) setup.py
 PPPP = $(PYTHON) pppp -C ppppconfig.py
 
 all:
-	$(PPPP) *.in contrib tests
+	$(PPPP) Pymacs.py.in pppp.rst.in pymacs.el.in pymacs.rst.in contrib tests
 	$(PYSETUP) --quiet build
 
 check: clean-debug
@@ -21,7 +21,7 @@ check: clean-debug
 	  $(PYTHON) pytest -f t $(TEST)
 
 install:
-	$(PPPP) *.in Pymacs.py.in contrib tests
+	$(PPPP) Pymacs.py.in pppp.rst.in pymacs.el.in pymacs.rst.in contrib tests
 	$(PYSETUP) install
 
 clean: clean-debug

diff --git a/pymacs.rst.in b/pymacs.rst.in
@@ -266,8 +266,8 @@ be installed in turn.  Always start with the Python file.
   read the ``Makefile`` file and emulate what ``make install`` does,
   maybe something like this::
 
-    python pppp -C ppppconfig.py pppp.rst.in pymacs.el.in \
-      pymacs.rst.in Pymacs.py.in contrib tests
+    python pppp -C ppppconfig.py \
+      Pymacs.py.in pppp.rst.in pymacs.el.in pymacs.rst.in contrib tests
     python setup.py install
 
   Without ``make install``, you might also have to combine the two first