Skip to content
Snippets Groups Projects
Commit 1b39754b authored by Florian Schmaus's avatar Florian Schmaus
Browse files

[Makefile] fix smoke-test/static-analysis target

This adds yet another target "smoke-test-suite", which just runs all
tests in the 'smoke' test suite. The static-analysis target was
changed to include *all* static analysis thingies we have, even 'doc'
as Doxygen does also do some checks that the documentation is
"correct".

The smoke-test target is also kept, as it allows developers to simply
run all smoke tests. Furthermore, this adds some missing PHONY
declarations in the Makefile.

The gitlab-ci now runs the smoke-test-suite and static-analysis
targets in two different jobs. Previously the smoke-test would also
run the static-analysis target, which was not intended.
parent 0d91eae7
No related branches found
No related tags found
No related merge requests found
...@@ -32,9 +32,9 @@ stages: ...@@ -32,9 +32,9 @@ stages:
- smoke-test - smoke-test
- test - test
smoke-test: smoke-test-suite:
stage: smoke-test stage: smoke-test
script: make smoke-test script: make smoke-test-suite
static-analysis-with-emper-io: static-analysis-with-emper-io:
stage: smoke-test stage: smoke-test
......
...@@ -41,12 +41,17 @@ else ...@@ -41,12 +41,17 @@ else
$(warning old mesion version $(MESON_VERSION) detected, meson >= 0.52 required for clang-tidy) $(warning old mesion version $(MESON_VERSION) detected, meson >= 0.52 required for clang-tidy)
endif endif
static-analysis: all .PHONY: static-analysis
static-analysis: all check-format check-license doc
$(NINJA) -C build $(STATIC_ANALYSIS_NINJA_TARGETS) $(NINJA) -C build $(STATIC_ANALYSIS_NINJA_TARGETS)
smoke-test: all check-format check-license doc static-analysis .PHONY: smoke-test-suite
smoke-test-suite: all
cd build && meson test --suite smoke cd build && meson test --suite smoke
.PHONY: smoke-test
smoke-test: smoke-test-suite static-analysis
TEST_NINJA_TARGETS += test TEST_NINJA_TARGETS += test
doc: all doc: all
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment