Re: Confused!



You'll have to be more specific about what you mean by VC++. If you mean
VC++ as found in Visual Studio 2005 and you are targeting Windows CE 5 and
later, then, yes, you can potentially use that. If you are talking about an
earlier version of Windows CE, eVC is your choice. Use eVC3.0 for Windows
CE 3.0 devices and eVC4.0 for Windows CE.NET 4.x devices (it also works for
Windows CE 5.0 devices, so there's a small amount of overlap).

The inclusion or exclusion of a given set of libraries is based on what's
actually in the operating system on the device. If the device has a media
player, presumably the media player APIs will be in the device's SDK; if
not, they won't (and you, of course, wouldn't be able to write a media
application for that device because media isn't in the device). WiFi is a
pretty general thing that most devices will include support for, but it's
still an OS component and can be included or excluded at the whim of the
device vendor.

There is no difference between Platform Builder from a vendor and from MS.
You can't buy it from Microsoft unless you are a very large customer. It's
just an alternative distribution channel.

SDKs are available from MS for device types that are standardized by MS:
Pocket PC and SmartPhone. For anything else, MS has no idea what's in the
OS on the device, so you have to get the SDK from the device vendor. We
don't 'sell' ours, since you have to buy a device to use it for anything,
but I suppose that some vendors might. As for what is an SDK, just as on
the desktop, it's a collection of things that you need to build software for
the device which the SDK is built for. It includes the header files, like
windows.h, and the libraries, like coredll.lib, that allow you to compile
and link your code into an application that will run on the device.

Are you planning to build your own device? If not, you don't need to know
what a BSP is. It is, in fact, a set of things like drivers and so on, that
allow the operating system to run on a *specific* piece of hardware, yours.

Platform Builder is something separate from Visual Studio and is *only* used
for those building the OS for custom hardware or for those writing drivers
to run in Windows CE. If you are an applications developer, you don't need
it.

***TELL US WHAT YOU ARE PLANNING TO DO AND WE CAN HELP YOU, BUT RIGHT NOW
YOU'RE JUST ASKING RANDOM QUESTIONS. WE CAN ANSWER THEM, BUT WITHOUT
KNOWING WHAT YOUR GOAL IS, THE ANSWERS ARE JUST MORE INFORMATION, NOT THE
RIGHT INFORMATION***

Paul T.

"Robby" <Robby@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E3F84043-DC58-42A1-84D7-F8D305292BC0@xxxxxxxxxxxxxxxx
Hi,

I am a little discouraged. I know I need some help. And I don't know who
to
open to so here it goes.

I am a <newbie> in this embeded world. I am a beginner VC++ programmer and
wish to eventually program an embeded board. I don't know if I can do this
with VC++ or eVC++ and what software/hardware I need. I know that in my
previous post, some very kind gentlemen have asnwered me that eVC++ is for
CE
only. But it goes further than this where, how would I know if eVC++ would
have all the libraries neccessary for what I want to do, ex: Play music,
video, WIFI?????

I am very confused since I started reading the msdn, and the sites I found
on google, I find myself reading stuff and then when I go on some vendor's
sight, I read stuff that completely contridicts what I learned.

Microsoft talks about platform builder, so do vendors, whats the
difference
between the platform builder that vendors sell as opposed to the ones
Microsoft sells?

The same goes for Microsoft's, SDKs, so do vendors sell them, whats the
difference?
What is an SDK? I have read that its a software development kit, so is it
software or hardware or both and exactly what does it do?

What is a BSP? Microsoft sells this and so do vendors..... I feel
frustrated
when I see all these terms. Is there some sort of an FAQ sight that can
start me slowly in the embeded world.

I have looked at the videos of Mike Hall, and found it somewhat confusing.
I
felt discouraged because they looked quite interesting, unfortunately I am
missing some basic notions.

Also, I have Microsoft Visual studio .NET 2003 installed on my machine, so
does this mean I have the SDK or the platform builder or is this sold
seperately.

As you can see, I need some basic literature or links that explain this. I
would really appreciate any suggestions or hints that could set me
straight
on this stuff.

Thanking all of you gentlemen in advance for your time and patients!

--
Best regards
Robert


.



Relevant Pages

  • Re: What are these targets for in eVC3?
    ... Well, we sell various Windows CE (not Pocket PC), devices and we have SDKs ... compiling against the basic Pocket PC SDK is probably adequate. ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: VS2005: installing old SDKs
    ... VS2005 only supports Windows CE 5.0 and later based SDKs ... Asking the vendors won't help. ... The SDK creation tools for 4.2 won't ... You have to stick with eVC 4 until the OS in those ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Playing fullscreen video
    ... the sample in the Windows Mobile 6 SDK compiled and ran fine under WM5. ... I've only been able to get DirectShow to play uncompressed AVI, ...
    (microsoft.public.windowsce.app.development)
  • Re: LTspice
    ... >>Ltspice really does run well under wine. ... >I think you will find that the extra overhead of running it under Windows ... So you have to solve the problem caused by the various distro vendors ... So far I've tried Fedora, Xandros, and SuSE. ...
    (sci.electronics.cad)
  • Re: Building VC++ 8.0 code on a machine without Visual Studio 2005
    ... In installed the Windows Platform SDK and as you noted ... I have not tried the latest SDK, ... Windows SDK is definitely a scenario we do support and in fact the VC ...
    (microsoft.public.dotnet.languages.vc)