openscad/tests/echotest

#!/usr/bin/env python

import re, sys, subprocess

result = subprocess.check_output([sys.argv[2], sys.argv[1], '-o', 'null'], stderr=subprocess.STDOUT)

result = re.sub(r'-?[0-9].[0-9]*e-[0-9]{2,}', '0', result)

open(sys.argv[3], 'w').write(result)
replace echotest and dumptest with python scripts this solves problems of sed compatibility on different platoforms. also, the openscad binary to use is now passed in from the ctest script. 2013-06-28 12:50:48 +04:00			`#!/usr/bin/env python`
use openscad as a replacement for dumptest and echotest the echotest and dumptest still contain hacks to keep the delta to the original unit tests minimal; possibly, some of these changes will make it into the openscad program, at which time they can go away from there. 2013-06-24 20:41:50 +04:00
replace echotest and dumptest with python scripts this solves problems of sed compatibility on different platoforms. also, the openscad binary to use is now passed in from the ctest script. 2013-06-28 12:50:48 +04:00			`import re, sys, subprocess`
use openscad as a replacement for dumptest and echotest the echotest and dumptest still contain hacks to keep the delta to the original unit tests minimal; possibly, some of these changes will make it into the openscad program, at which time they can go away from there. 2013-06-24 20:41:50 +04:00
replace echotest and dumptest with python scripts this solves problems of sed compatibility on different platoforms. also, the openscad binary to use is now passed in from the ctest script. 2013-06-28 12:50:48 +04:00			`result = subprocess.check_output([sys.argv[2], sys.argv[1], '-o', 'null'], stderr=subprocess.STDOUT)`

			`result = re.sub(r'-?[0-9].[0-9]*e-[0-9]{2,}', '0', result)`

			`open(sys.argv[3], 'w').write(result)`