[Coco] Microware C Compiler -- issues finding library files

Thu Aug 13 16:40:17 EDT 2015

Bill, your biggest advice is worth gold! It is these small details that make or break a project and the motivation behind.

>From what I can conclude from reading threads posted here I would assume that using an FPGA CoCo3 with OS/9 would also be a much faster alternative for compiling C. Would that be a correct conclusion? Has anyone done this and care to comment? :-)

Salvador

-----Original Message-----
From: Bill Pierce via Coco <coco at maltedmedia.com>
To: coco <coco at maltedmedia.com>
Cc: Bill Pierce <ooogalapasooo at aol.com>
Sent: Thu, Aug 13, 2015 9:11 am
Subject: Re: [Coco] Microware C Compiler -- issues finding library files

Chris, the original Microware C compiler is "hard coded" internally to look on
"/d1/defs" & "/d1/lib" for it's defs & libraries. As they are, the compiler disk
should be in "d0" and the library disk in "d1".
You can use "ded" to change this
as it's present in "cc1" and "c.prep". There is an article in the 1989 Oct
Rainbow (p82) about this; "What you should know about your C
compiler"

Alternately, you can download the "cc.dsk" disk image of the C
compiler from the Nitros9 repo which (I believe) already has those fixes and are
coded for "/dd/defs" & "/dd/lib". Of course, you need to have the "/dd"
descriptor in your boot.

Also, you can specify the library dir in the c.link
cmd line:
c.link -o=/dd/cmds/module xxx xxx xxx -l=/dx/lib/clib.l

If you go
beyond just using the cmd line to compile and use "makefiles", there are many
options to solve this. And ultimately, using a ramdisk will make the compiler
faster (Coco 3, OS9 L2).

Personally, I prefer a custom C system using several
"updated" or custom C tools. I also use NitrOS9 and Drivewire4.

The biggest
advise I can give is to use the Vcc Coco3 emulator for C compiling as you can
overclock the CPU and compiling C programs takes only seconds. Once compiled,
you can move your files to you Coco for testing. The Coco (1, 2, or 3, even
6309) is slow as molassass in January when it comes to compiling C code.
I have
a project that has over 125 C sources. It takes the Coco most of the day to
compile. Vcc at 72mhz will compile it in a few seconds (less than a minute) and
you still stay within the Coco and OS9 enviroment.

Bill Pierce
"Charlie
stole the handle, and the train it won't stop going, no way to slow down!" - Ian
Anderson - Jethro Tull

My Music from the Tandy/Radio Shack Color Computer 2
& 3
https://sites.google.com/site/dabarnstudio/
Co-Contributor, Co-Editor for
CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
Global Moderator for
TRS-80/Tandy Color Computer Forums
http://www.tandycoco.com/forum/

E-Mail:
ooogalapasooo at aol.com

-----Original Message-----
From: Chris Oliver
<chris.w.oliver at me.com>
To: coco <coco at maltedmedia.com>
Sent: Thu, Aug 13, 2015
7:21 am
Subject: Re: [Coco] Microware C Compiler -- issues finding library
files

Gene,

I have the 1983 Microware C Compiler, version 1.0, cat number
26-3038
distributed by Radio Shack.  Comes on 2 floppies: one has the compiler,
the
other has the libraries.

Thank you!

Chris

Generally, those options are
set
in the compilers driver script.  You 
didn't say which one, and there
are
several variations extant.

Cheers, Gene Heskett
-- 
"There are four boxes
to be
used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in
that
order."
-Ed Howdershelt (Author)
Genes Web
page
<
http://geneslinuxbox.net:6309/gene
>

> On Aug 13, 2015, at 12:47 AM,
Chris
Oliver <chris.w.oliver at me.com> wrote:
> 
> All,
> 
> Two-drive OS-9
scenario —
compiler (cc1) in /d1/cmds, LIB and DEFS (including stdio.h) on /d0. 
Execution
directory set to /d1/cmds.  For the life of me, I can’t figure out how
to get
the compiler to look on /d0 for LIB and DEFS — and I can’t put everything
on /d1
due to space.  Is there a way in OS-9 to pin one of the drives as the
“default
drive”, such that the compiler will look there vs. on the same drive as
the
current execution directory?  When I get to the linker, for example, I get
a
cannot-find error on “/d1/lib/cstart.r” — when, of course, cstart.r is
sitting
in /d0/lib.
> 
> Many thanks — I’m guessing there is something simple
here that
I’m overlooking…
> 
> Chris

-- 
Coco
mailing
list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco

-- 
Coco mailing
list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco