Talk:Compiling under VS2005: Difference between revisions
| Line 41: | Line 41: | ||
I'd recommend /not/ using #pragma warning to disable the deprecated function comments... if you add _CRT_SECURE_NO_DEPRECATE and _CRT_NON_CONFORMING_SWPRINTFS to the preprocessor options for the projects, and then run a series of simple find/replaces across the solution (no more than about 6 - stricmp->_stricmp, __stricmp->_stricmp, strnicmp->_strnicmp, __strnicmp->_strnicmp, and a few others in similar fashion) then it actually fixes the warnings instead of just making the compiler not tell us about them. --[[User:Superpig]] | I'd recommend /not/ using #pragma warning to disable the deprecated function comments... if you add _CRT_SECURE_NO_DEPRECATE and _CRT_NON_CONFORMING_SWPRINTFS to the preprocessor options for the projects, and then run a series of simple find/replaces across the solution (no more than about 6 - stricmp->_stricmp, __stricmp->_stricmp, strnicmp->_strnicmp, __strnicmp->_strnicmp, and a few others in similar fashion) then it actually fixes the warnings instead of just making the compiler not tell us about them. --[[User:Superpig]] | ||
Also, a nicer fix for ..\tier1\KeyValues.cpp(800): just change the type of the variable to be a const char* instead of a char*. --[[User:Superpig]] | |||
---- | ---- | ||
Revision as of 13:52, 5 March 2006
Misc
I'll be getting a copy of Visual Studio 2005 (not express) in the next couple of weeks. Is there a problem compiling on it too or does anybody know yet? --AndrewNeo 07:11, 28 Jan 2006 (PST)
Yes, what i read is there are no Problems with normal, full Version of VS 05, but i had problems... same as with express. --Rotzi 4 Fe 2006 (GMT+1)
Other Fixes / Comments
got some info from this forumthreat
i had some errors in c_rope
fixed it once with:
taking the closing "}" from ( int iRenderCache = 0; iRenderCache < nRenderCacheCount; ++iRenderCache )
behind ++m_aRenderCache[iRenderCache].m_nCacheCount;
(means from line 231 (i think) to line 252)
i'm still trying to complete this so it will compile, hope i could help anyone...
greetz
User:Rotzi Jan 2006
grml...
doesn't work neither with express nor with full version... maybe i'm just stupid...
I'll try again this weekend and update here...
User:Rotzi Feb 2006
And still I'm having problems... Just tried it again, Release Client only, but did not get past 3 kinds of errors, wich all in all were 190 errors and 439 warnings...
I also noticed that including user32.lib and excluding LIBC did not change these error-numbers, so atleast up to that point, it did not need them... Still I'm only talking about client-Release Only.
I'd recommend /not/ using #pragma warning to disable the deprecated function comments... if you add _CRT_SECURE_NO_DEPRECATE and _CRT_NON_CONFORMING_SWPRINTFS to the preprocessor options for the projects, and then run a series of simple find/replaces across the solution (no more than about 6 - stricmp->_stricmp, __stricmp->_stricmp, strnicmp->_strnicmp, __strnicmp->_strnicmp, and a few others in similar fashion) then it actually fixes the warnings instead of just making the compiler not tell us about them. --User:Superpig
Also, a nicer fix for ..\tier1\KeyValues.cpp(800): just change the type of the variable to be a const char* instead of a char*. --User:Superpig
No longer needed, just if i/we need it again... ;)
'undeclared variable' ..\cl_dll\interpolatedvar.h(538) ..\public\sentence.cpp(735) ..\public\sentence.cpp(1098) ..\public\sentence.cpp(1168)