On Sat, 2004-02-28 at 17:41, Chris Liechti wrote: > > All you have to do is to use the emerge command: > > emerge msp430-binutils msp430-gcc msp430-libc msp430-pyjtag > > nice. > > i havent looked at your script, i dont use gentoo myself, but i'd like > to ask how did you name the pyjtag tool. the binary should be named > msp430-jtag (similar for pybsl->msp430-bsl) because that's the names all > the examples refer to and the windows binaries have that name too.
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. 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). 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. > does it make sense to have it in the mspgcc.sf.net downloads too? It might belong to the packaging directory in cvs, but I would like people to test them first, and then give me some feedback before they are part of the project. Please Gentoo users, test and give me feedback. Jonas
