appveyor: Work around incorrect "find" invocation

test_all_fex.sh now accepts an optional second parameter that
specifies the find executable to use. Without explicitly passing
it, AppVeyor would invoke the wrong one (Windows' own find.exe).
Signed-off-by: Bernhard Nortmann <bernhard.nortmann@web.de>

appveyor.yml

@@ -18,7 +18,7 @@ build_script:
   - cmd: mingw32-make misc
 
 test_script:
-  - cmd: mingw32-make -C tests/ check_all_fex
+  - cmd: mingw32-make -C tests/ check_all_fex FIND=/bin/find
 
 after_test:
   - cmd: .appveyor/package-artifacts.cmd

tests/Makefile

@@ -9,7 +9,7 @@ check: check_all_fex coverage
 
 # Conversion cycle (.fex -> .bin -> .fex) test for all sunxi-boards
 check_all_fex: $(BOARDS_DIR)/README unify-fex
-	./test_all_fex.sh $(BOARDS_DIR)
+	./test_all_fex.sh $(BOARDS_DIR) $(FIND)
 
 coverage:
 	# Usage help / invocation with no args

tests/test_all_fex.sh

 #!/bin/sh
 FEXFILES=fexfiles.lst
-find $1 -name '*.fex' > ${FEXFILES}
+if test -z $2; then
+	FIND=find
+else
+	FIND=$2
+fi
+${FIND} $1 -name '*.fex' > ${FEXFILES}
 while read fex; do
 	./fextest.sh ${fex} || exit
 done <${FEXFILES}