John Marshall <[EMAIL PROTECTED]> wrote in message
news:2644@palm-dev-forum...
>
> Nick Hammond <[EMAIL PROTECTED]> wrote:
> > See http://www.palm.com/devzone/tools/gcc/ for version 2.0 but be
prepared
> > to struggle with the setup,
>
> I really wish people would explain in what way they find these things to
be
> a struggle. It would then become possible to make it less of a struggle.
John,
Perhaps it would have been clearer to say "arriving at a working stable
development system" rather than just "the setup". A brief history:
Installation worked OK except that:
o mount is far from intuitive and after wasting more than enough time
stuffing around with it I just went in and hacked the Registry.
o the documentation doesn't say where in the directory tree to put the
SDK include files and I guessed wrong. Worked around this with the -I
option and finally fixed it after I found your message with the correct
directory tree description on pilot.programmer.gcc (which still seems to be
dead incidentally).
Next problem was that build-prc rejected wildcard specifications such as
"*.bin". This turned out to be that make was using DOS rather than Unix
mode. I have been using the --unix option but a recent message on this
forum points to an environment variable which can be set. It would be good
to do this in the installation.
Current problem is that although the app I am using for testing appears to
compile and link OK, it doesn't run -- hangs in Poser with no error message
at all. Behaviour indicates a problem with floating point math intensive
functions. A new message in this forum points to possible problems with the
libraries and suggests copying the 0.5.0 libraries -- I haven't yet tried
this.
None of this is particularly earth shattering but it is fair to say that the
experience of upgrading from 0.5.0 isn't yet seamless. If it wasn't for the
fact that the 32K limit and a disinclination to have separate libraries
dictates the use of 2.0, I would probably have reverted to 0.5.0 and waited
for a bigger experience base to build up.
Part of the problem is that the documentation is fine for systems
programmers with a Unix background but more difficult for ordinary people.
When I finally get this working, I will volunteer to work on updating the
documentation for the rest of us.
Please don't take any of the above as criticism. I have nothing but
admiration for you and all the other people who have worked to bring us an
alternative development system for the Palm and I appreciate that any new
system is going to have teething problems.
Best regards,
Nick.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
