Aaron Ardiri writes:
> Vereecke Jan writes:
>> Next I change the contents of the file
>> lib\gcc-lib\m68k-palmos-coff\2.7.2.2-kgpd-071097\include\PalmOS
>> from "!<symlink>../../../../../m68k-palmos-coff/include/PalmOS" to
>> "!<symlink>../../../../../m68k-palmos-coff/include/PalmOS 3.1 Support/Incs"
>> or to "!<symlink>../../../../../m68k-palmos-coff/include/PalmOS 3.0
>> Support/Incs" depending on what headers I want to use.
>>
>> 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.
(Look in the specs file or m68kpalmos.h of the patches on my web site
if you are interested how this was implemented. It makes a big mess in
the specs file, but apparently people think it's a useful feature...)
John
