I installed prc-tools from the ports. I am using freebsd 4.6. so I made a little work directory and downloaded some palm code and tried to compile Main.c as shown below. Main.c has the following includes
#include <BuildDefines.h> #include <PalmOS.h> I get the error mesagaes Main.c:13: BuildDefines.h: No such file or directory Main.c:17: PalmOS.h: No such file or directory In other words it is not finding the files. But these files are in /usr/local/palmdev/sdk-3.5/include In fact, PalmOS.h and BuildDefines.h include more files that are in /usr/local/palmdev/sdk-3.5/include/Core/ So there are a bunch of header files for palm programming that are based at /usr/local/palmdev/sdk-3.5 and may be stuck even deaper in folders contained in /usr/local/palmdev/sdk-3.5/include/ Seems like there has to be a way to add a search path to gcc to look for included files that are of the type #include <thefile.h>. It would be a pain if I had to manually put all the needed files into /usr/include. Hope this is enough info. Let me know if you need more. Thanks. Wayne --- Adam Weinberger <[EMAIL PROTECTED]> wrote: > did you install the prc-tools port, or the > prc-tools-gcc port? or did > you not install from the ports tree? > > what error message are you getting? > > can you give an example of the #include directive? > > do the header files even exist within > /usr/local/palmdev? > > some more info would be a big help. > > -Adam > > > >> (10.05.2002 @ 1548 PST): Wayne Lubin said, in > 0.9K: << > > Hi, > > > > I grabbed the prc-tools development environment > for > > the palmos. The problem is the palm has a bunch of > its > > own header files and a lot of code includes them > in > > the #include<thefile.h> type of include. But the > files > > live in the palmdev folder, but gcc doesn't look > there > > by default of course. I tried to play with the -I > > switch like so > > > > gcc -c -I /usr/local/palmdev/ -o Main.o Main.c > > > > but that doesn't work. The man page says something > > about using -I- along with -I to get it to do what > I > > want, but I did not understand the man page. > Anyone > > know what I should do? Is there a way to add the > path > > to gcc itself so that I wouldn't even have to do > it > > each time on the command line? Thanks. > > > > Wayne > > > > __________________________________________________ > > Do you Yahoo!? > > Faith Hill - Exclusive Performances, Videos & More > > http://faith.yahoo.com > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-questions" in the body > of the message > > > >> end of "adding a path to gcc to find #include > <something.h> type includes" from Wayne Lubin << > > > -- > "Oh good, my dog found the chainsaw." > -Lilo, "Lilo & Stitch" > Adam Weinberger > [EMAIL PROTECTED] > http://vectors.cx > __________________________________________________ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
