2 # This is one of a set of test that generate checksums after files are
3 # created. Generally a bitmap if first produced by a program such as sym_strip,
4 # rect_in_rect, rect_cen_in_rect, circ_in_circ, circ_in_rect,
5 # generate_coupler_bitmap etc.
7 # In a few cases, the checksum is performed on a file that is
8 # supplied with the package, rather than one that is
11 # The checksum of the bitmaps generated is compared to what is known to be
12 # the correct checksum using a program 'mymd5sum' which is a cut-down version of
13 # the normal md5 or md5sum command. It does not print the filename
14 # to stdout, as the normal version does.
16 # I have tried to test these checksums on as many systems as possible and
17 # know all tests pass on all systems I have checked this on. Typically the
18 # systems have been mainly Suns, but running various operating systems.
19 # such as Solaris 9, NetBSD, Solaris 2.5, Linux but also a PC running
20 # rehat Linux and a Dec Alpha. Any failure probably indicates a
21 # program bug, so PLEASE PLEASE let me know about it!!
22 # Dr. David Kirkby, drkirkby@ntlworld.com
24 $top_builddir/src/create_bmp_for_stripline_coupler -vv -b 16 1 1 1 1.0 $top_builddir/tmp/test_stripline_coupler.bmp > $top_builddir/tmp/test_stripline_coupler.bmp.pre-atlc.txt
25 rm $top_builddir/tmp/test_stripline_coupler.bmp.pre-atlc.txt
27 touch $top_builddir/tmp/test_stripline_coupler.bmp
28 MD5SUM=`$top_builddir/tools/src/mymd5sum $top_builddir/tmp/test_stripline_coupler.bmp`
29 if [ $MD5SUM = 70e1fd121d8437cebd18916090f6b7d0 ]; then
30 echo "PASSED:" $0 >> tests.log
33 echo "FAILED:" $0 >> tests.log