summaryrefslogtreecommitdiff
path: root/features/compile.feature
diff options
context:
space:
mode:
authorLuis Lavena <luislavena@gmail.com>2008-11-29 01:45:07 -0200
committerLuis Lavena <luislavena@gmail.com>2008-11-29 01:45:07 -0200
commitaa7166b8990e74bc2801742acbf3298522fd901d (patch)
tree48905a1d7bf72034fa829620a701afbbfffebffb /features/compile.feature
parenta5f63d597369e21038351899c17a8a446d527eba (diff)
downloadrake-compiler-aa7166b8990e74bc2801742acbf3298522fd901d.tar.gz
Only trigger step when 'gcc' or 'cl' compilers are executed
Steps should have less of this noise and more functionality. Candidates of refactoring and simplification on next version.
Diffstat (limited to 'features/compile.feature')
-rw-r--r--features/compile.feature2
1 files changed, 1 insertions, 1 deletions
diff --git a/features/compile.feature b/features/compile.feature
index 7954f31..2d2dc22 100644
--- a/features/compile.feature
+++ b/features/compile.feature
@@ -20,7 +20,7 @@ Feature: Compile C code into Ruby extensions.
And not changed any file since
When rake task 'compile' is invoked
Then rake task 'compile' succeeded
- And output of rake task 'compile' do not contain /extension_one/
+ And output of rake task 'compile' do not contain /gcc|cl/
Scenario: recompile extension when source is modified
Given a safe project directory