Bug #431
cpplint from command line
Added by Tunnell, Christopher almost 12 years ago.
Updated over 11 years ago.
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?
plus chmod +x ./tests/style/cpplint.py
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.
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.
- Target version changed from MAUS-v0.0.1 to Future MAUS release
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
- Status changed from Open to Closed
- % Done changed from 0 to 100
- Target version changed from Future MAUS release to MAUS-v0.0.1
Also available in: Atom
PDF
