add RIOT tests to dist and make sure Makefiles are not excluded by .gitignore

.gitignore

@@ -191,5 +191,5 @@ wrapper/CSharp/x64/
 *.vscode
 
 # RIOT_OS workspace directories:
-RIOT_Make/*/bin/*
+RIOT_Make/*/bin/
 RIOT_Make/*/*.c

Makefile.am

@@ -105,6 +105,7 @@ include mcapi/zlib.X/nbproject/include.am
 include tirtos/include.am
 include scripts/include.am
 include IDE/include.am
+include RIOT_Make/include.am
 
 if USE_VALGRIND
 TESTS_ENVIRONMENT=./valgrind-error.sh

RIOT_Make/benchmark/Makefile.benchmark

@@ -0,0 +1,29 @@
+# name of your application
+APPLICATION = wolfbenchmark
+
+# If no BOARD is found in the environment, use this default:
+BOARD ?= native
+
+# This has to be the absolute path to the RIOT base directory:
+RIOTBASE ?= $(CURDIR)/../../../../
+
+# Comment this out to disable code in RIOT that does safety checking
+# which is not needed in a production environment but helps in the
+# development process:
+CFLAGS += -DDEVELHELP
+
+# Change this to 0 show compiler invocation lines by default:
+QUIET ?= 1
+
+# bindist specific stuff:
+#
+# build and use module "abc".
+# use BINARY_DIRS instead of DIRS
+#BINARY_DIRS += wolfssl/src
+INCLUDES += -I$(RIOTBASE)/examples/wolfssl
+
+# list of files to include in binary distribution
+# "bin/$(BOARD)/$(APPLICATION).elf" will automatically be added
+DIST_FILES += Makefile
+
+include $(RIOTBASE)/Makefile.include

RIOT_Make/benchmark/include.am

@@ -0,0 +1,7 @@
+# vim:ft=automake
+# included from Top Level Makefile.am
+# All paths should be given relative to the root
+
+EXTRA_DIST+= RIOT_Make/benchmark/README
+EXTRA_DIST+= RIOT_Make/benchmark/Makefile.benchmark
+EXTRA_DIST+= RIOT_Make/benchmark/wolf-build-and-run-test.sh

RIOT_Make/benchmark/wolf-build-and-run-test.sh

@@ -2,6 +2,7 @@
 
 wolf_riot_setup () {
 #copy the test sources here
+cp Makefile.benchmark Makefile
 cp ../../wolfcrypt/benchmark/benchmark.c ./
 
 cp ../../wolfcrypt/src/*.c ./
@@ -15,6 +16,7 @@ wolf_riot_cleanup () {
     #leave this line in for testing. Comment it out when you want to build
     # a .elf for flashing to a device
     make clean &> /dev/null
+    rm Makefile
 }
 trap wolf_riot_cleanup INT TERM
 

RIOT_Make/include.am

@@ -0,0 +1,10 @@
+# vim:ft=automake
+# included from Top Level Makefile.am
+# All paths should be given relative to the root
+
+include RIOT_Make/benchmark/include.am
+include RIOT_Make/testsuite/include.am
+include RIOT_Make/wolfcrypt-test/include.am
+
+EXTRA_DIST+= RIOT_Make/benchmark RIOT_Make/testsuite RIOT_Make/wolfcrypt-test \
+             RIOT_Make/test-all.sh RIOT_Make/README

RIOT_Make/testsuite/Makefile.testsuite

@@ -0,0 +1,29 @@
+# name of your application
+APPLICATION = wolftestsuite
+
+# If no BOARD is found in the environment, use this default:
+BOARD ?= native
+
+# This has to be the absolute path to the RIOT base directory:
+RIOTBASE ?= $(CURDIR)/../../../../
+
+# Comment this out to disable code in RIOT that does safety checking
+# which is not needed in a production environment but helps in the
+# development process:
+CFLAGS += -DDEVELHELP
+
+# Change this to 0 show compiler invocation lines by default:
+QUIET ?= 1
+
+# bindist specific stuff:
+#
+# build and use module "abc".
+# use BINARY_DIRS instead of DIRS
+#BINARY_DIRS += wolfssl/src
+INCLUDES += -I$(RIOTBASE)/examples/wolfssl
+
+# list of files to include in binary distribution
+# "bin/$(BOARD)/$(APPLICATION).elf" will automatically be added
+DIST_FILES += Makefile
+
+include $(RIOTBASE)/Makefile.include

RIOT_Make/testsuite/include.am

@@ -0,0 +1,7 @@
+# vim:ft=automake
+# included from Top Level Makefile.am
+# All paths should be given relative to the root
+
+EXTRA_DIST+= RIOT_Make/testsuite/README
+EXTRA_DIST+= RIOT_Make/testsuite/Makefile.testsuite
+EXTRA_DIST+= RIOT_Make/testsuite/wolf-build-and-run-test.sh

RIOT_Make/testsuite/wolf-build-and-run-test.sh

@@ -2,6 +2,7 @@
 
 wolf_riot_setup () {
 #copy the test sources here
+cp Makefile.testsuite Makefile
 cp ../../wolfcrypt/test/test.c ./
 cp ../../examples/server/server.c ./
 cp ../../examples/client/client.c ./
@@ -21,6 +22,7 @@ wolf_riot_cleanup () {
     #leave this line in for testing. Comment it out when you want to build
     # a .elf for flashing to a device
     make clean &> /dev/null
+    rm Makefile
 }
 trap wolf_riot_cleanup INT TERM
 

RIOT_Make/wolfcrypt-test/Makefile.wolfcrypttest

@@ -0,0 +1,29 @@
+# name of your application
+APPLICATION = testwolfcrypt
+
+# If no BOARD is found in the environment, use this default:
+BOARD ?= native
+
+# This has to be the absolute path to the RIOT base directory:
+RIOTBASE ?= $(CURDIR)/../../../../
+
+# Comment this out to disable code in RIOT that does safety checking
+# which is not needed in a production environment but helps in the
+# development process:
+CFLAGS += -DDEVELHELP
+
+# Change this to 0 show compiler invocation lines by default:
+QUIET ?= 1
+
+# bindist specific stuff:
+#
+# build and use module "abc".
+# use BINARY_DIRS instead of DIRS
+#BINARY_DIRS += wolfssl/src
+INCLUDES += -I$(RIOTBASE)/examples/wolfssl
+
+# list of files to include in binary distribution
+# "bin/$(BOARD)/$(APPLICATION).elf" will automatically be added
+DIST_FILES += Makefile
+
+include $(RIOTBASE)/Makefile.include

RIOT_Make/wolfcrypt-test/include.am

@@ -0,0 +1,7 @@
+# vim:ft=automake
+# included from Top Level Makefile.am
+# All paths should be given relative to the root
+
+EXTRA_DIST+= RIOT_Make/wolfcrypt-test/README
+EXTRA_DIST+= RIOT_Make/wolfcrypt-test/Makefile.wolfcrypttest
+EXTRA_DIST+= RIOT_Make/wolfcrypt-test/wolf-build-and-run-test.sh

RIOT_Make/wolfcrypt-test/wolf-build-and-run-test.sh

@@ -1,6 +1,7 @@
 #!/bin/sh
 
 wolf_riot_setup () {
+    cp Makefile.wolfcrypttest Makefile
     #copy the test sources here
     cp ../../wolfcrypt/test/*.c ./
 
@@ -14,6 +15,7 @@ wolf_riot_cleanup () {
     #leave this line in for testing. Comment it out when you want to build
     # a .elf for flashing to a device
     make clean &> /dev/null
+    rm Makefile
 }
 
 BACKUPCFLAGS=${CFLAGS}