View Issue Details

IDProjectCategoryView StatusLast Update
0002211FSSCPBuild systempublic2010-06-04 11:13
ReporterThe_E Assigned Tochief1983  
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
Product Version3.6.12 RC2 
Summary0002211: Building release FRED fails on VS2010
DescriptionGuess I should start a ticket for this.

Basically, when using VS2010 and its associated toolchain and SDK, it seems impossible to build regular FRED builds. It errors out with the following errors:
3>C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\atlmfc\include\afxwin2.inl(362): error C2039: 'NotifyWinEvent' : is not a member of '`global namespace''
3>C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\atlmfc\include\afxwin2.inl(362): error C2660: 'CWnd::NotifyWinEvent' : function does not take 4 arguments

Going back to the v9 toolset (if you have VS2008 installed) fixes this, but that's not what I'd like to call an elegant solution.
TagsNo tags attached.

Activities

The_E

2010-05-25 00:47

administrator   ~0011998

Oh, I should add that DEBUG FRED builds just fine.

The_E

2010-05-25 00:58

administrator   ~0011999

And just by a miracle, the solution appears. It seems that setting WINVER to 401 or whatever is bad for the VS2010 standard ATL/MFC includes. The whole thing needs at least WINVER=0x500 to compile correctly.

iss_mneur

2010-05-25 01:23

developer   ~0012000

But I assume that means it still compiles with VC6? Just not with the new SDK?

chief1983

2010-05-25 04:22

administrator   ~0012001

A commit was made to change this only for VS2010 project files. Unfortunately, that may preclude VS2010 from making Win98 compatible FRED builds. Times are a'changin' ain't they?

Goober5000

2010-06-04 05:48

administrator   ~0012039

Last edited: 2010-06-04 05:48

Well poo. I'm not too worried about this though because VC6 and VC2005 still work fine, and we'll eventually retire FRED in favor of wxFRED anyway, thus restoring compatibility.

I noticed a commit on this subject in the log. Can this be resolved as fixed?

The_E

2010-06-04 11:13

administrator   ~0012040

Probably.

Issue History

Date Modified Username Field Change
2010-05-25 00:46 The_E New Issue
2010-05-25 00:46 The_E Status new => assigned
2010-05-25 00:46 The_E Assigned To => chief1983
2010-05-25 00:47 The_E Note Added: 0011998
2010-05-25 00:58 The_E Note Added: 0011999
2010-05-25 01:23 iss_mneur Note Added: 0012000
2010-05-25 04:22 chief1983 Note Added: 0012001
2010-06-04 05:48 Goober5000 Note Added: 0012039
2010-06-04 05:48 Goober5000 Note Edited: 0012039
2010-06-04 05:48 Goober5000 Note Edited: 0012039
2010-06-04 11:13 The_E Note Added: 0012040
2010-06-04 11:13 The_E Status assigned => resolved
2010-06-04 11:13 The_E Resolution open => fixed