Jonas Sølvhøj wrote:
Well, msp430-pyjtag isn't the name of a binary. It's the name of the
package. The tool is called pyJTAG at
http://mspgcc.sourceforge.net/tools.html, so I think msp430-pyjtag is
the right name for the package.
thats fine of course.
The tool itself is called jtag.py and is
installed in /usr/bin. Maybe it should be renamed to msp430-jtag(.py?),
but then I think the files in cvs should be renamed too (eg.
pyjtag/jtag.py should be pyjtag/msp430-jtag.py).
yeah...
but as its a python source file, i'd like to keep the .py ending. files
witout ending are especialy nasty on windows. and on windows i have to
build an exe anyway as you cant make scripts executable (at least not in
an usable way).
i think the name jtag.py isnt a problem itself, but as you say the docs
could be changed.
You are right that the same tool shouldn't have different names, but I
think it's allready the case. The documentation (pyjtag/readme.txt) use
the name jtag.py in it's examples.
maybe i should refer to msp430-jtag in the docs and add a section about
installing and document there that jtag.py should be installed as
/usr/local/bin/msp430-jtag on un*x.
as i mentioned before an "install" target in the makefile would be best
anyway...
chris
