Re: [pilot-db-list] development environment (was: Hebrew support)

[Yedidyah Bar-D. <di...@ta...>]

On Tue, Apr 27, 2004 at 09:57:01AM -0600, Nathan Kurz wrote:
> > > I've found that the Palm Simulators _almost_ work under Wine, and
> > > perhaps someone with greater knowledge could actually make them work.
> > > I have had success running GDB on Linux ethernet connected to
> > > Simulators running on Windows.  If you do this, note that you will
> > > need gdbpanel installed for  GDB to work with a Simulator.
> > 
> > I currently won't try this, as Windows is much less convinient for me.
> > If/When you make it work with wine, I might try this.
> 
> Windows is terribly inconvenient for me as well, as besides making me
> violent, I need to borrow a laptop just to run it.  The problem is

For me it means to connect to a Windows Terminal Server at work, over
ADSL. Not that bad, compared to borrowing a laptop, but still...

> that all recent Palm devices (including all high resolution ones) will
> not run on Pose.  So if one wishes to check for compatibility, one
> either needs recent real devices to test on needs to run the Simulator.
> 
> Most of the known problems with the CVS version were with recent devices.

OK, but the *good* things are the same, I hope. So if you fix the bad
ones (or simply go to 1.1.0), I can still work with pose only, if all I
want is to add new stuff (or fix bug that also happen in pose, such as
the one I talked about).

BTW, I tried playing with the simulator very briefly. I saw it has its
own ROMs, which IIRC are the really compatible with real devices' ROMs.
Is it so? Doesn't this mean that for debugging a problem with a new real
device you still need a new real device (unless the problem isn't specific
to it, but rather is related to high resolution etc.)?

> 
> > > What this means is that you should concentrate your efforts on the
> > > 1.1.0 release code, and ignore the CVS and alpha series.  I'll try to
> > > make the appropriate changes to the CVS repository later this week.
> > > 
> > 
> > I will try and see if there is anything that works for me better with
> > the CVS version. If not, Fine. Otherwise I'll try to back-port to 1.1.0.
> 
> Feel free to use it, but to be clearer: by the end of the week, I hope
> that the CVS version will become a branch called "Scott", and the
> 1.1.0 will become the version you get by default (HEAD).  The Scott
> branch (current CVS) will be preserved for historical interest and
> occasional code consultation, but likely will never be released again.
> If you write patches for it, they will not be of use by others.

That's just fine with me - 1.1.0 is ok for me. I just wanted to make
sure that CVS doesn't also include fixes to bugs in 1.1.0 (and not only
the middle of adding new features). Are you sure it's not the case?

For example, io.c from 1.1.0 #includes CharAttr.h, which does not exist
in sdk5r3 (but does in older versions). CVS does not include it. Not that
it's such a big thing, but maybe there are other fixes.

> 
> > > Yes, external SDK's are required for these.  Worse, these SDK's aren't
> > > all easily available, and need to be extensively massaged if they are
> > > to work with GCC (prc-tools).  While you can build successfully
> > > without them, in the CVS version I found bugs in the non-enabled code
> > > path.  Contact me if you'd like help getting these SDK's.
> > 
> > No, unless you think I should also use them with 1.1.0.
> 
> Probably you should, but you are more likely to be safe without them.

If it's trivial for you to email, and not legally or otherwise
problematic, go ahead. I'd rather work on an environment as yours and
see the same bugs you see.
-- 
Didi