News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

General questions

Started by johne53, April 20, 2007, 11:55:52 PM

Previous topic - Next topic

johne53

#30
This is the full build log that I'm seeing:-

QuoteExecution of 'cl.exe /nologo /MD /W3 /GX /O2 /DWIN32 /DNDEBUG /D_WINDOWS /D_AFXDLL /FD /Zp1 /D_MBCS /DFILETREECTRL_NO_RESOURCES  /I"E:\Program Files\Microsoft Visual Studio\VC98\Bin\include" /I"D:\Program Files\ComboDemoNew" /c "D:\Program Files\ComboDemoNew\ComboDemo.cpp" /FoRelease\ComboDemo.obj' in 'D:\Program Files\ComboDemoNew' failed.
Nothing to be done.

That was in response to pressing CTRL+SHIFT+F9 (i.e. just attempting to compile 1 x source file). I've tried 2 x compilers - namely Visual C++ 6.0 and Visual C++ 2003. I get the same message in either case. I can't help feeling that I need to 'turn something on' in order to see the compiler's actual output. Or do I maybe have to redirect it somewhere (e.g. via a pipe?)

MortenMacFly

Please post a minimal example to reproduce. MS Visual C++ v6.0 isn't supported by C::B natively. It can be attached (there is an article in the WiKi) but I wonder if you had used that information?
Anyway: Have a look at my sig to see the full compiler command...
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

johne53

Thanks Morten. I switched to "Full command line" which simply gives me this output:-

Quotecl.exe /nologo /MD /W3 /GX /O2 /DWIN32 /DNDEBUG /D_WINDOWS /D_AFXDLL /FD /Zp1 /D_MBCS /DFILETREECTRL_NO_RESOURCES  /I"E:\Program Files\Microsoft Visual Studio\VC98\Bin\include" /I"D:\Program Files\ComboDemoNew" /c "D:\Program Files\ComboDemoNew\ComboDemo.cpp" /FoRelease\ComboDemo.obj
Execution of 'cl.exe /nologo /MD /W3 /GX /O2 /DWIN32 /DNDEBUG /D_WINDOWS /D_AFXDLL /FD /Zp1 /D_MBCS /DFILETREECTRL_NO_RESOURCES  /I"E:\Program Files\Microsoft Visual Studio\VC98\Bin\include" /I"D:\Program Files\ComboDemoNew" /c "D:\Program Files\ComboDemoNew\ComboDemo.cpp" /FoRelease\ComboDemo.obj' in 'D:\Program Files\ComboDemoNew' failed.
Nothing to be done.

I'll try the wiki and if that doesn't make things any clearer, I'll post a small project.

johne53

I think that the wiki must be referring to an older version. It says:-

QuoteThe compiler/linker setup (tab "Directories) should be done as following:
Under the tab "Compiler" add the following path's:
{YOUR_MSVC6}\VC98\Include
{YOUR_MSVC6}\VC98\MFC\Include
{YOUR_MSVC6}\VC98\ATL\Include

Under the tab "Linker" add the following path's:
{YOUR_MSVC6}\VC98\Lib
{YOUR_MSVC6}\VC98\MFC\Lib

Under the tab "Resource compiler" add the following path's:
{YOUR_MSVC6}\VC98\Include
{YOUR_MSVC6}\VC98\MFC\Include
{YOUR_MSVC6}\VC98\ATL\Include


However, I can't seem to find any of those tabs...  :(

Charon

Some time ago one tab-page was changed to a drop-down list.

Select "Search directories" in dthe drop-down list, then you will see your tabs.

Markus

[attachment deleted by admin]
hi, i am a signature virus. please copy me into your sig!
Wish list : no root-node for workspaces, open files and symbols; world domination

johne53

Woohoo...! It's looking good.... I still need to add a few more search directories (to match my existing setup) but finally, I seem to be seeing real compiler warnings.  :D

johne53

I've managed to build and run a complete MFC application but I'm not sure whether I'll be able to debug it (i.e. single stepping etc). Would I need to use a separate debugger to achieve this? As far as I can see, there's no separate debugger supplied with VC++.