summaryrefslogtreecommitdiffstats
path: root/build-scripts/test-unsigned-char
diff options
context:
space:
mode:
authorJay Berkenbilt <ejb@ql.org>2022-09-23 23:43:01 +0200
committerJay Berkenbilt <ejb@ql.org>2022-09-23 23:44:16 +0200
commit77111086eb38f6075fd2e8e4da74acc32719be02 (patch)
tree78e4a1d2250138d5a0f1a4e9b6a4c43aa7508d8b /build-scripts/test-unsigned-char
parenta085479ad9bd2a513018264a93db7aa8a27b8e06 (diff)
downloadqpdf-77111086eb38f6075fd2e8e4da74acc32719be02.tar.zst
Add code to CI to verify signed/unsigned char
Make sure that our attempt to test both signed and unsigned char is actually right.
Diffstat (limited to 'build-scripts/test-unsigned-char')
-rwxr-xr-xbuild-scripts/test-unsigned-char4
1 files changed, 4 insertions, 0 deletions
diff --git a/build-scripts/test-unsigned-char b/build-scripts/test-unsigned-char
index 840b517d..1f4c68d8 100755
--- a/build-scripts/test-unsigned-char
+++ b/build-scripts/test-unsigned-char
@@ -15,4 +15,8 @@ env CFLAGS="-funsigned-char" \
-DENABLE_QTC=1
cmake --build build -j$(nproc) -- -k
cd build
+# Make sure char is unsigned by default. ./build-linux verifies that
+# that build has char signed by default. That way we can be sure we
+# are testing both ways.
+./qpdf/test_char_sign | grep 'char is unsigned'
ctest --verbose