> -----Original Message-----
> From: John Marshall [mailto:[EMAIL PROTECTED]]
>
> Aaron Ardiri writes:
> > Vereecke Jan writes:
> >>
> >> In fact I would like it even more if I could just use the
> command line of
> >> gcc to indicate where my headers are, but I didn't get
> that to work yet.
> >
> > -I/gnu_palm/m68k-palmos-coff/include/PalmOS3
> >
> > should work fine - just modify the Makefile :>
>
> Rather no. The SDK includes are in five or six directories under this
> one, and you have to have -I options for all of them. We
> discussed this
> one to death on pilot-unix last year; the thread starts at
>
> http://www.acm.rpi.edu/~albert/pilot/Sep98/0124.html
>
>At Simon's insistance :-), we retained the ability to specify in the
>command line which set of include files you want. In the new version
>of Palm OS GCC, you can say things like
>
> m68k-palmos-gcc -c blah.c -palmos2
>
>to get the includes from the /usr/local/m68k-palmos/include/PalmOS2 tree.
>This allows you to have include trees for several OS revisions coexisting
>happily, and different projects building against different SDK trees.
I think what you're referring to is that off the "Incs" directory
there are subdirectories of "UI", "System", etc. and the files
from these subdirectories are included as (for example) <AboutBox.h>
instead of <UI/AboutBox.h>.
One pass through the headers (especially UI/UIAll.h) to correct the
includes would take care of this such that you would only need to -I
the topmost directory instead of each of the subdirectories individually.
I don't think that that sort of change would break too much code, since
most code includes <Pilot.h>, which in turn includes most of what you
need from the subdirectories.
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
