From 0708d07f905687e38d4b2544117eeccbcda9d539 Mon Sep 17 00:00:00 2001
From: "Kartik K. Agaram" <vc@akkartik.com>
Date: Wed, 31 Aug 2016 13:19:16 -0700
Subject: 3287 - drop hacky implicit meaning of CXXFLAGS

Now that we have a new build system we shouldn't need to run unoptimized
just to save time. (Though that's not strictly true; if a change
modifies .build/mu_0.cc which is twice as large as later compilation
units, dropping -O3 shaves 10s off the time for an incremental build.)

Since we don't need to run unoptimized anymore, let's just explicitly
ask for --test-only-app when we need it.
---
 mu | 10 ----------
 1 file changed, 10 deletions(-)

(limited to 'mu')

diff --git a/mu b/mu
index 57590f88..7d82e32a 100755
--- a/mu
+++ b/mu
@@ -5,15 +5,6 @@
 # show make output only if something needs doing
 make -q || make >&2 || exit 1
 
-# Little bit of cleverness: If I'm setting flags at the commandline I'm often
-# disabling optimizations. In that case don't run all tests if I load any app
-# files.
-# Might be too clever..
-if [[ $CXXFLAGS && $# -gt 0 && $1 != '--help' ]]  # latter two conditions are to continue printing the help message
-then
-  FLAGS=--test-only-app
-fi
-
 ./mu_bin $FLAGS "$@"
 
 # Scenarios considered:
@@ -21,4 +12,3 @@ fi
 #   mu --help
 #   mu test
 #   mu test file1.mu
-#   CXXFLAGS=-g mu test file1.mu  # run only tests in file1.mu
-- 
cgit 1.4.1-2-gfad0