Bug #448
scons does not clean properly some changes
Status:
Closed
Priority:
Normal
Assignee:
Tunnell, Christopher
Category:
Build System
Target version:
Start date:
11 May 2011
Due date:
% Done:
100%
Estimated time:
Workflow:
Description
I don't know if this can be fixed - cpplint.py moved from being a built file to being a library. Because it was no longer a built file, scons didn't know it existed, didn't clean it from build/. Even scons -c didn't clean it up.
Maybe hard code a
rm build/*step? Would that be too gross? Anyway, that's why maus_per_commit_gcc was broken. It's fixed now for cpplint at least in the maus_per_commit_gcc build.
Related issues
Updated by Tunnell, Christopher over 12 years ago
- Target version changed from MAUS-v0.0.2 to Future MAUS release
Want me to add that command to the jenkins stuff you mean? And the -c as well?
Also: can we leave the version stuff at future MAUS release until it's closed and is going into a release? Makes my life easier.
Updated by Tunnell, Christopher over 12 years ago
So we want scons -c to clear out build, right? And that to happen automatically for the per commit jenkins test?
Updated by Tunnell, Christopher over 12 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
Applied in changeset r504.
Updated by Rogers, Chris over 12 years ago
- Target version changed from Future MAUS release to MAUS-v0.0.2