Debian Automated Code Analysis

checkbashisms analysis of libsyncml_0.5.4-2.dsc

possible bashism in ./tests/coverage.sh.cmake line 22 (should be 'b = a'):
if [ "$RESULT" == "0" ]; then
possible bashism in ./tests/coverage.sh.cmake line 28 (should be 'b = a'):
if [ "$RESULT" == "0" ]; then
possible bashism in ./tests/coverage.sh.cmake line 40 (should be >word 2>&1):
genhtml --legend -t "$TITLE" -o ${CMAKE_BINARY_DIR}/coverage/html/$TITLE ${CMAKE_BINARY_DIR}/coverage/$TITLE.info &> /dev/null
possible bashism in ./tests/coverage.sh.cmake line 59 (echo -e):
echo -e "\nTroubleshooting:\n If the Code Coverage number is quite low (less then 51%):"
possible bashism in ./tests/coverage.sh.cmake line 60 (echo -e):
echo -e "\t-Did you run any unit tests before $0?"
possible bashism in ./tests/coverage.sh.cmake line 61 (echo -e):
echo -e "\t-Did you build with enable_profiling=1?"
possible bashism in ./tests/coverage.sh.cmake line 62 (echo -e):
echo -e "\t-Run ALL available unit tests!"
possible bashism in ./tests/coverage.sh.cmake line 63 (echo -e):
echo -e "\t-Check if testcases in unit test are disabled!"
possible bashism in ./tests/coverage.sh.cmake line 64 (echo -e):
echo -e "\t-Fix unit tests and their test cases!"
possible bashism in ./tests/coverage.sh.cmake line 65 (echo -e):
echo -e "\t-Write new and more test cases!"

This report was generated on Thu, 16 Dec 2010 17:38:32 +0000, based on results by checkbashisms 2.10.65git5