Hi.
Glad you got it working !!

jsand wrote :

> Since macros are just substitute scripts, that makes them
> akin to definitions within, say the include files...

Correctly, they have to be included in every source
file (where they are referenced!), either directly or
indirectly. I usualy have one common "project-inlude-file",
that just includes the rellevant specific include files. So
if one inc file is added to the project, it just has to be
inserted in one file (the project common inc file).

(This is the deafult setup in Olin's environment...)

> I fancy using Olin's environment, but I'll only tackle that after I've
> got more running confidence with the insides of linkers and suchlike.

Actulay, one reason to take a look at Olins environment is
to *not* have to worry about "the insides of linkers and suchlike".
Olin have already done all that stuff for you !

I had my first Olin'ized project up an running using his environment
right out-of-the-box, and only learned more about the linker and linker
scripts later when I had some specific problems. And learning by looking
at a *working* example is unbeatable...

Or, to put it another way, if you had used Olins environment for
this actual project, you hadn't done *this* error :-)

>
> I really must start eating a lot more cabbage.
> Thanks, to you guys. I owe you all a beer or six.
> Next time you're in Johannesburg.......

Well, Sweden might be in the right time-zone, but...
:-) :-)

Regards
Jan-Erik.

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu