Discussion:
MFC requires WINVER to be #defined to 0x0400 or greater
(too old to reply)
yiannisp
2008-01-03 22:12:42 UTC
Permalink
I am trying to build a Windows CE project written with Visual Studio 2005 for
a Windows CE 5.0 device. Altgouth this project does build (debug and release)
for a pocket pc 2003 it produces this error when build on windows ce 5.0.
Graeme Wintle
2008-01-09 19:58:21 UTC
Permalink
So what happens if you define WINVER=400 in the compile options, isn't this
a warning rather than err anyhow?
--
--
GraemeW
Web - http://www.bytesnap.co.uk
Blog - http://ce4all.blogspot.com
Post by yiannisp
I am trying to build a Windows CE project written with Visual Studio 2005 for
a Windows CE 5.0 device. Altgouth this project does build (debug and release)
for a pocket pc 2003 it produces this error when build on windows ce 5.0.
yiannisp via PocketPCJunkies.com
2008-01-10 07:11:57 UTC
Permalink
I found what was wrong. The problem was that when I add a new configuration I
didn't ask the wizard to copy the settings from the arm configuration. Next
time when I did everything was ok. There are some debug and link command
lines that are supposed to be almost the same.
Post by Graeme Wintle
So what happens if you define WINVER=400 in the compile options, isn't this
a warning rather than err anyhow?
Post by yiannisp
I am trying to build a Windows CE project written with Visual Studio 2005 for
a Windows CE 5.0 device. Altgouth this project does build (debug and release)
for a pocket pc 2003 it produces this error when build on windows ce 5.0.
--
Message posted via PocketPCJunkies.com
http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-vc/200801/1
unknown
2010-04-27 07:22:42 UTC
Permalink
I am running a MFC proejct on windows mobile 5.0 pocket pc emulator and I am getting the error "MFC requires WINVER to be #defined to 0x0400 or greater" so how to solve that?
I saw that WinVER is define to the value _WIN32_WCE.
if I set the its value to 0x501 then I am getting so many errors.



yiannisp via PocketPCJunkies.com wrote:

I found what was wrong.
10-Jan-08

I found what was wrong. The problem was that when I add a new configuration I
didn't ask the wizard to copy the settings from the arm configuration. Next
time when I did everything was ok. There are some debug and link command
lines that are supposed to be almost the same.



Graeme Wintle wrote:
--
Message posted via PocketPCJunkies.com
http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-vc/200801/1

Previous Posts In This Thread:

On Thursday, January 03, 2008 5:12 PM
yiannisp wrote:

MFC requires WINVER to be #defined to 0x0400 or greater
I am trying to build a Windows CE project written with Visual Studio 2005 for
a Windows CE 5.0 device. Altgouth this project does build (debug and release)
for a pocket pc 2003 it produces this error when build on windows ce 5.0.

On Wednesday, January 09, 2008 2:58 PM
Graeme Wintle wrote:

So what happens if you define WINVER=400 in the compile options, isn't this a
So what happens if you define WINVER=400 in the compile options, is not this
a warning rather than err anyhow?

--
--
GraemeW
Web - http://www.bytesnap.co.uk
Blog - http://ce4all.blogspot.com

On Thursday, January 10, 2008 2:11 AM
yiannisp via PocketPCJunkies.com wrote:

I found what was wrong.
I found what was wrong. The problem was that when I add a new configuration I
didn't ask the wizard to copy the settings from the arm configuration. Next
time when I did everything was ok. There are some debug and link command
lines that are supposed to be almost the same.



Graeme Wintle wrote:
--
Message posted via PocketPCJunkies.com
http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-vc/200801/1


Submitted via EggHeadCafe - Software Developer Portal of Choice
Book Review: C# 4.0 In a Nutshell [O'Reilly]
http://www.eggheadcafe.com/tutorials/aspnet/6dc05c04-c7f9-40cc-a2da-88dde2e6d891/book-review-c-40-in-a.aspx
Loading...