From 244f86a9cdf19904169456c234a2752f125dd427 Mon Sep 17 00:00:00 2001 From: Christopher Vogt Date: Sun, 12 Mar 2017 01:47:57 -0500 Subject: revamp loop feature now CBT and builds pass their file names to the current build via the context. The build then simply blocks until any file changes. Then it returns with a special exit code, which the bash script picks up and restarts CBT. Thats works well for looping over project files. It works less well for looping over builds and CBT itself. For this a build has to success once, so that the .cbt-loop.tmp file exists. Then looping works for cbt and builds, but the file list is not updated in case of compile errors, etc. Fixes - https://github.com/cvogt/cbt/issues/406 - https://github.com/cvogt/cbt/issues/405 - https://github.com/cvogt/cbt/issues/202 - https://github.com/cvogt/cbt/issues/50 - https://github.com/cvogt/cbt/issues/22 We should improve for 1.0 in https://github.com/cvogt/cbt/issues/419 to handle looping over build files and cbt itself smarter. --- test/test.scala | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'test') diff --git a/test/test.scala b/test/test.scala index 45315ce..4d1d7fb 100644 --- a/test/test.scala +++ b/test/test.scala @@ -133,7 +133,8 @@ object Main{ cbtHome, cbtHome, cbtHome ++ "/compatibilityTarget", - null + null, + Array() ) val b = new BasicBuild(noContext){ -- cgit v1.2.3