source: tests/Tesselations/trianglematcher.in@ 92d0e6

Action_Thermostats Adding_Graph_to_ChangeBondActions Adding_MD_integration_tests Adding_StructOpt_integration_tests AutomationFragmentation_failures Candidate_v1.6.1 ChemicalSpaceEvaluator Enhanced_StructuralOptimization Enhanced_StructuralOptimization_continued Exclude_Hydrogens_annealWithBondGraph Fix_Verbose_Codepatterns ForceAnnealing_with_BondGraph ForceAnnealing_with_BondGraph_continued ForceAnnealing_with_BondGraph_continued_betteresults ForceAnnealing_with_BondGraph_contraction-expansion Gui_displays_atomic_force_velocity JobMarket_RobustOnKillsSegFaults JobMarket_StableWorkerPool PythonUI_with_named_parameters Recreated_GuiChecks StoppableMakroAction TremoloParser_IncreasedPrecision
Last change on this file since 92d0e6 was 3532b7, checked in by Frederik Heber <heber@…>, 9 years ago

DISTFIX: adjacencymatcher and trianglematcher are check_PROGRAMS, not bin_...

  • as such they are not installed and hence .in files must not use AUTOTEST_PATH but topdir (top build directory).
  • also in GuiChecks, regresssion, and Tesselations tests TESTSUITE was made dependent on them but target check and installcheck only actually depend on the wrapper scripts (molecuilder, ...).
  • Property mode set to 100755
File size: 581 bytes
Line 
1#!/bin/sh
2#
3# wrapper for testing with trianglematcher
4
5. ../../atlocal
6
7if test ! -z ${valgrind}
8then
9G_SLICE=always-malloc G_DEBUG=gc-friendly \
10libtool --mode=execute \
11${valgrind} -v \
12--log-file=valgrind.log \
13--xml=yes \
14--xml-file=valgrind.err \
15--time-stamp=yes \
16--error-exitcode=255 \
17--leak-check=full \
18--leak-resolution=high \
19--num-callers=20 \
20--track-origins=yes \
21--show-reachable=yes \
22"${topdir}/src/Tesselation/TriangleMatcher/trianglematcher" \
23${1+"$@"}
24else
25"${topdir}/src/Tesselation/TriangleMatcher/trianglematcher" \
26${1+"$@"}
27fi
28
29status=$?
30
31exit $status
Note: See TracBrowser for help on using the repository browser.