Rick,
The CVS repository is where work done by the MSPGCC development team is
stored. There are two ways to get to the repository. You can use command
line tools, like 'cvs' in the 'buildnew' script, or you can browse with a
web browser to http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mspgcc/.
Notive that there are some 15 directories, one of which is 'examples'. You
can either modify the script to pull the examples, or you can type a line
similar to the script to do the same thing (the script isn't required is
what I think my point is).
Besides the examples directory, there is the pybsl directory, which is a
Python based tool for using the FET140 or other FET programmers to program
the MSP430s. There's also the 'gdb' tools, which are a pain-in-the-butt
debugging toolset. 'Insight' is supposed to make 'gdb' easier to use, but
... well, the user interface to gdb sucks. And what it sucks probably isn't
appropriate for a family oriented mailing list.
You can pull any or all of these directories and build the tool sets in
them. They all have varying ways of doing this, so there are no generalized
instructions I can give you. In ideal-land, you'd yank the directory, type
'./configure && make && make install' and EVERYTHING would be done for you.
However, Linux isn't ideal-land (it's situation about 4000 miles from there.
It is, however, about 25 miles from Trenton, New Jersey, which some say is
only a stones throw from hell).
You can use your browser to poke around in the CVS to get an idea of
what's
there. You have read-only access, so there's nothing to break.
Hope this helps some. If not, let me know. CVS and tool building
isn't an
intuitive process. Sometimes it takes a lot of poking and guessing to get
it right. Allow me to make an aside comment that while CVS can be somewhat
arcane, it's a very valuable version management tool. I keep most of my
projects in it. There are CVS tools for every major OS, and they're all
pretty much interoperable. Very handy for projects with multiple
developers, and for doing version control. It also simplifies my backups,
since I only need to push my CVS directory out to DVD every day (a single
directory and it's children, rather than directories spread out all over the
disk).
--John
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]on Behalf Of Rick
> Jenkins
> Sent: Sunday, March 30, 2003 16:08
> To: [email protected]
> Subject: Re: [Mspgcc-users] Makefiles for examples
>
>
> Using the J.C. Wren "buildnew" script for the install, this
> top-level examples
> directory is missing. How do I retrieve it?
>
> Thanks,
> rick
>
>
> On Sun, 30 Mar 2003 12:05:41 <[email protected]> wrote:
> > NO you did not.
> > there are really no makefiles.
> > But there are another top-level dir 'examples' which
> contains some examples
> > along with makefiles.
> > ~d
> --
> Rick Jenkins <[email protected]>
> Hartman Technica http://www.hartmantech.com
> Phone +1 (403) 230-1987 voice & fax
> 221 35 Avenue. N.E., Calgary, Alberta, Canada T2E 2K5
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Mspgcc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>
