Re: Where to start ? Too many options to choose from.

Ulrich Eckhardt wrote:

Avoid eVC4 if you can. It has an age-old, far from standard-compliant C++
compiler and is really old anyway. The difference between 2003 and 2005 is
not that big, the latter has supposedly better integration but it also
still suffers some childhood problems. We use it for CE5 development here
nonetheless, so it works.
Aye

It's not part of any of those products. PB is used to build a platform
(hear, hear...) which means you select a CPU, drivers, applications etc
which are then compiled into an image. The process is comparable with Linux
kernel configuration but it also includes quite a few userspace tools to
choose from.
Yes, it's very similar to uClinux build process. First compile kernel, then userspace program, then create a bootable image. And it was a quite painless process I might add (i.e. depencies were tracked fairly well)

It further serves as IDE for debugging the kernel and
compiling new/adapted device drivers. Note that for distribution, the
generated CE images need to be licensed, a cost which also depends on the
contained feature set.

Of course. FYI, with evaluation board I have a Win CE 5.0 Pro license.

You typically only need that if you are creating the hardware, too. Since
you already have a system with a working CE5 on it, you don't need it
unless you have to make changes there. Since you are currently only using
an evaluation board, I guess that the final hardware will be derived from
it, so I guess you will need PB.
Exactly. Also final product won't need media player, nor internet explorer since this is a industrial control application. Hence I'd need platform builder. But I still haven't got my answer; where can I get it ? Since it should be specifically built for this device, I suppose board manufacturer would be the appropriate place to ask for it.

The default settings for the serial port are 19200 Baud, I think that value
can be increased. Otherwise, see these links:

http://blogs.msdn.com/vsdteam/archive/2005/01/05/347332.aspx
http://blogs.msdn.com/vsdteam/archive/2005/04/28/413304.aspx
Looks promissing, thanks.

Upgrading always requires some changes, but my recent switch from 4.2 to 5.0
was relatively painless. However, in that case you definitely need platform
builder (though I'm not sure it's still called that, I have heard PB for
CE6 is integrated into VS2005 instead of being a standalone product).
I suppose it's called "Platform Manager" or something like that. I've also read that it's integrated with VS2005, but I couldn't find more information.

This is where I'm having problem actually, I can't find the information I'm looking for and I don't know who to ask (I think here's the most appropriate place). Even though linux world is known with its poor documentation, I could have find what I'm looking for. And with Microsoft, it's true that most of the .NET framework is well documented with samples, I having trouble finding my way with embedded development.

I'd appreciate a few directions for information here.
.

Relevant Pages

  • Re: interesting use of NEXT SENTENCE vs. CONTINUE
    ... These days I don't do compiler maintenance, but I HAVE done in the past, so ... You had a chance to point out how adherence to the standard can improve ... >> compile it WITH MINOR MODIFICATIONS for a specific platform. ... > platform-specific extension to COBOL ...
    (comp.lang.cobol)
  • Re: interesting use of NEXT SENTENCE vs. CONTINUE
    ... I DID think any old compiler would be able to ... > compile it WITH MINOR MODIFICATIONS for a specific platform. ... > not going to go to the Standard to see what SHOULD work. ... If you write your COBOL code avoiding the things that are marked as ...
    (comp.lang.cobol)
  • Re: Standard Ada Preprocessor
    ... because Ada cannot deal with the portability issues. ... > you are interfacing directly to some special-purpose hardware. ... by their nature not compiler ... one platform you get 3 members back, and on another you get 5, ...
    (comp.lang.ada)
  • Re: C portability is a myth
    ... > solicitation for the availability of a compiler for a given platform. ... If the source is pure Standard C ... can be successfully ported to all implementations. ...
    (comp.lang.c)
  • Re: C portability is a myth
    ... > solicitation for the availability of a compiler for a given platform. ... People frequently talk about porting applications where no ... Yet further down you say the Java standard ports. ...
    (comp.lang.c)
Loading