Ok, a google search pulls up nothing. Basically, I just installed eVC++ 4.0,
the PPC 2003 sdk, and SP4. Cannot get anything to build. If I create a new
PPC 2003 simple CE app or hello world app then attempt to build, it will not
work. I get the following error:

Compiling resources...
C:\Documents and Settings\Paul King\My Documents\Dev\HelloWorld\newres.h(32)
: fatal error RC1015: cannot open include file 'winver.h'.
Error executing rc.exe.

A google search pulls up many people asking this question, but no solutions.
Can somebody please help?

Re: eVC++ 4.0 SP4, Cannot build anything. Please help by Lao

Lao
Mon Apr 03 01:11:43 CDT 2006

It is very hard to guess what is going on with such error message. You
need to give more details for people to help. For example, how do you
create the project (the wizard setting), what files are in the project,
what target platform did you choose, and etc?

AFAIK newres.h is for Smartphone projects. Are you starting a
smartphone project?

---
Lao K
Windows Mobile Pocket PC Smartphone Programming Hints and Tips
http://windowsmobilepro.blogspot.com


Re: eVC++ 4.0 SP4, Cannot build anything. Please help by Kerstin

Kerstin
Mon Apr 03 03:49:39 CDT 2006

Hi!

Basically it looks like your "Include Directories" list is incomplete. One
of the drawbacks of eVC is that it does not set those lists all that
intelligently (one of the drawbacks of VS 2005 is that it won't tell me
voluntarily how and why it set said lists) - so just try and check "Tools->
Options->Directories" as well as yur INCLUDEDIRS.

Greetings,

Kerstin

=?Utf-8?B?Sm9uYXRoYW4gS2luZw==?=
<JonathanKing@discussions.microsoft.com> wrote in
news:A613317B-4252-4B77-8A62-9B5E59B866AB@microsoft.com:

> Ok, a google search pulls up nothing. Basically, I just installed
> eVC++ 4.0, the PPC 2003 sdk, and SP4. Cannot get anything to build. If
> I create a new PPC 2003 simple CE app or hello world app then attempt
> to build, it will not work. I get the following error:
>
> Compiling resources...
> C:\Documents and Settings\Paul King\My
> Documents\Dev\HelloWorld\newres.h(32)
>: fatal error RC1015: cannot open include file 'winver.h'.
> Error executing rc.exe.
>
> A google search pulls up many people asking this question, but no
> solutions. Can somebody please help?


Re: eVC++ 4.0 SP4, Cannot build anything. Please help by r_z_aret

r_z_aret
Mon Apr 03 16:41:54 CDT 2006

On 2 Apr 2006 23:11:43 -0700, "Lao K" <windowsmobilepro@yahoo.com>
wrote:


clip


>AFAIK newres.h is for Smartphone projects. Are you starting a
>smartphone project?

I'm pretty sure the resources commonly defined in newres.h are
required for _any_ program that uses SHCreateMenuBar. And I'm sure
that covers all Pocket PCs. I have a copy in the source folders for
many (probably all) samples that came with my Pocket PC and Smartphone
SDKs. And I sure need a copy for my Pocket PC projects.

>
>---
>Lao K
>Windows Mobile Pocket PC Smartphone Programming Hints and Tips
>http://windowsmobilepro.blogspot.com

-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).

Robert E. Zaret, eMVP
PenFact, Inc.
20 Park Plaza, Suite 478
Boston, MA 02116
www.penfact.com

Re: eVC++ 4.0 SP4, Cannot build anything. Please help by JonathanKing

JonathanKing
Mon Apr 03 16:59:03 CDT 2006

I am creating a new Pocket PC 2003 application, building for WCE ARMV4 and
WCE emulator. The I select typical hellow world application or a simple
WinCE application. Either one gives me the same error. I just tried with a
smartphone project same thing.

I just went to "Tools->Options->Directories". Under the Pocket PC 2003
platform, there are three entries:
C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\Include\emulator
C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\mfc\include
C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\atl\include
Winver.h is in the first directory, so why wont it open? If I move winver.h
to the project directory, then I get another error that it cannot find
aygshell.h. If I copy that to the project folder, I get another error, and on
and on. It really does sound like an include problem, but the directory is
there.

Another thing, if in the workspace viewer, I click the resources tab and try
to expand the resources folder, I get the same thing. Error RC1015 cannot
open winver.h. What is wrong?

"Kerstin Pirrung" wrote:

> Hi!
>
> Basically it looks like your "Include Directories" list is incomplete. One
> of the drawbacks of eVC is that it does not set those lists all that
> intelligently (one of the drawbacks of VS 2005 is that it won't tell me
> voluntarily how and why it set said lists) - so just try and check "Tools->
> Options->Directories" as well as yur INCLUDEDIRS.
>
> Greetings,
>
> Kerstin
>
> =?Utf-8?B?Sm9uYXRoYW4gS2luZw==?=
> <JonathanKing@discussions.microsoft.com> wrote in
> news:A613317B-4252-4B77-8A62-9B5E59B866AB@microsoft.com:
>
> > Ok, a google search pulls up nothing. Basically, I just installed
> > eVC++ 4.0, the PPC 2003 sdk, and SP4. Cannot get anything to build. If
> > I create a new PPC 2003 simple CE app or hello world app then attempt
> > to build, it will not work. I get the following error:
> >
> > Compiling resources...
> > C:\Documents and Settings\Paul King\My
> > Documents\Dev\HelloWorld\newres.h(32)
> >: fatal error RC1015: cannot open include file 'winver.h'.
> > Error executing rc.exe.
> >
> > A google search pulls up many people asking this question, but no
> > solutions. Can somebody please help?
>
>

Re: eVC++ 4.0 SP4, Cannot build anything. Please help by Kerstin

Kerstin
Tue Apr 04 04:34:16 CDT 2006

Hi!

Now this looks interesting...

I only ran across a similar problem once in my life - and the solution
was that the INCLUDEDIRS list was too long, longer than 512 Bytes. So I
had to weed out the path list somewhat.

On older systems, a similar behaviour could be found if someone did edit
the environmentals manually and did not take care of whitespace, but if
you install everything with the proper tools, that should never happen.

Can you export a makefile and have a direct look at it? That would tell
most clearly where your compiler is searching for the includes.

Greetings,

Kerstin



=?Utf-8?B?Sm9uYXRoYW4gS2luZw==?=
<JonathanKing@discussions.microsoft.com> wrote in
news:D95C8FC5-BD55-4C29-B051-1EA4BDBFC86E@microsoft.com:

> I am creating a new Pocket PC 2003 application, building for WCE ARMV4
> and WCE emulator. The I select typical hellow world application or a
> simple WinCE application. Either one gives me the same error. I just
> tried with a smartphone project same thing.
>
> I just went to "Tools->Options->Directories". Under the Pocket PC 2003
> platform, there are three entries:
> C:\Program Files\Windows CE Tools\wce420\POCKET PC
> 2003\Include\emulator C:\Program Files\Windows CE Tools\wce420\POCKET
> PC 2003\mfc\include C:\Program Files\Windows CE Tools\wce420\POCKET PC
> 2003\atl\include Winver.h is in the first directory, so why wont it
> open? If I move winver.h to the project directory, then I get another
> error that it cannot find aygshell.h. If I copy that to the project
> folder, I get another error, and on and on. It really does sound like
> an include problem, but the directory is there.
>
> Another thing, if in the workspace viewer, I click the resources tab
> and try to expand the resources folder, I get the same thing. Error
> RC1015 cannot open winver.h. What is wrong?
>
> "Kerstin Pirrung" wrote:
>
>> Hi!
>>
>> Basically it looks like your "Include Directories" list is
>> incomplete. One of the drawbacks of eVC is that it does not set those
>> lists all that intelligently (one of the drawbacks of VS 2005 is that
>> it won't tell me voluntarily how and why it set said lists) - so just
>> try and check "Tools-> Options->Directories" as well as yur
>> INCLUDEDIRS.
>>
>> Greetings,
>>
>> Kerstin
>>
>> =?Utf-8?B?Sm9uYXRoYW4gS2luZw==?=
>> <JonathanKing@discussions.microsoft.com> wrote in
>> news:A613317B-4252-4B77-8A62-9B5E59B866AB@microsoft.com:
>>
>> > Ok, a google search pulls up nothing. Basically, I just installed
>> > eVC++ 4.0, the PPC 2003 sdk, and SP4. Cannot get anything to build.
>> > If I create a new PPC 2003 simple CE app or hello world app then
>> > attempt to build, it will not work. I get the following error:
>> >
>> > Compiling resources...
>> > C:\Documents and Settings\Paul King\My
>> > Documents\Dev\HelloWorld\newres.h(32)
>> >: fatal error RC1015: cannot open include file 'winver.h'.
>> > Error executing rc.exe.
>> >
>> > A google search pulls up many people asking this question, but no
>> > solutions. Can somebody please help?
>>
>>


Re: eVC++ 4.0 SP4, Cannot build anything. Please help by r_z_aret

r_z_aret
Tue Apr 04 17:11:52 CDT 2006

On Mon, 3 Apr 2006 14:59:03 -0700, Jonathan King
<JonathanKing@discussions.microsoft.com> wrote:

>I am creating a new Pocket PC 2003 application, building for WCE ARMV4 and
>WCE emulator. The I select typical hellow world application or a simple
>WinCE application. Either one gives me the same error. I just tried with a
>smartphone project same thing.
>
>I just went to "Tools->Options->Directories". Under the Pocket PC 2003
>platform, there are three entries:
>C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\Include\emulator
>C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\mfc\include
>C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\atl\include
>Winver.h is in the first directory, so why wont it open? If I move winver.h
>to the project directory, then I get another error that it cannot find
>aygshell.h. If I copy that to the project folder, I get another error, and on
>and on. It really does sound like an include problem, but the directory is
>there.

I have wasted a lot of time moving header files around, so I
recommend not doing it. It tends to snowball (trigger several new
error messages for each one suppressed).

I see a copy of winver in each of the CPU-specific "include" folders
(include\armv4, include\emulator). The list you see in
Tools->Options->Directories should depend on platform and CPU. In
particular, you should see only emulator folders for the emulator list
and only ARMV4 folders for the ARMV4 list. (This paragraph is
_definitely_ not as clear as I would like, but each of several
attempts I made to clarify were even muddier.)

I've never quite understood the difference between "" and <> in
references to header (include) files. Does "" mean look _only_ in
current (caller's) folder, or first in current and then in "system"?
Does <> mean look only in "system"?

>
>Another thing, if in the workspace viewer, I click the resources tab and try
>to expand the resources folder, I get the same thing. Error RC1015 cannot
>open winver.h. What is wrong?

I'm not so surprised that the resource compiler and resource editor
suffer from the same problem.

What happens if you try to compile just a source (c or cpp) file? If
that works, then the problem is somewhat limited to resources.

At least for diagnostics, you might want to try adding the appropriate
"CPU folder" (see above) to the "Additional resource include
directories" in Project->Settings->Resources. You should add only one
folder for each target (CPU/platform).


>
>"Kerstin Pirrung" wrote:
>
>> Hi!
>>
>> Basically it looks like your "Include Directories" list is incomplete. One
>> of the drawbacks of eVC is that it does not set those lists all that
>> intelligently (one of the drawbacks of VS 2005 is that it won't tell me
>> voluntarily how and why it set said lists) - so just try and check "Tools->
>> Options->Directories" as well as yur INCLUDEDIRS.
>>
>> Greetings,
>>
>> Kerstin
>>
>> =?Utf-8?B?Sm9uYXRoYW4gS2luZw==?=
>> <JonathanKing@discussions.microsoft.com> wrote in
>> news:A613317B-4252-4B77-8A62-9B5E59B866AB@microsoft.com:
>>
>> > Ok, a google search pulls up nothing. Basically, I just installed
>> > eVC++ 4.0, the PPC 2003 sdk, and SP4. Cannot get anything to build. If
>> > I create a new PPC 2003 simple CE app or hello world app then attempt
>> > to build, it will not work. I get the following error:
>> >
>> > Compiling resources...
>> > C:\Documents and Settings\Paul King\My
>> > Documents\Dev\HelloWorld\newres.h(32)
>> >: fatal error RC1015: cannot open include file 'winver.h'.
>> > Error executing rc.exe.
>> >
>> > A google search pulls up many people asking this question, but no
>> > solutions. Can somebody please help?
>>
>>

-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).

Robert E. Zaret, eMVP
PenFact, Inc.
20 Park Plaza, Suite 478
Boston, MA 02116
www.penfact.com

Re: eVC++ 4.0 SP4, Cannot build anything. Please help by JonathanKing

JonathanKing
Tue Apr 04 18:05:02 CDT 2006

I cannot compile because then I get another error because
'emulatorDbg/HelloWorld.pch' does not exist. I'm guessing that that file is
dependent on the resources. I exported the makefile, but I really don't know
what to look for.

Something interesting, if I copy everything from the correct include folder
into my project directory OR (what you suggested) just add the directory to
the settings, I get past one hurdle. It successfully compiles the resources,
and I am now able to expand the resources in the workspace viewer. Now, the
build stops here:
Compiling resources...
Compiling...
StdAfx.cpp
Compiling...
HelloWorld.cpp
C:\Documents and Settings\Paul King\My
Documents\Dev\proj\HelloWorld\HelloWorld.cpp(7) : fatal error C1083: Cannot
open include file: 'aygshell.h': No such file or directory
Error executing cl.exe

It looks like it just won't look in the directories that it is supposed to.
I installed eVC on my other computer, and it works fine. I need eVC on this
computer though, because the other is extremely slowww. I'm wondering if it
is due to a bad install. I had Visual Studio 2005 developer preview 2
installed. Could that have affected it? I just got rid of it, and I am about
to reinstall eVC.

"r_z_aret@pen_fact.com" wrote:

> On Mon, 3 Apr 2006 14:59:03 -0700, Jonathan King
> <JonathanKing@discussions.microsoft.com> wrote:
>
> >I am creating a new Pocket PC 2003 application, building for WCE ARMV4 and
> >WCE emulator. The I select typical hellow world application or a simple
> >WinCE application. Either one gives me the same error. I just tried with a
> >smartphone project same thing.
> >
> >I just went to "Tools->Options->Directories". Under the Pocket PC 2003
> >platform, there are three entries:
> >C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\Include\emulator
> >C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\mfc\include
> >C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\atl\include
> >Winver.h is in the first directory, so why wont it open? If I move winver.h
> >to the project directory, then I get another error that it cannot find
> >aygshell.h. If I copy that to the project folder, I get another error, and on
> >and on. It really does sound like an include problem, but the directory is
> >there.
>
> I have wasted a lot of time moving header files around, so I
> recommend not doing it. It tends to snowball (trigger several new
> error messages for each one suppressed).
>
> I see a copy of winver in each of the CPU-specific "include" folders
> (include\armv4, include\emulator). The list you see in
> Tools->Options->Directories should depend on platform and CPU. In
> particular, you should see only emulator folders for the emulator list
> and only ARMV4 folders for the ARMV4 list. (This paragraph is
> _definitely_ not as clear as I would like, but each of several
> attempts I made to clarify were even muddier.)
>
> I've never quite understood the difference between "" and <> in
> references to header (include) files. Does "" mean look _only_ in
> current (caller's) folder, or first in current and then in "system"?
> Does <> mean look only in "system"?
>
> >
> >Another thing, if in the workspace viewer, I click the resources tab and try
> >to expand the resources folder, I get the same thing. Error RC1015 cannot
> >open winver.h. What is wrong?
>
> I'm not so surprised that the resource compiler and resource editor
> suffer from the same problem.
>
> What happens if you try to compile just a source (c or cpp) file? If
> that works, then the problem is somewhat limited to resources.
>
> At least for diagnostics, you might want to try adding the appropriate
> "CPU folder" (see above) to the "Additional resource include
> directories" in Project->Settings->Resources. You should add only one
> folder for each target (CPU/platform).
>
>
> >
> >"Kerstin Pirrung" wrote:
> >
> >> Hi!
> >>
> >> Basically it looks like your "Include Directories" list is incomplete. One
> >> of the drawbacks of eVC is that it does not set those lists all that
> >> intelligently (one of the drawbacks of VS 2005 is that it won't tell me
> >> voluntarily how and why it set said lists) - so just try and check "Tools->
> >> Options->Directories" as well as yur INCLUDEDIRS.
> >>
> >> Greetings,
> >>
> >> Kerstin
> >>
> >> =?Utf-8?B?Sm9uYXRoYW4gS2luZw==?=
> >> <JonathanKing@discussions.microsoft.com> wrote in
> >> news:A613317B-4252-4B77-8A62-9B5E59B866AB@microsoft.com:
> >>
> >> > Ok, a google search pulls up nothing. Basically, I just installed
> >> > eVC++ 4.0, the PPC 2003 sdk, and SP4. Cannot get anything to build. If
> >> > I create a new PPC 2003 simple CE app or hello world app then attempt
> >> > to build, it will not work. I get the following error:
> >> >
> >> > Compiling resources...
> >> > C:\Documents and Settings\Paul King\My
> >> > Documents\Dev\HelloWorld\newres.h(32)
> >> >: fatal error RC1015: cannot open include file 'winver.h'.
> >> > Error executing rc.exe.
> >> >
> >> > A google search pulls up many people asking this question, but no
> >> > solutions. Can somebody please help?
> >>
> >>
>
> -----------------------------------------
> To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).
>
> Robert E. Zaret, eMVP
> PenFact, Inc.
> 20 Park Plaza, Suite 478
> Boston, MA 02116
> www.penfact.com
>

Re: eVC++ 4.0 SP4, Cannot build anything. Please help by JonathanKing

JonathanKing
Tue Apr 04 20:13:02 CDT 2006

I just completely removed eVC and VS, then installed eVC again. Same error.
The resources compile if I include the folder in the resources tab. What
folder do I need to add, and how do I add it to get past this next error?

Thanks to everyone for the continuing help.

"Jonathan King" wrote:

> I cannot compile because then I get another error because
> 'emulatorDbg/HelloWorld.pch' does not exist. I'm guessing that that file is
> dependent on the resources. I exported the makefile, but I really don't know
> what to look for.
>
> Something interesting, if I copy everything from the correct include folder
> into my project directory OR (what you suggested) just add the directory to
> the settings, I get past one hurdle. It successfully compiles the resources,
> and I am now able to expand the resources in the workspace viewer. Now, the
> build stops here:
> Compiling resources...
> Compiling...
> StdAfx.cpp
> Compiling...
> HelloWorld.cpp
> C:\Documents and Settings\Paul King\My
> Documents\Dev\proj\HelloWorld\HelloWorld.cpp(7) : fatal error C1083: Cannot
> open include file: 'aygshell.h': No such file or directory
> Error executing cl.exe
>
> It looks like it just won't look in the directories that it is supposed to.
> I installed eVC on my other computer, and it works fine. I need eVC on this
> computer though, because the other is extremely slowww. I'm wondering if it
> is due to a bad install. I had Visual Studio 2005 developer preview 2
> installed. Could that have affected it? I just got rid of it, and I am about
> to reinstall eVC.
>
> "r_z_aret@pen_fact.com" wrote:
>
> > On Mon, 3 Apr 2006 14:59:03 -0700, Jonathan King
> > <JonathanKing@discussions.microsoft.com> wrote:
> >
> > >I am creating a new Pocket PC 2003 application, building for WCE ARMV4 and
> > >WCE emulator. The I select typical hellow world application or a simple
> > >WinCE application. Either one gives me the same error. I just tried with a
> > >smartphone project same thing.
> > >
> > >I just went to "Tools->Options->Directories". Under the Pocket PC 2003
> > >platform, there are three entries:
> > >C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\Include\emulator
> > >C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\mfc\include
> > >C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\atl\include
> > >Winver.h is in the first directory, so why wont it open? If I move winver.h
> > >to the project directory, then I get another error that it cannot find
> > >aygshell.h. If I copy that to the project folder, I get another error, and on
> > >and on. It really does sound like an include problem, but the directory is
> > >there.
> >
> > I have wasted a lot of time moving header files around, so I
> > recommend not doing it. It tends to snowball (trigger several new
> > error messages for each one suppressed).
> >
> > I see a copy of winver in each of the CPU-specific "include" folders
> > (include\armv4, include\emulator). The list you see in
> > Tools->Options->Directories should depend on platform and CPU. In
> > particular, you should see only emulator folders for the emulator list
> > and only ARMV4 folders for the ARMV4 list. (This paragraph is
> > _definitely_ not as clear as I would like, but each of several
> > attempts I made to clarify were even muddier.)
> >
> > I've never quite understood the difference between "" and <> in
> > references to header (include) files. Does "" mean look _only_ in
> > current (caller's) folder, or first in current and then in "system"?
> > Does <> mean look only in "system"?
> >
> > >
> > >Another thing, if in the workspace viewer, I click the resources tab and try
> > >to expand the resources folder, I get the same thing. Error RC1015 cannot
> > >open winver.h. What is wrong?
> >
> > I'm not so surprised that the resource compiler and resource editor
> > suffer from the same problem.
> >
> > What happens if you try to compile just a source (c or cpp) file? If
> > that works, then the problem is somewhat limited to resources.
> >
> > At least for diagnostics, you might want to try adding the appropriate
> > "CPU folder" (see above) to the "Additional resource include
> > directories" in Project->Settings->Resources. You should add only one
> > folder for each target (CPU/platform).
> >
> >
> > >
> > >"Kerstin Pirrung" wrote:
> > >
> > >> Hi!
> > >>
> > >> Basically it looks like your "Include Directories" list is incomplete. One
> > >> of the drawbacks of eVC is that it does not set those lists all that
> > >> intelligently (one of the drawbacks of VS 2005 is that it won't tell me
> > >> voluntarily how and why it set said lists) - so just try and check "Tools->
> > >> Options->Directories" as well as yur INCLUDEDIRS.
> > >>
> > >> Greetings,
> > >>
> > >> Kerstin
> > >>
> > >> =?Utf-8?B?Sm9uYXRoYW4gS2luZw==?=
> > >> <JonathanKing@discussions.microsoft.com> wrote in
> > >> news:A613317B-4252-4B77-8A62-9B5E59B866AB@microsoft.com:
> > >>
> > >> > Ok, a google search pulls up nothing. Basically, I just installed
> > >> > eVC++ 4.0, the PPC 2003 sdk, and SP4. Cannot get anything to build. If
> > >> > I create a new PPC 2003 simple CE app or hello world app then attempt
> > >> > to build, it will not work. I get the following error:
> > >> >
> > >> > Compiling resources...
> > >> > C:\Documents and Settings\Paul King\My
> > >> > Documents\Dev\HelloWorld\newres.h(32)
> > >> >: fatal error RC1015: cannot open include file 'winver.h'.
> > >> > Error executing rc.exe.
> > >> >
> > >> > A google search pulls up many people asking this question, but no
> > >> > solutions. Can somebody please help?
> > >>
> > >>
> >
> > -----------------------------------------
> > To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).
> >
> > Robert E. Zaret, eMVP
> > PenFact, Inc.
> > 20 Park Plaza, Suite 478
> > Boston, MA 02116
> > www.penfact.com
> >

Re: eVC++ 4.0 SP4, Cannot build anything. Please help by Kerstin

Kerstin
Wed Apr 05 06:07:38 CDT 2006

=?Utf-8?B?Sm9uYXRoYW4gS2luZw==?=
<JonathanKing@discussions.microsoft.com> wrote in
news:E4D2BB1E-3061-4029-8195-DEE9531D8DA5@microsoft.com:

> I just completely removed eVC and VS, then installed eVC again. Same
> error. The resources compile if I include the folder in the resources
> tab. What folder do I need to add, and how do I add it to get past
> this next error?
>

Did you declare the headers as "external dependencies" in the "files"
tab? Maybe that could help you...
But still, it shouldn't be necessary; there must be another snag in it.

Try having a look at your environmentals (NOT eVC- or VS internal, but
system-wide).

Or can you maybe post the makefile? Or your command lines? That might
give us a clue.

Greetings,

Kerstin





> Thanks to everyone for the continuing help.
>
> "Jonathan King" wrote:
>
>> I cannot compile because then I get another error because
>> 'emulatorDbg/HelloWorld.pch' does not exist. I'm guessing that that
>> file is dependent on the resources. I exported the makefile, but I
>> really don't know what to look for.
>>
>> Something interesting, if I copy everything from the correct include
>> folder into my project directory OR (what you suggested) just add the
>> directory to the settings, I get past one hurdle. It successfully
>> compiles the resources, and I am now able to expand the resources in
>> the workspace viewer. Now, the build stops here:
>> Compiling resources...
>> Compiling...
>> StdAfx.cpp
>> Compiling...
>> HelloWorld.cpp
>> C:\Documents and Settings\Paul King\My
>> Documents\Dev\proj\HelloWorld\HelloWorld.cpp(7) : fatal error C1083:
>> Cannot open include file: 'aygshell.h': No such file or directory
>> Error executing cl.exe
>>
>> It looks like it just won't look in the directories that it is
>> supposed to. I installed eVC on my other computer, and it works fine.
>> I need eVC on this computer though, because the other is extremely
>> slowww. I'm wondering if it is due to a bad install. I had Visual
>> Studio 2005 developer preview 2 installed. Could that have affected
>> it? I just got rid of it, and I am about to reinstall eVC.
>>
>> "r_z_aret@pen_fact.com" wrote:
>>
>> > On Mon, 3 Apr 2006 14:59:03 -0700, Jonathan King
>> > <JonathanKing@discussions.microsoft.com> wrote:
>> >
>> > >I am creating a new Pocket PC 2003 application, building for WCE
>> > >ARMV4 and WCE emulator. The I select typical hellow world
>> > >application or a simple WinCE application. Either one gives me the
>> > >same error. I just tried with a smartphone project same thing.
>> > >
>> > >I just went to "Tools->Options->Directories". Under the Pocket PC
>> > >2003 platform, there are three entries:
>> > >C:\Program Files\Windows CE Tools\wce420\POCKET PC
>> > >2003\Include\emulator C:\Program Files\Windows CE
>> > >Tools\wce420\POCKET PC 2003\mfc\include C:\Program Files\Windows
>> > >CE Tools\wce420\POCKET PC 2003\atl\include Winver.h is in the
>> > >first directory, so why wont it open? If I move winver.h to the
>> > >project directory, then I get another error that it cannot find
>> > >aygshell.h. If I copy that to the project folder, I get another
>> > >error, and on and on. It really does sound like an include
>> > >problem, but the directory is there.
>> >
>> > I have wasted a lot of time moving header files around, so I
>> > recommend not doing it. It tends to snowball (trigger several new
>> > error messages for each one suppressed).
>> >
>> > I see a copy of winver in each of the CPU-specific "include"
>> > folders (include\armv4, include\emulator). The list you see in
>> > Tools->Options->Directories should depend on platform and CPU. In
>> > particular, you should see only emulator folders for the emulator
>> > list and only ARMV4 folders for the ARMV4 list. (This paragraph is
>> > _definitely_ not as clear as I would like, but each of several
>> > attempts I made to clarify were even muddier.)
>> >
>> > I've never quite understood the difference between "" and <> in
>> > references to header (include) files. Does "" mean look _only_ in
>> > current (caller's) folder, or first in current and then in
>> > "system"? Does <> mean look only in "system"?
>> >
>> > >
>> > >Another thing, if in the workspace viewer, I click the resources
>> > >tab and try to expand the resources folder, I get the same thing.
>> > >Error RC1015 cannot open winver.h. What is wrong?
>> >
>> > I'm not so surprised that the resource compiler and resource editor
>> > suffer from the same problem.
>> >
>> > What happens if you try to compile just a source (c or cpp) file?
>> > If that works, then the problem is somewhat limited to resources.
>> >
>> > At least for diagnostics, you might want to try adding the
>> > appropriate "CPU folder" (see above) to the "Additional resource
>> > include directories" in Project->Settings->Resources. You should
>> > add only one folder for each target (CPU/platform).
>> >
>> >
>> > >
>> > >"Kerstin Pirrung" wrote:
>> > >
>> > >> Hi!
>> > >>
>> > >> Basically it looks like your "Include Directories" list is
>> > >> incomplete. One of the drawbacks of eVC is that it does not set
>> > >> those lists all that intelligently (one of the drawbacks of VS
>> > >> 2005 is that it won't tell me voluntarily how and why it set
>> > >> said lists) - so just try and check "Tools->
>> > >> Options->Directories" as well as yur INCLUDEDIRS.
>> > >>
>> > >> Greetings,
>> > >>
>> > >> Kerstin
>> > >>
>> > >> =?Utf-8?B?Sm9uYXRoYW4gS2luZw==?=
>> > >> <JonathanKing@discussions.microsoft.com> wrote in
>> > >> news:A613317B-4252-4B77-8A62-9B5E59B866AB@microsoft.com:
>> > >>
>> > >> > Ok, a google search pulls up nothing. Basically, I just
>> > >> > installed eVC++ 4.0, the PPC 2003 sdk, and SP4. Cannot get
>> > >> > anything to build. If I create a new PPC 2003 simple CE app or
>> > >> > hello world app then attempt to build, it will not work. I get
>> > >> > the following error:
>> > >> >
>> > >> > Compiling resources...
>> > >> > C:\Documents and Settings\Paul King\My
>> > >> > Documents\Dev\HelloWorld\newres.h(32)
>> > >> >: fatal error RC1015: cannot open include file 'winver.h'.
>> > >> > Error executing rc.exe.
>> > >> >
>> > >> > A google search pulls up many people asking this question, but
>> > >> > no solutions. Can somebody please help?
>> > >>
>> > >>
>> >
>> > -----------------------------------------
>> > To reply to me, remove the underscores (_) from my email address
>> > (and please indicate which newsgroup and message).
>> >
>> > Robert E. Zaret, eMVP
>> > PenFact, Inc.
>> > 20 Park Plaza, Suite 478
>> > Boston, MA 02116
>> > www.penfact.com
>> >
>


Re: eVC++ 4.0 SP4, Cannot build anything. Please help by JonathanKing

JonathanKing
Wed Apr 05 15:39:09 CDT 2006

Here is the contents of the dependencies:

# eMbedded Visual C++ Dependency File, included by HelloWorld.vcn

!IF "$(CFG)" == "HelloWorld - Win32 (WCE emulator) Release"

.\HelloWorld.cpp : \
".\HelloWorld.h"\
".\StdAfx.h"\
{$(INCLUDE)}"sipapi.h"\


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE emulator) Debug"

.\HelloWorld.cpp : \
".\HelloWorld.h"\
".\StdAfx.h"\
{$(INCLUDE)}"sipapi.h"\


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE ARMV4) Release"

.\HelloWorld.cpp : \
".\HelloWorld.h"\
".\StdAfx.h"\


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE ARMV4) Debug"

.\HelloWorld.cpp : \
".\HelloWorld.h"\
".\StdAfx.h"\


!ENDIF

!IF "$(CFG)" == "HelloWorld - Win32 (WCE emulator) Release"

.\HelloWorld.rc : \
".\HelloWorld.ico"\
".\newres.h"\


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE emulator) Debug"

.\HelloWorld.rc : \
".\HelloWorld.ico"\
".\newres.h"\


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE ARMV4) Release"

.\HelloWorld.rc : \
".\HelloWorld.ico"\
".\newres.h"\


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE ARMV4) Debug"

.\HelloWorld.rc : \
".\HelloWorld.ico"\
".\newres.h"\


!ENDIF

!IF "$(CFG)" == "HelloWorld - Win32 (WCE emulator) Release"

.\StdAfx.cpp : \
".\StdAfx.h"\


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE emulator) Debug"

.\StdAfx.cpp : \
".\StdAfx.h"\


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE ARMV4) Release"

.\StdAfx.cpp : \
".\StdAfx.h"\


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE ARMV4) Debug"

.\StdAfx.cpp : \
".\StdAfx.h"\


!ENDIF

Re: eVC++ 4.0 SP4, Cannot build anything. Please help by JonathanKing

JonathanKing
Wed Apr 05 15:59:01 CDT 2006

Make file:

# Microsoft eMbedded Visual Tools Generated NMAKE File, Based on
HelloWorld.vcp
!IF "$(CFG)" == ""
CFG=HelloWorld - Win32 (WCE emulator) Debug
!MESSAGE No configuration specified. Defaulting to HelloWorld - Win32 (WCE
emulator) Debug.
!ENDIF

!IF "$(CESubsystem)" == ""
CESubsystem=windowsce,2.0
!MESSAGE Variable CESubsystem not specified. Defaulting to windowsce,2.11
!ENDIF

!IF "$(CEVersion)" == ""
CEVersion=200
!MESSAGE Variable CEVersion not specified. Defaulting to 211
!ENDIF

!IF $(CEVersion) < 201
CECrt=L
CECrtDebug=Ld
CECrtMT=T
CECrtMTDebug=Td
CENoDefaultLib=corelibc.lib
CEx86Corelibc=
!ELSE
CECrt=C
CECrtDebug=C
CECrtMT=C
CECrtMTDebug=C
CENoDefaultLib=libc.lib /nodefaultlib:libcd.lib /nodefaultlib:libcmt.lib
/nodefaultlib:libcmtd.lib /nodefaultlib:msvcrt.lib /nodefaultlib:msvcrtd.lib
CEx86Corelibc=corelibc.lib
!ENDIF

!IF "$(CE_PLATFORM)"==""
CePlatform=WIN32_PLATFORM_UNKNOWN
!ELSE
CePlatform=$(CE_PLATFORM)
!ENDIF

!IF "$(CFG)" != "HelloWorld - Win32 (WCE emulator) Release" && "$(CFG)" !=
"HelloWorld - Win32 (WCE emulator) Debug" && "$(CFG)" != "HelloWorld - Win32
(WCE ARMV4) Release" && "$(CFG)" != "HelloWorld - Win32 (WCE ARMV4) Debug"
!MESSAGE Invalid configuration "$(CFG)" specified.
!MESSAGE You can specify a configuration when running NMAKE
!MESSAGE by defining the macro CFG on the command line. For example:
!MESSAGE
!MESSAGE NMAKE /f "HelloWorld.vcn" CFG="HelloWorld - Win32 (WCE emulator)
Debug"
!MESSAGE
!MESSAGE Possible choices for configuration are:
!MESSAGE
!MESSAGE "HelloWorld - Win32 (WCE emulator) Release" (based on "Win32 (WCE
emulator) Application")
!MESSAGE "HelloWorld - Win32 (WCE emulator) Debug" (based on "Win32 (WCE
emulator) Application")
!MESSAGE "HelloWorld - Win32 (WCE ARMV4) Release" (based on "Win32 (WCE
ARMV4) Application")
!MESSAGE "HelloWorld - Win32 (WCE ARMV4) Debug" (based on "Win32 (WCE ARMV4)
Application")
!MESSAGE
!ERROR An invalid configuration is specified.
!ENDIF

!IF "$(OS)" == "Windows_NT"
NULL=
!ELSE
NULL=nul
!ENDIF

!IF "$(CFG)" == "HelloWorld - Win32 (WCE emulator) Release"

OUTDIR=.\emulatorRel
INTDIR=.\emulatorRel
# Begin Custom Macros
OutDir=.\emulatorRel
# End Custom Macros

ALL : "$(OUTDIR)\HelloWorld.exe"


CLEAN :
-@erase "$(INTDIR)\HelloWorld.obj"
-@erase "$(INTDIR)\HelloWorld.pch"
-@erase "$(INTDIR)\HelloWorld.res"
-@erase "$(INTDIR)\StdAfx.obj"
-@erase "$(OUTDIR)\HelloWorld.exe"

"$(OUTDIR)" :
if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"

RSC=rc.exe
RSC_PROJ=/l 0x409 /fo"$(INTDIR)\HelloWorld.res" /d UNDER_CE=$(CEVersion) /d
_WIN32_WCE=$(CEVersion) /d "UNICODE" /d "_UNICODE" /d "NDEBUG" /d
"$(CePlatform)" /d "_X86_" /d "x86" /d "_i386_" /r
CPP=cl.exe
CPP_PROJ=/nologo /W3 /D _WIN32_WCE=$(CEVersion) /D "$(CePlatform)" /D
"_i386_" /D UNDER_CE=$(CEVersion) /D "i_386_" /D "UNICODE" /D "_UNICODE" /D
"_X86_" /D "x86" /D "NDEBUG" /Fp"$(INTDIR)\HelloWorld.pch" /Yu"stdafx.h"
/Fo"$(INTDIR)\\" /Gs8192 /GF /O2 /c

.c{$(INTDIR)}.obj::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cpp{$(INTDIR)}.obj::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cxx{$(INTDIR)}.obj::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.c{$(INTDIR)}.sbr::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cpp{$(INTDIR)}.sbr::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cxx{$(INTDIR)}.sbr::
$(CPP) @<<
$(CPP_PROJ) $<
<<

MTL=midl.exe
MTL_PROJ=/nologo /D "NDEBUG" /mktyplib203 /o "NUL" /win32
BSC32=bscmake.exe
BSC32_FLAGS=/nologo /o"$(OUTDIR)\HelloWorld.bsc"
BSC32_SBRS= \

LINK32=link.exe
LINK32_FLAGS=commctrl.lib coredll.lib $(CEx86Corelibc) aygshell.lib /nologo
/base:"0x00010000" /stack:0x10000,0x1000 /entry:"WinMainCRTStartup"
/incremental:no /pdb:"$(OUTDIR)\HelloWorld.pdb" /nodefaultlib:"OLDNAMES.lib"
/nodefaultlib:$(CENoDefaultLib) /out:"$(OUTDIR)\HelloWorld.exe"
/subsystem:$(CESubsystem) /MACHINE:IX86
LINK32_OBJS= \
"$(INTDIR)\HelloWorld.obj" \
"$(INTDIR)\StdAfx.obj" \
"$(INTDIR)\HelloWorld.res"

"$(OUTDIR)\HelloWorld.exe" : "$(OUTDIR)" $(DEF_FILE) $(LINK32_OBJS)
$(LINK32) @<<
$(LINK32_FLAGS) $(LINK32_OBJS)
<<

!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE emulator) Debug"

OUTDIR=.\emulatorDbg
INTDIR=.\emulatorDbg
# Begin Custom Macros
OutDir=.\emulatorDbg
# End Custom Macros

ALL : "$(OUTDIR)\HelloWorld.exe"


CLEAN :
-@erase "$(INTDIR)\HelloWorld.obj"
-@erase "$(INTDIR)\HelloWorld.pch"
-@erase "$(INTDIR)\HelloWorld.res"
-@erase "$(INTDIR)\StdAfx.obj"
-@erase "$(INTDIR)\vc60.pdb"
-@erase "$(OUTDIR)\HelloWorld.exe"
-@erase "$(OUTDIR)\HelloWorld.ilk"
-@erase "$(OUTDIR)\HelloWorld.pdb"

"$(OUTDIR)" :
if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"

RSC=rc.exe
RSC_PROJ=/l 0x409 /fo"$(INTDIR)\HelloWorld.res" /d "$(CePlatform)" /d
UNDER_CE=$(CEVersion) /d _WIN32_WCE=$(CEVersion) /d "UNICODE" /d "_UNICODE"
/d "DEBUG" /d "_X86_" /d "x86" /d "_i386_" /r
CPP=cl.exe
CPP_PROJ=/nologo /W3 /Zi /Od /D "DEBUG" /D "_i386_" /D UNDER_CE=$(CEVersion)
/D _WIN32_WCE=$(CEVersion) /D "$(CePlatform)" /D "i_386_" /D "UNICODE" /D
"_UNICODE" /D "_X86_" /D "x86" /Fp"$(INTDIR)\HelloWorld.pch" /Yu"stdafx.h"
/Fo"$(INTDIR)\\" /Fd"$(INTDIR)\\" /Gs8192 /GF /c

.c{$(INTDIR)}.obj::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cpp{$(INTDIR)}.obj::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cxx{$(INTDIR)}.obj::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.c{$(INTDIR)}.sbr::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cpp{$(INTDIR)}.sbr::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cxx{$(INTDIR)}.sbr::
$(CPP) @<<
$(CPP_PROJ) $<
<<

MTL=midl.exe
MTL_PROJ=/nologo /D "_DEBUG" /mktyplib203 /o "NUL" /win32
BSC32=bscmake.exe
BSC32_FLAGS=/nologo /o"$(OUTDIR)\HelloWorld.bsc"
BSC32_SBRS= \

LINK32=link.exe
LINK32_FLAGS=commctrl.lib coredll.lib $(CEx86Corelibc) aygshell.lib /nologo
/base:"0x00010000" /stack:0x10000,0x1000 /entry:"WinMainCRTStartup"
/incremental:yes /pdb:"$(OUTDIR)\HelloWorld.pdb" /debug
/nodefaultlib:"OLDNAMES.lib" /nodefaultlib:$(CENoDefaultLib)
/out:"$(OUTDIR)\HelloWorld.exe" /subsystem:$(CESubsystem) /MACHINE:IX86
LINK32_OBJS= \
"$(INTDIR)\HelloWorld.obj" \
"$(INTDIR)\StdAfx.obj" \
"$(INTDIR)\HelloWorld.res"

"$(OUTDIR)\HelloWorld.exe" : "$(OUTDIR)" $(DEF_FILE) $(LINK32_OBJS)
$(LINK32) @<<
$(LINK32_FLAGS) $(LINK32_OBJS)
<<

!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE ARMV4) Release"

OUTDIR=.\ARMV4Rel
INTDIR=.\ARMV4Rel
# Begin Custom Macros
OutDir=.\ARMV4Rel
# End Custom Macros

ALL : "$(OUTDIR)\HelloWorld.exe"


CLEAN :
-@erase "$(INTDIR)\HelloWorld.obj"
-@erase "$(INTDIR)\HelloWorld.pch"
-@erase "$(INTDIR)\HelloWorld.res"
-@erase "$(INTDIR)\StdAfx.obj"
-@erase "$(OUTDIR)\HelloWorld.exe"

"$(OUTDIR)" :
if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"

RSC=rc.exe
RSC_PROJ=/l 0x409 /fo"$(INTDIR)\HelloWorld.res" /d UNDER_CE=$(CEVersion) /d
_WIN32_WCE=$(CEVersion) /d "NDEBUG" /d "UNICODE" /d "_UNICODE" /d
"$(CePlatform)" /d "ARM" /d "_ARM_" /d "ARMV4" /r
CPP=clarm.exe
CPP_PROJ=/nologo /W3 /D _WIN32_WCE=$(CEVersion) /D "$(CePlatform)" /D "ARM"
/D "_ARM_" /D "ARMV4" /D UNDER_CE=$(CEVersion) /D "UNICODE" /D "_UNICODE" /D
"NDEBUG" /Fp"$(INTDIR)\HelloWorld.pch" /Yu"stdafx.h" /Fo"$(INTDIR)\\" /O2
/M$(CECrtMT) /c

.c{$(INTDIR)}.obj::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cpp{$(INTDIR)}.obj::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cxx{$(INTDIR)}.obj::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.c{$(INTDIR)}.sbr::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cpp{$(INTDIR)}.sbr::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cxx{$(INTDIR)}.sbr::
$(CPP) @<<
$(CPP_PROJ) $<
<<

MTL=midl.exe
MTL_PROJ=/nologo /D "NDEBUG" /mktyplib203 /o "NUL" /win32
BSC32=bscmake.exe
BSC32_FLAGS=/nologo /o"$(OUTDIR)\HelloWorld.bsc"
BSC32_SBRS= \

LINK32=link.exe
LINK32_FLAGS=commctrl.lib coredll.lib aygshell.lib /nologo
/base:"0x00010000" /stack:0x10000,0x1000 /entry:"WinMainCRTStartup"
/incremental:no /pdb:"$(OUTDIR)\HelloWorld.pdb"
/nodefaultlib:"$(CENoDefaultLib)" /out:"$(OUTDIR)\HelloWorld.exe"
/subsystem:$(CESubsystem) /align:"4096" /MACHINE:ARM
LINK32_OBJS= \
"$(INTDIR)\HelloWorld.obj" \
"$(INTDIR)\StdAfx.obj" \
"$(INTDIR)\HelloWorld.res"

"$(OUTDIR)\HelloWorld.exe" : "$(OUTDIR)" $(DEF_FILE) $(LINK32_OBJS)
$(LINK32) @<<
$(LINK32_FLAGS) $(LINK32_OBJS)
<<

!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE ARMV4) Debug"

OUTDIR=.\ARMV4Dbg
INTDIR=.\ARMV4Dbg
# Begin Custom Macros
OutDir=.\ARMV4Dbg
# End Custom Macros

ALL : "$(OUTDIR)\HelloWorld.exe"


CLEAN :
-@erase "$(INTDIR)\HelloWorld.obj"
-@erase "$(INTDIR)\HelloWorld.pch"
-@erase "$(INTDIR)\HelloWorld.res"
-@erase "$(INTDIR)\StdAfx.obj"
-@erase "$(INTDIR)\vc60.pdb"
-@erase "$(OUTDIR)\HelloWorld.exe"
-@erase "$(OUTDIR)\HelloWorld.ilk"
-@erase "$(OUTDIR)\HelloWorld.pdb"

"$(OUTDIR)" :
if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"

RSC=rc.exe
RSC_PROJ=/l 0x409 /fo"$(INTDIR)\HelloWorld.res" /d UNDER_CE=$(CEVersion) /d
_WIN32_WCE=$(CEVersion) /d "DEBUG" /d "UNICODE" /d "_UNICODE" /d
"$(CePlatform)" /d "ARM" /d "_ARM_" /d "ARMV4" /r
CPP=clarm.exe
CPP_PROJ=/nologo /W3 /Zi /Od /D "DEBUG" /D "ARM" /D "_ARM_" /D "ARMV4" /D
UNDER_CE=$(CEVersion) /D _WIN32_WCE=$(CEVersion) /D "$(CePlatform)" /D
"UNICODE" /D "_UNICODE" /Fp"$(INTDIR)\HelloWorld.pch" /Yu"stdafx.h"
/Fo"$(INTDIR)\\" /Fd"$(INTDIR)\\" /M$(CECrtMTDebug) /c

.c{$(INTDIR)}.obj::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cpp{$(INTDIR)}.obj::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cxx{$(INTDIR)}.obj::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.c{$(INTDIR)}.sbr::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cpp{$(INTDIR)}.sbr::
$(CPP) @<<
$(CPP_PROJ) $<
<<

.cxx{$(INTDIR)}.sbr::
$(CPP) @<<
$(CPP_PROJ) $<
<<

MTL=midl.exe
MTL_PROJ=/nologo /D "_DEBUG" /mktyplib203 /o "NUL" /win32
BSC32=bscmake.exe
BSC32_FLAGS=/nologo /o"$(OUTDIR)\HelloWorld.bsc"
BSC32_SBRS= \

LINK32=link.exe
LINK32_FLAGS=commctrl.lib coredll.lib aygshell.lib /nologo
/base:"0x00010000" /stack:0x10000,0x1000 /entry:"WinMainCRTStartup"
/incremental:yes /pdb:"$(OUTDIR)\HelloWorld.pdb" /debug
/nodefaultlib:"$(CENoDefaultLib)" /out:"$(OUTDIR)\HelloWorld.exe"
/subsystem:$(CESubsystem) /align:"4096" /MACHINE:ARM
LINK32_OBJS= \
"$(INTDIR)\HelloWorld.obj" \
"$(INTDIR)\StdAfx.obj" \
"$(INTDIR)\HelloWorld.res"

"$(OUTDIR)\HelloWorld.exe" : "$(OUTDIR)" $(DEF_FILE) $(LINK32_OBJS)
$(LINK32) @<<
$(LINK32_FLAGS) $(LINK32_OBJS)
<<

!ENDIF


!IF "$(NO_EXTERNAL_DEPS)" != "1"
!IF EXISTS("HelloWorld.dep")
!INCLUDE "HelloWorld.dep"
!ELSE
!MESSAGE Warning: cannot find "HelloWorld.dep"
!ENDIF
!ENDIF


!IF "$(CFG)" == "HelloWorld - Win32 (WCE emulator) Release" || "$(CFG)" ==
"HelloWorld - Win32 (WCE emulator) Debug" || "$(CFG)" == "HelloWorld - Win32
(WCE ARMV4) Release" || "$(CFG)" == "HelloWorld - Win32 (WCE ARMV4) Debug"
SOURCE=.\HelloWorld.cpp

!IF "$(CFG)" == "HelloWorld - Win32 (WCE emulator) Release"


"$(INTDIR)\HelloWorld.obj" : $(SOURCE) "$(INTDIR)" "$(INTDIR)\HelloWorld.pch"


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE emulator) Debug"


"$(INTDIR)\HelloWorld.obj" : $(SOURCE) "$(INTDIR)" "$(INTDIR)\HelloWorld.pch"


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE ARMV4) Release"


"$(INTDIR)\HelloWorld.obj" : $(SOURCE) "$(INTDIR)" "$(INTDIR)\HelloWorld.pch"


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE ARMV4) Debug"


"$(INTDIR)\HelloWorld.obj" : $(SOURCE) "$(INTDIR)" "$(INTDIR)\HelloWorld.pch"


!ENDIF

SOURCE=.\HelloWorld.rc

!IF "$(CFG)" == "HelloWorld - Win32 (WCE emulator) Release"


"$(INTDIR)\HelloWorld.res" : $(SOURCE) "$(INTDIR)"
$(RSC) $(RSC_PROJ) $(SOURCE)


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE emulator) Debug"


"$(INTDIR)\HelloWorld.res" : $(SOURCE) "$(INTDIR)"
$(RSC) $(RSC_PROJ) $(SOURCE)


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE ARMV4) Release"


"$(INTDIR)\HelloWorld.res" : $(SOURCE) "$(INTDIR)"
$(RSC) $(RSC_PROJ) $(SOURCE)


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE ARMV4) Debug"


"$(INTDIR)\HelloWorld.res" : $(SOURCE) "$(INTDIR)"
$(RSC) $(RSC_PROJ) $(SOURCE)


!ENDIF

SOURCE=.\StdAfx.cpp

!IF "$(CFG)" == "HelloWorld - Win32 (WCE emulator) Release"

CPP_SWITCHES=/nologo /W3 /D _WIN32_WCE=$(CEVersion) /D "$(CePlatform)" /D
"_i386_" /D UNDER_CE=$(CEVersion) /D "i_386_" /D "UNICODE" /D "_UNICODE" /D
"_X86_" /D "x86" /D "NDEBUG" /Fp"$(INTDIR)\HelloWorld.pch" /Yc"stdafx.h"
/Fo"$(INTDIR)\\" /Gs8192 /GF /O2 /c

"$(INTDIR)\StdAfx.obj" "$(INTDIR)\HelloWorld.pch" : $(SOURCE) "$(INTDIR)"
$(CPP) @<<
$(CPP_SWITCHES) $(SOURCE)
<<


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE emulator) Debug"

CPP_SWITCHES=/nologo /W3 /Zi /Od /D "DEBUG" /D "_i386_" /D
UNDER_CE=$(CEVersion) /D _WIN32_WCE=$(CEVersion) /D "$(CePlatform)" /D
"i_386_" /D "UNICODE" /D "_UNICODE" /D "_X86_" /D "x86"
/Fp"$(INTDIR)\HelloWorld.pch" /Yc"stdafx.h" /Fo"$(INTDIR)\\" /Fd"$(INTDIR)\\"
/Gs8192 /GF /c

"$(INTDIR)\StdAfx.obj" "$(INTDIR)\HelloWorld.pch" : $(SOURCE) "$(INTDIR)"
$(CPP) @<<
$(CPP_SWITCHES) $(SOURCE)
<<


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE ARMV4) Release"

CPP_SWITCHES=/nologo /W3 /D _WIN32_WCE=$(CEVersion) /D "$(CePlatform)" /D
"ARM" /D "_ARM_" /D "ARMV4" /D UNDER_CE=$(CEVersion) /D "UNICODE" /D
"_UNICODE" /D "NDEBUG" /Fp"$(INTDIR)\HelloWorld.pch" /Yc"stdafx.h"
/Fo"$(INTDIR)\\" /O2 /M$(CECrtMT) /c

"$(INTDIR)\StdAfx.obj" "$(INTDIR)\HelloWorld.pch" : $(SOURCE) "$(INTDIR)"
$(CPP) @<<
$(CPP_SWITCHES) $(SOURCE)
<<


!ELSEIF "$(CFG)" == "HelloWorld - Win32 (WCE ARMV4) Debug"

CPP_SWITCHES=/nologo /W3 /Zi /Od /D "DEBUG" /D "ARM" /D "_ARM_" /D "ARMV4"
/D UNDER_CE=$(CEVersion) /D _WIN32_WCE=$(CEVersion) /D "$(CePlatform)" /D
"UNICODE" /D "_UNICODE" /Fp"$(INTDIR)\HelloWorld.pch" /Yc"stdafx.h"
/Fo"$(INTDIR)\\" /Fd"$(INTDIR)\\" /M$(CECrtMTDebug) /c

"$(INTDIR)\StdAfx.obj" "$(INTDIR)\HelloWorld.pch" : $(SOURCE) "$(INTDIR)"
$(CPP) @<<
$(CPP_SWITCHES) $(SOURCE)
<<


!ENDIF


!ENDIF



Re: eVC++ 4.0 SP4, Cannot build anything. Please help by Kerstin

Kerstin
Thu Apr 06 03:57:13 CDT 2006

Ouff...

Everything looks all right... sorry; I'm running out of ideas...
for some reason only Loki knows (maybe) your eVC doesn't make head or tail
of a - for my eyes - altogether correct project.

A really wild guess from one of our IT guys was that your problems might be
related to the order in which you installed eVC and VS.

Sorry that I couldn't give you something useful.

Greetings,

Kerstin

Re: eVC++ 4.0 SP4, Cannot build anything. Please help by Lao

Lao
Thu Apr 06 14:02:10 CDT 2006

Your HelloWorld is still too much for a real "hello world". How about
this?
- create a new project from scratch
- do not ask the wizard to create anything (choosing "Empty Project")
- Write the following TRUE helloworld.cpp. No header file, not resource
file. Just a CPP.
- build to see whether it works.

#include <windows.h>

// a unique String as a mutex
TCHAR* g_szMutex = TEXT("HelloWorld");
// WinMain
int WINAPI WinMain(
HINSTANCE hInstance,
HINSTANCE hPrevInstance,
LPSTR lpCmdLine,
int nCmdShow)
{
// We only allow one instance to run
const HANDLE hMutex = CreateMutex(NULL, false, g_szMutex);
if (GetLastError() == ERROR_ALREADY_EXISTS) {
goto Exit;
}

{
MessageBox(NULL, TEXT("Hello World!"), TEXT("Demo"),
MB_ICONINFORMATION|MB_OK|MB_SETFOREGROUND|MB_OK);
}

Exit:

CloseHandle(hMutex);
ReleaseMutex(hMutex);

return 0;
}


---
Lao K
Windows Mobile Pocket PC Smartphone Programming Hints and Tips
http://windowsmobilepro.blogspot.com


Re: eVC++ 4.0 SP4, Cannot build anything. Please help by JonathanKing

JonathanKing
Thu Apr 06 16:31:01 CDT 2006

That will not build either. First it gets stuck saying that it cannot link to
aygshell.lib. So I tried including aygshell.h. Then it complained that it
couldn't find aygshell.h. So I copied that header file over to my project
directory. Then I even had to put in the entire path of the file in the
include statement to get past that. Now it is saying:
Compiling...
Real.cpp
C:\Documents and Settings\Paul King\My
Documents\Dev\proj\RealHello\aygshell.h(23) : fatal error C1083: Cannot open
include file: 'winuserm.h': No such file or directory
Error executing cl.exe.
C:\Documents and Settings\Paul King\My
Documents\Dev\proj\RealHello\aygshell.h(23): Could not find the file
winuserm.h.
C:\Documents and Settings\Paul King\My
Documents\Dev\proj\RealHello\aygshell.h(26): Could not find the file
vibrate.h.
Must just be a bad install. Perhaps Kerstin is correct. It installed fine on
my other computer. I'll just have to put up with using the old slow laptop
for now. Thank you for everyone's continuing help. Your effort is much
appreciated.

Jonathan King

"Lao K" wrote:

> Your HelloWorld is still too much for a real "hello world". How about
> this?
> - create a new project from scratch
> - do not ask the wizard to create anything (choosing "Empty Project")
> - Write the following TRUE helloworld.cpp. No header file, not resource
> file. Just a CPP.
> - build to see whether it works.
>
> #include <windows.h>
>
> // a unique String as a mutex
> TCHAR* g_szMutex = TEXT("HelloWorld");
> // WinMain
> int WINAPI WinMain(
> HINSTANCE hInstance,
> HINSTANCE hPrevInstance,
> LPSTR lpCmdLine,
> int nCmdShow)
> {
> // We only allow one instance to run
> const HANDLE hMutex = CreateMutex(NULL, false, g_szMutex);
> if (GetLastError() == ERROR_ALREADY_EXISTS) {
> goto Exit;
> }
>
> {
> MessageBox(NULL, TEXT("Hello World!"), TEXT("Demo"),
> MB_ICONINFORMATION|MB_OK|MB_SETFOREGROUND|MB_OK);
> }
>
> Exit:
>
> CloseHandle(hMutex);
> ReleaseMutex(hMutex);
>
> return 0;
> }
>
>
> ---
> Lao K
> Windows Mobile Pocket PC Smartphone Programming Hints and Tips
> http://windowsmobilepro.blogspot.com
>
>

Re: eVC++ 4.0 SP4, Cannot build anything. Please help by r_z_aret

r_z_aret
Thu Apr 06 17:26:53 CDT 2006

On Tue, 4 Apr 2006 16:05:02 -0700, Jonathan King
<JonathanKing@discussions.microsoft.com> wrote:

>I cannot compile because then I get another error because
>'emulatorDbg/HelloWorld.pch' does not exist. I'm guessing that that file is
>dependent on the resources. I exported the makefile, but I really don't know
>what to look for.

The "pch" files are "precompiled headers". At least for now, you can
eliminate those messages by choosing not to use precompiled headers
(Project->Settings->C/C++->Precompiled Headers). I find them more
bother than useful, and never use them. They can reduce compilation
time for big projects, so some folks really like them.


>
>Something interesting, if I copy everything from the correct include folder
>into my project directory OR (what you suggested) just add the directory to
>the settings,

Copying files like that is a bit helpful for diagnosing installation
problems. Definitely not good for real use.


> I get past one hurdle. It successfully compiles the resources,
>and I am now able to expand the resources in the workspace viewer. Now, the
>build stops here:
>Compiling resources...
>Compiling...
>StdAfx.cpp
>Compiling...
>HelloWorld.cpp
>C:\Documents and Settings\Paul King\My
>Documents\Dev\proj\HelloWorld\HelloWorld.cpp(7) : fatal error C1083: Cannot
>open include file: 'aygshell.h': No such file or directory

The aygshell.h file is included only for some platforms. It is
included for Pocket PCs (all versions). It is generally not included
for others. So you are likely to get such an error if you include a
file from a Pocket PC SDK, but try to build with another SDK. Copying
header files is a very effective way to generate such errors.


>Error executing cl.exe
>
>It looks like it just won't look in the directories that it is supposed to.
>I installed eVC on my other computer, and it works fine. I need eVC on this
>computer though, because the other is extremely slowww. I'm wondering if it
>is due to a bad install.

A bad install is _very_ likely.


I had Visual Studio 2005 developer preview 2
>installed. Could that have affected it? I just got rid of it, and I am about
>to reinstall eVC.

Possible. But several folks, including me, have multiple compilers on
a single computer without problems. Of course, Beta/Preview versions
are always more suspect.

Completely removing software is not always easy. Leftovers may affect
the reinstall. In particular, registry settings can be painful.
Unfortunately, the only sure cure for them is to reinstall the
operating system. Not something to do lightly. Even more
unfortunately, I don't know nearly enough to help guide you much.


>
>"r_z_aret@pen_fact.com" wrote:
>
>> On Mon, 3 Apr 2006 14:59:03 -0700, Jonathan King
>> <JonathanKing@discussions.microsoft.com> wrote:
>>
>> >I am creating a new Pocket PC 2003 application, building for WCE ARMV4 and
>> >WCE emulator. The I select typical hellow world application or a simple
>> >WinCE application. Either one gives me the same error. I just tried with a
>> >smartphone project same thing.
>> >
>> >I just went to "Tools->Options->Directories". Under the Pocket PC 2003
>> >platform, there are three entries:
>> >C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\Include\emulator
>> >C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\mfc\include
>> >C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\atl\include
>> >Winver.h is in the first directory, so why wont it open? If I move winver.h
>> >to the project directory, then I get another error that it cannot find
>> >aygshell.h. If I copy that to the project folder, I get another error, and on
>> >and on. It really does sound like an include problem, but the directory is
>> >there.
>>
>> I have wasted a lot of time moving header files around, so I
>> recommend not doing it. It tends to snowball (trigger several new
>> error messages for each one suppressed).
>>
>> I see a copy of winver in each of the CPU-specific "include" folders
>> (include\armv4, include\emulator). The list you see in
>> Tools->Options->Directories should depend on platform and CPU. In
>> particular, you should see only emulator folders for the emulator list
>> and only ARMV4 folders for the ARMV4 list. (This paragraph is
>> _definitely_ not as clear as I would like, but each of several
>> attempts I made to clarify were even muddier.)
>>
>> I've never quite understood the difference between "" and <> in
>> references to header (include) files. Does "" mean look _only_ in
>> current (caller's) folder, or first in current and then in "system"?
>> Does <> mean look only in "system"?
>>
>> >
>> >Another thing, if in the workspace viewer, I click the resources tab and try
>> >to expand the resources folder, I get the same thing. Error RC1015 cannot
>> >open winver.h. What is wrong?
>>
>> I'm not so surprised that the resource compiler and resource editor
>> suffer from the same problem.
>>
>> What happens if you try to compile just a source (c or cpp) file? If
>> that works, then the problem is somewhat limited to resources.
>>
>> At least for diagnostics, you might want to try adding the appropriate
>> "CPU folder" (see above) to the "Additional resource include
>> directories" in Project->Settings->Resources. You should add only one
>> folder for each target (CPU/platform).
>>
>>
>> >
>> >"Kerstin Pirrung" wrote:
>> >
>> >> Hi!
>> >>
>> >> Basically it looks like your "Include Directories" list is incomplete. One
>> >> of the drawbacks of eVC is that it does not set those lists all that
>> >> intelligently (one of the drawbacks of VS 2005 is that it won't tell me
>> >> voluntarily how and why it set said lists) - so just try and check "Tools->
>> >> Options->Directories" as well as yur INCLUDEDIRS.
>> >>
>> >> Greetings,
>> >>
>> >> Kerstin
>> >>
>> >> =?Utf-8?B?Sm9uYXRoYW4gS2luZw==?=
>> >> <JonathanKing@discussions.microsoft.com> wrote in
>> >> news:A613317B-4252-4B77-8A62-9B5E59B866AB@microsoft.com:
>> >>
>> >> > Ok, a google search pulls up nothing. Basically, I just installed
>> >> > eVC++ 4.0, the PPC 2003 sdk, and SP4. Cannot get anything to build. If
>> >> > I create a new PPC 2003 simple CE app or hello world app then attempt
>> >> > to build, it will not work. I get the following error:
>> >> >
>> >> > Compiling resources...
>> >> > C:\Documents and Settings\Paul King\My
>> >> > Documents\Dev\HelloWorld\newres.h(32)
>> >> >: fatal error RC1015: cannot open include file 'winver.h'.
>> >> > Error executing rc.exe.
>> >> >
>> >> > A google search pulls up many people asking this question, but no
>> >> > solutions. Can somebody please help?
>> >>
>> >>
>>
>> -----------------------------------------
>> To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).
>>
>> Robert E. Zaret, eMVP
>> PenFact, Inc.
>> 20 Park Plaza, Suite 478
>> Boston, MA 02116
>> www.penfact.com
>>

-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).

Robert E. Zaret, eMVP
PenFact, Inc.
20 Park Plaza, Suite 478
Boston, MA 02116
www.penfact.com

Re: eVC++ 4.0 SP4, Cannot build anything. Please help by JonathanKing

JonathanKing
Sun Apr 09 14:20:02 CDT 2006

Ok, well I am going to go off the assumption that my system has been screwed
by visual studio. A google search tells me that I did not uninstall the
components in the correct order. One page that I found told me that if I do
not uninstall the .NET framework beta last, I will "not be a very happy
person." Well, I am there right now. Are there any tools that will help me
completely clean my system of Visual Studio?

"Jonathan King" wrote:

> That will not build either. First it gets stuck saying that it cannot link to
> aygshell.lib. So I tried including aygshell.h. Then it complained that it
> couldn't find aygshell.h. So I copied that header file over to my project
> directory. Then I even had to put in the entire path of the file in the
> include statement to get past that. Now it is saying:
> Compiling...
> Real.cpp
> C:\Documents and Settings\Paul King\My
> Documents\Dev\proj\RealHello\aygshell.h(23) : fatal error C1083: Cannot open
> include file: 'winuserm.h': No such file or directory
> Error executing cl.exe.
> C:\Documents and Settings\Paul King\My
> Documents\Dev\proj\RealHello\aygshell.h(23): Could not find the file
> winuserm.h.
> C:\Documents and Settings\Paul King\My
> Documents\Dev\proj\RealHello\aygshell.h(26): Could not find the file
> vibrate.h.
> Must just be a bad install. Perhaps Kerstin is correct. It installed fine on
> my other computer. I'll just have to put up with using the old slow laptop
> for now. Thank you for everyone's continuing help. Your effort is much
> appreciated.
>
> Jonathan King
>
> "Lao K" wrote:
>
> > Your HelloWorld is still too much for a real "hello world". How about
> > this?
> > - create a new project from scratch
> > - do not ask the wizard to create anything (choosing "Empty Project")
> > - Write the following TRUE helloworld.cpp. No header file, not resource
> > file. Just a CPP.
> > - build to see whether it works.
> >
> > #include <windows.h>
> >
> > // a unique String as a mutex
> > TCHAR* g_szMutex = TEXT("HelloWorld");
> > // WinMain
> > int WINAPI WinMain(
> > HINSTANCE hInstance,
> > HINSTANCE hPrevInstance,
> > LPSTR lpCmdLine,
> > int nCmdShow)
> > {
> > // We only allow one instance to run
> > const HANDLE hMutex = CreateMutex(NULL, false, g_szMutex);
> > if (GetLastError() == ERROR_ALREADY_EXISTS) {
> > goto Exit;
> > }
> >
> > {
> > MessageBox(NULL, TEXT("Hello World!"), TEXT("Demo"),
> > MB_ICONINFORMATION|MB_OK|MB_SETFOREGROUND|MB_OK);
> > }
> >
> > Exit:
> >
> > CloseHandle(hMutex);
> > ReleaseMutex(hMutex);
> >
> > return 0;
> > }
> >
> >
> > ---
> > Lao K
> > Windows Mobile Pocket PC Smartphone Programming Hints and Tips
> > http://windowsmobilepro.blogspot.com
> >
> >

Re: eVC++ 4.0 SP4, Cannot build anything. Please help by JonathanKing

JonathanKing
Sun Apr 09 14:26:01 CDT 2006

I had not seen your post. I guess I will give up on this computer. I might
reinstall Windows if I ever have lots of time.

Thanks for all the help.

Re: eVC++ 4.0