tpm2-tss: Files ignored by “make dist”
“make dist” ignores:
lib/tss2-esys.def
lib/tss2-mu.def
lib/tss2-tcti-mssim.def
lib/tss2-sys.def
lib/tss2-tcti-tbs.def
.gitattributes
.appveyor.yml
doc/TSS block diagram.png
Dockerfile
.dockerignore
bootstrap
src/tss2-sys/tss2-sys.vcxproj
src/tss2-tcti/tcti-tbs.c
src/tss2-tcti/tss2-tcti-tbs.vcxproj.filters
src/tss2-tcti/tss2-tcti-tbs.vcxproj
src/tss2-tcti/tss2-tcti-mssim.sln
src/tss2-tcti/tcti-tbs.h
src/tss2-tcti/tss2-tcti-mssim.vcxproj.filters
src/tss2-tcti/tss2-tcti-mssim.vcxproj
src/tss2-tcti/tss2-tcti-tbs.sln
src/tss2-esys/tss2-esys.vcxproj.filters
src/tss2-esys/tss2-esys.vcxproj
src/tss2-esys/tss2-esys.sln
src/tss2-mu/tss2-mu.vcxproj
MAINTAINERS
include/tss2/tss2_tcti_tbs.h
script/gen_fuzz.py
script/fuzz-log-compiler.sh
tpm2-tss.sln
.gitignore
.travis.yml
Consider tweaking the tests to first call “make dist”, unpack and call the tests on the unpacked code.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 18 (16 by maintainers)
IMHO, fuzz-testing is nothing to be done from the tar-ball. Thus, we can ignore it for distchecks…
If
bootstrapis not in the dist tarball, then it will not be possible to build the fuzzing tests from the unpacked tarball. In turnscript/gen_fuzz.pyandscript/fuzz-log-compiler.shcan be kept outside.We could even use this to speed up the process. If we remove make dist from all other runs and add a new run for building+testing from tar-ball, then we should be faster in the end. (multi-thredding… 😃 )