Re: building vxWorks for nitro-260

[wbrown@csg.lbl.gov (Bill Brown)]

FYI, here's the reply from Heurikon.

> From degreene@copernicus.heurikon.com Thu Dec  7 11:11:16 1995
> From: "David Greene" <degreene@copernicus.heurikon.com>
> Date: Thu, 7 Dec 1995 13:10:25 -0600
> In-Reply-To: wbrown@csg.lbl.gov (Bill Brown)
>         "Re: (Fwd) Re: VxWorks Tapes" (Dec  5, 12:30pm)

> Bill,
> 
> Following is a suggested workaround, but first is a general suggestion.
> 
> IN GENERAL:
> Normally, for a specific target, it is best to define options in the config.h
> file.  The settings in this configuration header file supercede anything set in
> configAll.h.  The "Programmer's Guide: VxWorks 5.2" explains this very well in
> sections 10.3.1.1 and 10.3.1.2 (and mercifiully with less than a page of text).
> 
> WORKAROUND:
> Here is the workaround I suggested to the other customer who is seeing
> apparently the same problem:
> 
> 	-Put all desired option definitions into config.h instead of
> configAll.h
> 
> 	-INCLUDE_SECURITY may cause compile problems when defined in config.h,
> 	 so I put it in configAll.h
> 
> This made the problem go away.  I don't yet know why and am still investigating
> the root cause.
> 
> Dave

It works, altho I haven't a clue as to why.  One can go on for days about the
wisdom of invoking which things in what .h files.  I thought that our setup
was a fairly generic release from WRS, but since I didn't originally build
it (or install the release) I could be wrong.

In anycase, if anyone else wants to use these boards, it would be a good
idea to squirel this info away in a "safe place.

I'm impressed with the support I got from Heurikon on this.  

-bill