> > just download the new headers and unzip them into the m68k
> > directory overwriting the current include files..
> >
> > cheers.
>
> I don't quite know what your needs are, but I believe that it should always
> be possible to keep different versions in parallel. In a good configuration
> management environment, it should be guaranteed that when you rebuild an old
> version of a program, you also reuse the same tools, libraries and include
> files. Therefore, overwriting an old directory seems awkward to me. What I
> have done (not with GCC 0.5, but with a version that contained 3.0
> libraries) is change my directory structure into
>
> m68k-palmos-coff\include\PalmOS 3.1 Support
> m68k-palmos-coff\include\PalmOS 3.0 Support
>
> Each of these directories then contains the header files including their
> subdirectories.
>
> 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 :>
it is common that the API's are backward compatable.. so it does not
hurt to build against 3.3 API's for 3.1 or 3.0 devices :> i dont
clobber my include dirs.. however someone who wants to replace them
can :>
cheers.
az.
--
Aaron Ardiri
Lecturer http://www.hig.se/~ardiri/
University-College i G�vle mailto:[EMAIL PROTECTED]
SE 801 76 G�vle SWEDEN
Tel: +46 26 64 87 38 Fax: +46 26 64 87 88
Mob: +46 70 656 1143 A/H: +46 26 10 16 11
