McCollister, Mike <[EMAIL PROTECTED]> wrote:
> However,
> when I switch to the 3.5 header files, I get complaints that certain header
> files can't be found.
If you're talking about things like Pilot.h being renamed PalmOS.h and
similarly Common.h -> PalmTypes.h and rearrangements like that, then that's
generic to 3.5 and CodeWarrior users need to deal with it too.
> Is there someone out there that has used GCC 0.5 for Win32 and added the OS
> 3.5 header files?
However the directory structure has also changed a bit in 3.5. This doesn't
affect users of CW (which searches a whole directory tree for headers), but
does affect GCC (which searches only one directory, so needs to be told about
each directory in a tree). Here are the instructions that will be in the
final version of the 3.5 SDK:
====
* prc-tools 0.5.0, based on GCC 2.7.2.2
Depending on how you have set things up, you want to add the header files
from this SDK to a `PalmOS35' directory alongside your old SDK headers.
This is complicated a little by the fact that most of the files in
`Palm OS 3.5 Support/Incs' are now down in a `Core' subdirectory.
1. Create a `PalmOS35' directory wherever you have put your `PalmOS1',
`PalmOS2', etc, directories.
2. Copy the directory tree under `Palm OS 3.5 Support/Incs/Core' to your
new `PalmOS35' directory.
3. Copy all the files in the top level `Palm OS 3.5 Support/Incs'
directory and all the files under `Palm OS 3.5 Support/Incs/Dynamic'
and `Palm OS 3.5 Support/Incs/Libraries' to your `PalmOS35' directory.
These files won't be in their official proper places, but at least you
will be able to get work done.
4. Again depending on how you have things set up, you can instruct GCC to
use these header files by changing the `PalmOS' symbolic link to point to
your `PalmOS35' directory.
5. You may also want to add the libraries in `Palm OS 3.5 Support/GCC
Libraries/m68k-palmos-coff' to somewhere in your linker search path.
Again, this depends on how you have set up the compiler; you may want
to use a `-L' linker option to point to the libraries if you use them.
====
There are better ways of doing this, but this way has the advantage of
being easy to explain :-). Prc-tools versions greater than 0.5.0 are
set up to use the 3.5 SDK layout as is, so this problem goes away.
(And a pre-built Windows version is currently about 3mm away from the
finish line at http://www.palm.com/devzone/, and it's crawling ever
closer... :-))
John
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
