Re: EVC3, EVC4 or VStudio 2005?

And I'm saying I'm using Studio 2005, just as it came out of the box, and I
see no errors or warnings when targeting PPC 2003 or WM devices. I know
many other people that are doing the same. I can therefore only conclude
that something is wrong with your environment.


--
Chris Tacke
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--




"ET" <e.thijsse@xxxxxxxxx> wrote in message
news:ce677$45b1454c$5962efda$7828@xxxxxxxxxxxxxxxxx
I will give an example:

In the PocketPC2003 SDK that is in VS2005 there is a C++ header file
called "vector".
In this header, there are the following lines:

typedef _A::size_type size_type;
typedef _A::difference_type difference_type;
typedef _A::pointer _Tptr;
typedef _A::const_pointer _Ctptr;
typedef _A::reference reference;
typedef _A::const_reference const_reference;
typedef _A::value_type value_type;

VS2005 C++ compiler complains about these lines, saying that 'typename'
must be inserted.

Looking at the WM5 SDK, in the same header file "vector", this file is
almost identical to the PocketPC2003 one, except for these particular
lines, which read:

typedef typename _A::size_type size_type;
typedef typename _A::difference_type difference_type;
typedef typename _A::pointer _Tptr;
typedef typename _A::const_pointer _Ctptr;
typedef typename _A::reference reference;
typedef typename _A::const_reference const_reference;
typedef typename _A::value_type value_type;

Therefore, I copied the WM5 version into the PocketPC2003 SDK, and voila,
no more complaints from the compiler about this header.

As you can see, the errors are easy to fix, but I still think the SDK
delivered with VS2005 should have had this fixed...

Thanks,

Etienne

"<ctacke/>" <ctacke[@]opennetcf[dot]com> schreef in bericht
news:uIYox5APHHA.4332@xxxxxxxxxxxxxxxxxxxxxxx
Yes, my point is I was using Studio 2005 when it was a Beta and have been
using it ever since and I've never had a problem. So I've got probably 2
years of usage without seeing what you're reporting. I also know several
other developers with the same experience as me. I've not made any
settings changes - I'm using it as installed, right out of the box.


--
Chris Tacke
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--




"ET" <e.thijsse@xxxxxxxxx> wrote in message
news:c4112$45b1320d$5962efda$23680@xxxxxxxxxxxxxxxxx
True, before VS2005, there was no problem...
The problem is with VS2005, not with anything before that; VS .NET
worked fine, eVC4 worked fine.
Just not VS2005...

Did you use VS2005 ? Maybe there is a setting somewhere with which you
can turn off these new language features; I don't know; I didn't find
it.

Etienne

"<ctacke/>" <ctacke[@]opennetcf[dot]com> schreef in bericht
news:OiF5im2OHHA.4644@xxxxxxxxxxxxxxxxxxxxxxx
I find that hard to believe. There's got to be something wrong with
what you've got set up. I've been developing since before Studio '05 was
released using the PPC 03 SDK (I rarely use the WM SDK) and I've seen no
problems at all.


--
Chris Tacke
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--




"ET" <e.thijsse@xxxxxxxxx> wrote in message
news:618f9$45affc09$5962efda$1343@xxxxxxxxxxxxxxxxx
I originally wrote a prototype of our product for PocketPC 2003 using
EVC4.

Later, I wanted to build it using VS2005 and also build for WM5.

The PocketPC 2003 SDK is included in the installation of VS2005, so I
thought I could build right out of the box.
Alas... The SDK included is the same one that I had downloaded earlier
for my work using EVC4, with which it builds fine. But, the C++
language of VS2005 has undergone some "breaking changes", and the
included SDK has not been updated, so sme of the code in some of the
header files don't compile.

Fortunately, the SDK for WM5 conforms to the new C++ language, but
this SDK is not included in the VS2005 installation. I ended up having
to copy six or seven header files from the WM5 SDK into the PocketPC
2003 SDK in order to get it to build correctly again. A windiff on
these headers learned that the only difference between the PPC2003 and
the WM5 version has to do with these C++ language changes, so I could
do this quit safely, at least for these six files.

I found it quite disappointing that an SDK included in the VS2005
installation does not conform to its own syntax rules...

Regards,

Etienne


"AliR (VC++ MVP)" <AliR@xxxxxxxxxxxxx> schreef in bericht
news:DKvph.26574$QU1.11102@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Everyone,

I have to maintain 2 programs one is PocketPC 2003 app and the other
is WinCE application. In the past the Pocket PC program was compiled
using evc3 and the WinCE was created and compiled using evc4.

I have just had to rebuild my development computer and I can't
compile either one of the projects. (I can't seem to get all the
pieces together!).

Anyway, I tried to open the PocketPC project (evc3) in VS2005 put it
wouldn't compile there either. wcesock.h was missing.

Anyway, before I get too deep into this conversion, I wanted to know
which compiler I should use. Should I convert the two program to
VS2005?

Thanks
AliR.














.

Relevant Pages

  • Re: EVC3, EVC4 or VStudio 2005?
    ... In the PocketPC2003 SDK that is in VS2005 there is a C++ header file called ... VS2005 C++ compiler complains about these lines, ... Therefore, I copied the WM5 version into the PocketPC2003 SDK, and voila, no ...
    (microsoft.public.pocketpc.developer)
  • Re: EVC3, EVC4 or VStudio 2005?
    ... Then I can only assume you are not using these six header files that I had ... VS2005 C++ compiler complains about these lines, ... Looking at the WM5 SDK, in the same header file "vector", this file is ... Therefore, I copied the WM5 version into the PocketPC2003 SDK, and voila, ...
    (microsoft.public.pocketpc.developer)
  • Re: Problems with GetOpenFileName and GetSaveFileName
    ... > OK I've tested your program with VC6 SP6. ... what version of the Platform SDK are you using? ... even offered them free upgrades to 98SE but they didn't go for it). ... > SDK installed and available to the VC compiler.. ...
    (microsoft.public.win32.programmer.ui)
  • Re: Platform Manager API and build directories
    ... The SDK installed for a given *device* knows what processorthe device ... To achieve this, given a compiler I ... Then retrieve the environment parameters. ... I have talked about the "target ...
    (microsoft.public.windowsce.platbuilder)
  • Re: VSS SDK writer impossible to compile
    ... have the same problem of a useless SDK, here is a solution that works. ... In the end, it seems to be a compiler issue, the C/C++ compiler in VStudio ... I created a SOURCES file and compiled it with DDK ... 6000 as a Win2K3 console application. ...
    (microsoft.public.win32.programmer.kernel)
Loading