The files...

[John S Gwynne]

--------

   In message <9411021338.AA07764 at sbctri.sbc.com> , you write:
 
| Could you share more information about your development environment?
| What you're using, any changes you needed to make, etc.

Ok, here's a list of m68k *specific* tools that were built:

m68k-sun-sunos4-ar	archive and library maintainer
m68k-sun-sunos4-as	assembler
m68k-sun-sunos4-c++	c++
m68k-sun-sunos4-c++filt	demangle C++ symbols
m68k-sun-sunos4-g++	GNU project C++ Compile
m68k-sun-sunos4-gcc	GNU project C
m68k-sun-sunos4-ld	the GNU linker
m68k-sun-sunos4-nm	list symbols from object files
m68k-sun-sunos4-objcopy	copy and translate object files
m68k-sun-sunos4-objdump	display information from object files
m68k-sun-sunos4-ranlib	generate index to archive
m68k-sun-sunos4-size	print the section sizes of an object file
m68k-sun-sunos4-strings print the strings of printable characters in files
m68k-sun-sunos4-strip	remove symbols and relocation bits

Of course other key components, like the pre-processor, are configured
for the host and are not included in this table. As you see, a typical
unix setup with make, emacs,...

Most of these tools now build with almost no effort (I recall having
more trouble making cross-development configurations on older versions).

Also, check the archive. I walked through the process of compiling and
loading a C program into my board for both a RAM and EPROM memory
model. It's all automated :). (I had to write a few things like a
loader script etc...)

                                       John S Gwynne
                                          Gwynne.1 at osu.edu
_______________________________________________________________________________
               T h e   O h i o - S t a t e   U n i v e r s i t y
    ElectroScience Laboratory, 1320 Kinnear Road, Columbus, Ohio 43212, USA
                Telephone: (614) 292-7981 * Fax: (614) 292-7292
-------------------------------------------------------------------------------