optimization Off but still get compiler error message
in [MFC]
|
Prev: How to serialize Mfc template dialog class ?
Next: 063770 M3i Zero , Ezflash Dsi , R4i Dsi 68210
From: phil oakleaf on 8 Sep 2009 10:07 Joseph M. Newcomer wrote: > Show us the command line itself. > joe > > On Tue, 08 Sep 2009 09:19:57 +0100, phil oakleaf <news(a)oakleafsoftware.co.uk> wrote: > >> Joseph M. Newcomer wrote: >>> Did you think of looking at the compiler options? Because "symbols for Edit-and-continue" >>> is INCOMPATIBLE with /O2 (as already pointed out by the error message), you have to set >>> the option for symbol information to NOT create symbols for Edit-and-Continue. RTFM. /Zi >>> creates complete debugging information. So your error was in choosing the wrong kind of >>> debug information. If you get an error that says explicitly what is wrong, then your >>> first reaction should be "what do I need to change to make this error go away?" and it >>> clearly says that if you have optimization set, you cannot use "Program Database for Edit >>> & Continue". This option would apply only to the debug version, not the release version. >>> joe >>> >>> On Mon, 07 Sep 2009 23:28:15 +0100, phil oakleaf <news(a)oakleafsoftware.co.uk> wrote: >>> >>>> I'm trying to compile with full debug information >>>> >>>> >>>> In the optimisation I've set >>>> Optimisation Disabled (/Od) >>>> >>>> debug info set to >>>> Program Database for Edit & Continue (/ZI) >>>> >>>> >>>> But the compiler complains >>>> '/O2' and '/ZI' command-line options are incompatible >>>> >>>> Any help will be Much appreciated >>>> >>>> Phil >>> Joseph M. Newcomer [MVP] >>> email: newcomer(a)flounder.com >>> Web: http://www.flounder.com >>> MVP Tips: http://www.flounder.com/mvp_tips.htm >> Joseph >> >> thanks for the reply >> >> The problem is that I have Optimisation OFF but the compiler keeps >> telling me it is /O2 >> >> I really have looked at the compiler options :) >> >> Phil > Joseph M. Newcomer [MVP] > email: newcomer(a)flounder.com > Web: http://www.flounder.com > MVP Tips: http://www.flounder.com/mvp_tips.htm Joseph I think it is a setting for a single CPP file that is messing it up Many thanks for the reply Phil
From: Joseph M. Newcomer on 8 Sep 2009 11:46 See below... On Tue, 08 Sep 2009 15:05:42 +0100, phil oakleaf <news(a)oakleafsoftware.co.uk> wrote: >Command Line >-------------------- >/Od /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >"_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >/Zc:forScope- /Yu"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >/Fo"c:\callidusOutput\release\\" /Fd"c:\callidusOutput\release\vc80.pdb" >/W0 /nologo /c /ZI /errorReport:prompt > > >Output from the Build >-------------------------------------- >1>------ Build started: Project: callidusXML, Configuration: Release >Win32 ------ >1>Compiling... >1>cl : Command line error D8016 : '/O2' and '/ZI' command-line options >are incompatible >1>Build log was saved at "file://c:\callidusOutput\release\BuildLog.htm" >1>callidusXML - 1 error(s), 0 warning(s) >========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== > >BuildLog.html >------------------------------------------------- >Note: There is a refence to /O2 in the BuildLog.html but I dont know how >that can be if the command line doesn't have it. > >Build Log Build started: Project: callidusXML, Configuration: >Release|Win32 > Command Lines Creating temporary file >"c:\callidusOutput\release\RSP00000828924912.rsp" with contents >[ >/Od /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >"_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >/Zc:forScope- /Yu"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >/Fo"c:\callidusOutput\release\\" /Fd"c:\callidusOutput\release\vc80.pdb" >/W0 /c /ZI /MP > >.\FloorPaintBrushes.cpp >-- lots of other files >] >Creating command line "cl.exe >@c:\callidusOutput\release\RSP00000828924912.rsp /nologo >/errorReport:prompt" >Creating temporary file >"c:\callidusOutput\release\RSP00000928924912.rsp" with contents >[ >/O2 /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >"_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >/Zc:forScope- /Yc"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >/Fo"c:\callidusOutput\release\\" /Fd"c:\callidusOutput\release\vc80.pdb" >/W0 /c /ZI /MP **** Note that if you have gone in and modified the settings for ONE PARTICULAR file, these "local" settings override the "global" settings for your project. So if your project uses /Od /ZI and your file says /O2 /ZI, then your file will have these conflicting settings. Note that for release mode, you should never use /ZI, ever, under any circumstances, because it presumes a debug mode edit-and-continue model is being used. Therefore, if this represents an "unoptimized" Release build, the use of /ZI is what is erroneous, every place it is used. You should use /Zi for release builds, whether you are using /Od or /O2 or any other optimization settings. It looks to me like you have a local file override here. **** > >".\ASCII Format.cpp" >] >Creating command line "cl.exe >@c:\callidusOutput\release\RSP00000928924912.rsp /nologo >/errorReport:prompt" >Creating temporary file >"c:\callidusOutput\release\RSP00000A28924912.rsp" with contents >[ >/O2 /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >"_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >/Zc:forScope- /Yu"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >/Fo"c:\callidusOutput\release\\" /Fd"c:\callidusOutput\release\vc80.pdb" >/W0 /c /ZI /MP **** Ditto. Make sure you have not overridden the setting for this individual file **** > >.\F_Fdraw.cpp > > >] >Creating command line "cl.exe >@c:\callidusOutput\release\RSP00000A28924912.rsp /nologo >/errorReport:prompt" >Creating temporary file >"c:\callidusOutput\release\RSP00000B28924912.rsp" with contents >[ >/Od /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >"_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >/Zc:forScope- /Yu"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >/Fo"c:\callidusOutput\release/Carpettl1.obj" >/Fd"c:\callidusOutput\release\vc80.pdb" /W0 /c /ZI /MP > >.\Carpettl.cpp >] >Creating command line "cl.exe >@c:\callidusOutput\release\RSP00000B28924912.rsp /nologo >/errorReport:prompt" >Creating temporary file >"c:\callidusOutput\release\RSP00000C28924912.rsp" with contents >[ >/Od /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >"_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >/Zc:forScope- /Fo"c:\callidusOutput\release\\" >/Fd"c:\callidusOutput\release\vc80.pdb" /W0 /c /ZI /MP > >.\gpc.c >] >Creating command line "cl.exe >@c:\callidusOutput\release\RSP00000C28924912.rsp /nologo >/errorReport:prompt" >Creating temporary file >"c:\callidusOutput\release\RSP00000D28924912.rsp" with contents >[ >/Od /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >"_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >/Zc:forScope- /Yu"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >/Fo"c:\callidusOutput\release/RollCut_Fitting1.obj" >/Fd"c:\callidusOutput\release\vc80.pdb" /W0 /c /ZI /MP > >.\RollCut_Fitting.cpp >] >Creating command line "cl.exe >@c:\callidusOutput\release\RSP00000D28924912.rsp /nologo >/errorReport:prompt" > Output Window Compiling... >cl : Command line error D8016 : '/O2' and '/ZI' command-line options are >incompatible > Results Build log was saved at >"file://c:\callidusOutput\release\BuildLog.htm" >callidusXML - 1 error(s), 0 warning(s) Joseph M. Newcomer [MVP] email: newcomer(a)flounder.com Web: http://www.flounder.com MVP Tips: http://www.flounder.com/mvp_tips.htm
From: phil oakleaf on 8 Sep 2009 17:33 Joseph M. Newcomer wrote: > See below... > On Tue, 08 Sep 2009 15:05:42 +0100, phil oakleaf <news(a)oakleafsoftware.co.uk> wrote: > >> Command Line >> -------------------- >> /Od /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >> "_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >> /Zc:forScope- /Yu"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >> /Fo"c:\callidusOutput\release\\" /Fd"c:\callidusOutput\release\vc80.pdb" >> /W0 /nologo /c /ZI /errorReport:prompt >> >> >> Output from the Build >> -------------------------------------- >> 1>------ Build started: Project: callidusXML, Configuration: Release >> Win32 ------ >> 1>Compiling... >> 1>cl : Command line error D8016 : '/O2' and '/ZI' command-line options >> are incompatible >> 1>Build log was saved at "file://c:\callidusOutput\release\BuildLog.htm" >> 1>callidusXML - 1 error(s), 0 warning(s) >> ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== >> >> BuildLog.html >> ------------------------------------------------- >> Note: There is a refence to /O2 in the BuildLog.html but I dont know how >> that can be if the command line doesn't have it. >> >> Build Log Build started: Project: callidusXML, Configuration: >> Release|Win32 >> Command Lines Creating temporary file >> "c:\callidusOutput\release\RSP00000828924912.rsp" with contents >> [ >> /Od /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >> "_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >> /Zc:forScope- /Yu"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >> /Fo"c:\callidusOutput\release\\" /Fd"c:\callidusOutput\release\vc80.pdb" >> /W0 /c /ZI /MP >> >> .\FloorPaintBrushes.cpp >> -- lots of other files >> ] >> Creating command line "cl.exe >> @c:\callidusOutput\release\RSP00000828924912.rsp /nologo >> /errorReport:prompt" >> Creating temporary file >> "c:\callidusOutput\release\RSP00000928924912.rsp" with contents >> [ >> /O2 /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >> "_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >> /Zc:forScope- /Yc"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >> /Fo"c:\callidusOutput\release\\" /Fd"c:\callidusOutput\release\vc80.pdb" >> /W0 /c /ZI /MP > **** > Note that if you have gone in and modified the settings for ONE PARTICULAR file, these > "local" settings override the "global" settings for your project. So if your project uses > /Od /ZI and your file says /O2 /ZI, then your file will have these conflicting settings. > > Note that for release mode, you should never use /ZI, ever, under any circumstances, > because it presumes a debug mode edit-and-continue model is being used. Therefore, if > this represents an "unoptimized" Release build, the use of /ZI is what is erroneous, every > place it is used. You should use /Zi for release builds, whether you are using /Od or /O2 > or any other optimization settings. > > It looks to me like you have a local file override here. > **** >> ".\ASCII Format.cpp" >> ] >> Creating command line "cl.exe >> @c:\callidusOutput\release\RSP00000928924912.rsp /nologo >> /errorReport:prompt" >> Creating temporary file >> "c:\callidusOutput\release\RSP00000A28924912.rsp" with contents >> [ >> /O2 /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >> "_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >> /Zc:forScope- /Yu"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >> /Fo"c:\callidusOutput\release\\" /Fd"c:\callidusOutput\release\vc80.pdb" >> /W0 /c /ZI /MP > **** > Ditto. Make sure you have not overridden the setting for this individual file > **** >> .\F_Fdraw.cpp >> >> >> ] >> Creating command line "cl.exe >> @c:\callidusOutput\release\RSP00000A28924912.rsp /nologo >> /errorReport:prompt" >> Creating temporary file >> "c:\callidusOutput\release\RSP00000B28924912.rsp" with contents >> [ >> /Od /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >> "_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >> /Zc:forScope- /Yu"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >> /Fo"c:\callidusOutput\release/Carpettl1.obj" >> /Fd"c:\callidusOutput\release\vc80.pdb" /W0 /c /ZI /MP >> >> .\Carpettl.cpp >> ] >> Creating command line "cl.exe >> @c:\callidusOutput\release\RSP00000B28924912.rsp /nologo >> /errorReport:prompt" >> Creating temporary file >> "c:\callidusOutput\release\RSP00000C28924912.rsp" with contents >> [ >> /Od /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >> "_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >> /Zc:forScope- /Fo"c:\callidusOutput\release\\" >> /Fd"c:\callidusOutput\release\vc80.pdb" /W0 /c /ZI /MP >> >> .\gpc.c >> ] >> Creating command line "cl.exe >> @c:\callidusOutput\release\RSP00000C28924912.rsp /nologo >> /errorReport:prompt" >> Creating temporary file >> "c:\callidusOutput\release\RSP00000D28924912.rsp" with contents >> [ >> /Od /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >> "_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >> /Zc:forScope- /Yu"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >> /Fo"c:\callidusOutput\release/RollCut_Fitting1.obj" >> /Fd"c:\callidusOutput\release\vc80.pdb" /W0 /c /ZI /MP >> >> .\RollCut_Fitting.cpp >> ] >> Creating command line "cl.exe >> @c:\callidusOutput\release\RSP00000D28924912.rsp /nologo >> /errorReport:prompt" >> Output Window Compiling... >> cl : Command line error D8016 : '/O2' and '/ZI' command-line options are >> incompatible >> Results Build log was saved at >> "file://c:\callidusOutput\release\BuildLog.htm" >> callidusXML - 1 error(s), 0 warning(s) > Joseph M. Newcomer [MVP] > email: newcomer(a)flounder.com > Web: http://www.flounder.com > MVP Tips: http://www.flounder.com/mvp_tips.htm Joseph Again, many thanks for the help - I can certainly see where the O2 settings are coming from now. Is there a way to clear any file override settings for an entire project. Other than going through every single one I have looked on google but cant find anything obvious Phil
From: Joseph M. Newcomer on 8 Sep 2009 19:34 It is sometimes informative to read the .vcproj file. Search-and-replace work well if you know what you are looking for and understand what you are about to do. However, always make a backup copy (or six or seven or ten) of the file as you make changes so you can back out of a change if you really mess it up. joe On Tue, 08 Sep 2009 22:33:36 +0100, phil oakleaf <news(a)oakleafsoftware.co.uk> wrote: >Joseph M. Newcomer wrote: >> See below... >> On Tue, 08 Sep 2009 15:05:42 +0100, phil oakleaf <news(a)oakleafsoftware.co.uk> wrote: >> >>> Command Line >>> -------------------- >>> /Od /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >>> "_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >>> /Zc:forScope- /Yu"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >>> /Fo"c:\callidusOutput\release\\" /Fd"c:\callidusOutput\release\vc80.pdb" >>> /W0 /nologo /c /ZI /errorReport:prompt >>> >>> >>> Output from the Build >>> -------------------------------------- >>> 1>------ Build started: Project: callidusXML, Configuration: Release >>> Win32 ------ >>> 1>Compiling... >>> 1>cl : Command line error D8016 : '/O2' and '/ZI' command-line options >>> are incompatible >>> 1>Build log was saved at "file://c:\callidusOutput\release\BuildLog.htm" >>> 1>callidusXML - 1 error(s), 0 warning(s) >>> ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== >>> >>> BuildLog.html >>> ------------------------------------------------- >>> Note: There is a refence to /O2 in the BuildLog.html but I dont know how >>> that can be if the command line doesn't have it. >>> >>> Build Log Build started: Project: callidusXML, Configuration: >>> Release|Win32 >>> Command Lines Creating temporary file >>> "c:\callidusOutput\release\RSP00000828924912.rsp" with contents >>> [ >>> /Od /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >>> "_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >>> /Zc:forScope- /Yu"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >>> /Fo"c:\callidusOutput\release\\" /Fd"c:\callidusOutput\release\vc80.pdb" >>> /W0 /c /ZI /MP >>> >>> .\FloorPaintBrushes.cpp >>> -- lots of other files >>> ] >>> Creating command line "cl.exe >>> @c:\callidusOutput\release\RSP00000828924912.rsp /nologo >>> /errorReport:prompt" >>> Creating temporary file >>> "c:\callidusOutput\release\RSP00000928924912.rsp" with contents >>> [ >>> /O2 /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >>> "_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >>> /Zc:forScope- /Yc"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >>> /Fo"c:\callidusOutput\release\\" /Fd"c:\callidusOutput\release\vc80.pdb" >>> /W0 /c /ZI /MP >> **** >> Note that if you have gone in and modified the settings for ONE PARTICULAR file, these >> "local" settings override the "global" settings for your project. So if your project uses >> /Od /ZI and your file says /O2 /ZI, then your file will have these conflicting settings. >> >> Note that for release mode, you should never use /ZI, ever, under any circumstances, >> because it presumes a debug mode edit-and-continue model is being used. Therefore, if >> this represents an "unoptimized" Release build, the use of /ZI is what is erroneous, every >> place it is used. You should use /Zi for release builds, whether you are using /Od or /O2 >> or any other optimization settings. >> >> It looks to me like you have a local file override here. >> **** >>> ".\ASCII Format.cpp" >>> ] >>> Creating command line "cl.exe >>> @c:\callidusOutput\release\RSP00000928924912.rsp /nologo >>> /errorReport:prompt" >>> Creating temporary file >>> "c:\callidusOutput\release\RSP00000A28924912.rsp" with contents >>> [ >>> /O2 /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >>> "_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >>> /Zc:forScope- /Yu"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >>> /Fo"c:\callidusOutput\release\\" /Fd"c:\callidusOutput\release\vc80.pdb" >>> /W0 /c /ZI /MP >> **** >> Ditto. Make sure you have not overridden the setting for this individual file >> **** >>> .\F_Fdraw.cpp >>> >>> >>> ] >>> Creating command line "cl.exe >>> @c:\callidusOutput\release\RSP00000A28924912.rsp /nologo >>> /errorReport:prompt" >>> Creating temporary file >>> "c:\callidusOutput\release\RSP00000B28924912.rsp" with contents >>> [ >>> /Od /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >>> "_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >>> /Zc:forScope- /Yu"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >>> /Fo"c:\callidusOutput\release/Carpettl1.obj" >>> /Fd"c:\callidusOutput\release\vc80.pdb" /W0 /c /ZI /MP >>> >>> .\Carpettl.cpp >>> ] >>> Creating command line "cl.exe >>> @c:\callidusOutput\release\RSP00000B28924912.rsp /nologo >>> /errorReport:prompt" >>> Creating temporary file >>> "c:\callidusOutput\release\RSP00000C28924912.rsp" with contents >>> [ >>> /Od /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >>> "_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >>> /Zc:forScope- /Fo"c:\callidusOutput\release\\" >>> /Fd"c:\callidusOutput\release\vc80.pdb" /W0 /c /ZI /MP >>> >>> .\gpc.c >>> ] >>> Creating command line "cl.exe >>> @c:\callidusOutput\release\RSP00000C28924912.rsp /nologo >>> /errorReport:prompt" >>> Creating temporary file >>> "c:\callidusOutput\release\RSP00000D28924912.rsp" with contents >>> [ >>> /Od /Ob1 /Oi /Ot /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "VISUAL" /D >>> "_VC80_UPGRADE=0x0710" /D "_AFXDLL" /D "_MBCS" /GF /FD /EHa /MD /Gy >>> /Zc:forScope- /Yu"all.h" /Fp"c:\callidusOutput\release\Callidus.pch" >>> /Fo"c:\callidusOutput\release/RollCut_Fitting1.obj" >>> /Fd"c:\callidusOutput\release\vc80.pdb" /W0 /c /ZI /MP >>> >>> .\RollCut_Fitting.cpp >>> ] >>> Creating command line "cl.exe >>> @c:\callidusOutput\release\RSP00000D28924912.rsp /nologo >>> /errorReport:prompt" >>> Output Window Compiling... >>> cl : Command line error D8016 : '/O2' and '/ZI' command-line options are >>> incompatible >>> Results Build log was saved at >>> "file://c:\callidusOutput\release\BuildLog.htm" >>> callidusXML - 1 error(s), 0 warning(s) >> Joseph M. Newcomer [MVP] >> email: newcomer(a)flounder.com >> Web: http://www.flounder.com >> MVP Tips: http://www.flounder.com/mvp_tips.htm >Joseph > >Again, many thanks for the help - I can certainly see where the O2 >settings are coming from now. > > >Is there a way to clear any file override settings for an entire >project. Other than going through every single one > >I have looked on google but cant find anything obvious > >Phil Joseph M. Newcomer [MVP] email: newcomer(a)flounder.com Web: http://www.flounder.com MVP Tips: http://www.flounder.com/mvp_tips.htm
From: Scot T Brennecke on 9 Sep 2009 00:05 phil oakleaf wrote: > Volker Enderlein wrote: >> Hi Phil, >> >> On 08/09/2009 00:28, phil oakleaf wrote: >>> I'm trying to compile with full debug information >>> >>> >>> In the optimisation I've set >>> Optimisation Disabled (/Od) >>> >>> debug info set to >>> Program Database for Edit & Continue (/ZI) >>> >>> >>> But the compiler complains >>> '/O2' and '/ZI' command-line options are incompatible >>> >>> Any help will be Much appreciated >>> >>> Phil >> >> you can set the optimization switch for both the source file (*.cpp) >> and the project (*.vcproj). And, the settings in the source file will >> always overwrite the settings in the project file. >> I suppose you have set the optimization switch for a separate source >> file and changed it now in the project file. If you can't locate it in >> the Visual Studio GUI you might use your favorite text editor and >> search for /O2 in the project file (which is plain XML). >> >> Cheers Volker >> > that's it > > Many thanks > Just have to work through and find them now > > Phil You can the individual .cpp files in the Solution Explorer and open the properties. If there are any settings that are not default, they should be shown in bold. You can also use multi-selection to do several files at once. You can usually choose the "<Inherit...>" option to let it revert to whatever the default or project-wide setting is.
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 Prev: How to serialize Mfc template dialog class ? Next: 063770 M3i Zero , Ezflash Dsi , R4i Dsi 68210 |