Project

General

Profile

Bug #431

cpplint from command line

Added by Tunnell, Christopher almost 12 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Code Management
Target version:
Start date:
30 April 2011
Due date:
% Done:

100%

Estimated time:
Workflow:

Description

The cpplint script seems to bounce around in where it's located. I think the requirement is that it can live anywhere but somebody who just set up MAUS needs to be able to run "cpplint.py test_file.cpp" if we're going to enforce this type of stuff.

So we don't keep making conflicting changes, how do we do this?

Also available in: Atom PDF