Project

General

Profile

Bug #431

cpplint from command line

Added by Tunnell, Christopher over 11 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?

#1

Updated by Tunnell, Christopher over 11 years ago

plus chmod +x ./tests/style/cpplint.py

#2

Updated by Rogers, Chris over 11 years ago

Well, you asked me to move it so I moved it! I don't care where it goes. It needs to be in pythonpath for the test script to work.

#3

Updated by Rogers, Chris over 11 years ago

nb I would prefer to call cpplint like

python cpplint.py <filename>

At the moment I think it has

#! /usr/bin/python2.4

at the top, don't know what happens if you don't have python 2.4 installed but it probably doesn't work.

#4

Updated by Tunnell, Christopher over 11 years ago

  • Target version changed from MAUS-v0.0.1 to Future MAUS release
#5

Updated by Rogers, Chris over 11 years ago

Okay, cpplint.py lives in third_party/install/lib; can be called from the command line using

python ${MAUS_ROOT_DIR}/third_party/install/lib/cpplint.py <filename1> <filename2>

Added to Coding_style

#6

Updated by Rogers, Chris over 11 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100
#7

Updated by Tunnell, Christopher over 11 years ago

  • Target version changed from Future MAUS release to MAUS-v0.0.1

Also available in: Atom PDF