Re: [Vxl-users] VXL/CMake error during build

[Jim G. <jg...@ro...>]

Interesting steps to solve my problem below.  I looked at the VS MSDN 
help file and discovered that there is a compile switch /D that 
allows you to set the WINVER.  I had never needed to do this with my 
Win2000 install of the same VS software, CMake under Win2000 doesn't 
need it, but I added /D WINVER=0x0501 to the CMake compile switches 
and the error went away.

However, the other error did not disappear.  It was a can't read an 
.h file from the Vis Studio directory (the file is there and has read 
permissions for everybody) which caused a bunch of compile 
errors.  Never had this problem with my Win2000 install of the same 
VS software.  I think this is an example of the wisdom of the old 
saying, "if it's not broken, don't fix it".  I fixed it and got a 
bunch of problems.

So I just fell back and booted up my Win2000 partition, updated the 
VXL source there, ran CMake (no problem) and built the app (no 
problem).  Then ran the app (no problem).

I can't understand why Microsoft keeps making changes that break 
things that work?  I have built this app with VS2005 running under 
WinXP before with no problem, but I didn't do the installs so have no 
idea what the sys manager did to make it work under XP.  It shouldn't 
be that difficult, but it is.

At any rate, I don't mind booting up Win2000 to do my builds, so 
that's what I'll do.

Regards, Jim Green
---------------------------------------

At 05:21 PM 1/16/2009, Jim Green wrote:
>I fell back to Vis Studio 2005, and CMake now makes the vxl.sln file
>with no problems.  Then the vxl.sln file loads into Vis Studio 2005
>with no problem.  But, when I try to build a Brown contrib executable
>which has always built before with no problem, I get an "error"
>message from the C++ compiler saying:
>
>WINVER not defined.  Defaulting to  0x0502 (Windows Server 2003)
>
>This "error" message occurs a dozen or so times.
>
>Of course. I'm running Win XP with SP3.  The WINVER for XP is
>0x0501.  Before when I was running Win 2000 (for 8 years) I never had
>any such error message,  I never had to set WINVER, and everything
>built great.  (I'm also getting another error which I suspect is due to this.)
>
>Has anyone else ever seen this "error" when building VXL in Visual Studio?
>
>Thanks, Jim Green
>-----------------------------------
>
>
>------------------------------------------------------------------------------
>This SF.net email is sponsored by:
>SourcForge Community
>SourceForge wants to tell your story.
>http://p.sf.net/sfu/sf-spreadtheword
>_______________________________________________
>Vxl-users mailing list
>Vxl...@li...
>https://lists.sourceforge.net/lists/listinfo/vxl-users