Codeblocks integrate with Visual Toolkit 2003

[jozzzz]

  Good morning,  I'd want to Codeblocks integrate with Visual Toolkit 2003, but I have this both on disc F. Even if I enter path correct F:\Program Files\Microsoft Platform SDK\Lib\AdvAPI32.Lib etc., Codeblocks always use his header file , which hold in his directory.


What I be able to do, as to Codeblocks received setting  paths F:\Program Files\Microsoft Platform SDK\Lib\AdvAPI32.Lib?
Thank you P.

[MortenMacFly]

What I be able to do, as to Codeblocks received setting  paths F:\Program Files\Microsoft Platform SDK\Lib\AdvAPI32.Lib?

Die you setup the compiler for your project correctly? Did you setup the PATH for the include files and lib files correctly? Anyway: If you provide your project with a specific lib this doesn't neccesarily mean that a specific header file is used. These are 2 things: compiling and linking. Both steps require a correct path to be setup. Could you send the full compiler log of a project of yours explaining better what you are doing?!
With regards, Morten.
BTW: Making words bold doesn't always increase readability... I guess we would have understand your post without bold phrases, too. ;-)

[Michael]

Hello,

You can have a look at this helpful C::B wiki article.

Best wishes,
Michael

[jozzzz]

Now path is OK  I think, but new message:
LINK : fatal error LNK1158: cannot run 'cvtres.exe'

But I insert path to Settings-Compiler-Programs-Additional paths - F:\Program Files\Microsoft Platform SDK\Bin\win64.
Why is this message? Thanx P.



This is Build log:
Project   : Win32 Application
Compiler  : Microsoft Visual C++ Toolkit 2003 (called directly)
Directory : G:\docum_nty\PROJEKTY VC++\codeblocks_pokus\
--------------------------------------------------------------------------------
Switching to target: default
F:\Program Files\Microsoft Platform SDK\Bin\rc.exe  /I"F:\Program Files\Microsoft Platform SDK\Bin"  /I"F:\Program Files\Microsoft Platform SDK\Bin"  -fo.objs\main.res main.rc
C:\Program Files\Microsoft Visual C++ Toolkit 2003\bin\link.exe /nologo /subsystem:windows   /LIBPATH:"C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib" /LIBPATH:"F:\Program Files\Microsoft Platform SDK\Lib"  /LIBPATH:"C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib" /LIBPATH:"F:\Program Files\Microsoft Platform SDK\Lib" /out:"G:\docum_nty\PROJEKTY VC++\codeblocks_pokus\Win32GUI.exe"   "F:\Program Files\Microsoft Platform SDK\Lib\ComCtl32.Lib" "F:\Program Files\Microsoft Platform SDK\Lib\AdvAPI32.Lib" "F:\Program Files\Microsoft Platform SDK\Lib\Gdi32.Lib" "F:\Program Files\Microsoft Platform SDK\Lib\User32.Lib"  "F:\Program Files\Microsoft Platform SDK\Lib\AdvAPI32.Lib" "F:\Program Files\Microsoft Platform SDK\Lib\Gdi32.Lib" "F:\Program Files\Microsoft Platform SDK\Lib\User32.Lib" "F:\Program Files\Microsoft Platform SDK\Lib\ComCtl32.Lib" .objs\main.o  .objs\main.res   
LINK : fatal error LNK1158: cannot run 'cvtres.exe'
Process terminated with status 1 (0 minutes, 0 seconds)
 

[Michael]

Now path is OK  I think, but new message:
LINK : fatal error LNK1158: cannot run 'cvtres.exe'

Have a look at here.

If you want more info then try a search with e.g., cvtres.exe :wink:.

Best wishes,
Michael

PS.: It is not necessary to use bold... :roll:

[MortenMacFly]

LINK : fatal error LNK1158: cannot run 'cvtres.exe'

If you want to compile Win32 applications you'll also most likely require the MS platform SDK. This will include cvtres.exe. This all is written in the WiKi. I really suggest you read this.
With reagrds, Morten.

[jozzzz]

Thanx for all ,  Codeblocks make program successfull. .

[jozzzz]

Another question:
What debuger I can use , when  I have integrated Visual Toolkit?

[MortenMacFly]

What debuger I can use , when  I have integrated Visual Toolkit?

You are quite resistant to the WiKi, aren't you?! :?
C::B supports the CDB - the Microsoft debugger that ships with the free MS Debugging tools - directly.
With regards, Morten.

[jozzzz]

MVC Toolkit 2003  does not contain   CDB.exe

[MortenMacFly]

MVC Toolkit 2003  does not contain   CDB.exe

Yes, the MSVC Toolkit is not the same as the MS Debugging tools. Basically for (free) MSVC development you'll need 3 packages: The MSVC Toolkit (compiler, basic libs); the MS Platform SDK (all platform specific "deep level" stuff) and the MS Debugging tools for debugging purposes. Please note that this does not include MFC. Again: You should find this information in the WiKi, too.
With regards, Morten.

[jozzzz]

I download .NET.FRAMEWORK.SDK.1.1, but   does not contain   CDB.exe , where i can get this?  :?

[squizzz]

I don't use MSVT, but if there is no CDB.exe in .NET Framework SDK then it must be either somewhere here:
Debugging Tools for Windows
or here:
Platform SDK.

[jozzzz]

Well , i have F:\Program Files\Debugging Tools for Windows\cdb.exe,but i get this messagebox:
The debugger executable i not set. To set it, go to "Settings/Configure plugins/Compiler",switch to the"Programs" tab and select the debuger program.

But Settings no contain "Configur plugins"
I do sett in program tabs:
Debugger: F:\Program Files\Debugging Tools for Windows\cdb.exe
but if i press F8, i get messagebox -- The debugger executable i not set. To set it, go to "Settings/Configure plugins/Compiler etc.

[squizzz]

That's probably some legacy message pointing to wrong place (wrong since settings dialog redesign


First, navigate to Settings->Compiler and debugger->Programs .
Then either read what red label says (:lol:) or set debugger field to cdb.exe (no path!) and then go to Additional Paths tab and add F:\Program Files\Debugging Tools for Windows (or whatever path is correct).

That should help.

[rennie84]

squizz, I followed that, and the debugger seems to run, but it doesnt actually run my program Here is the debugger output:

Selecting target: Debug
Compiling: done
Adding source dir: D:\Source\snn\
Adding source dir: D:\Source\snn\
Adding file: snn.exe
Starting debugger: done
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Debugger finished with status 1

And then it just finishes. Am I missing something?

[squizzz]

@rennie84 - right click on your project (project tree), click Build options and check if "Produce debugging symbols" (or similar - I don't use visual toolkit...) is checked. If it is not, check it and rebuild whole project and then try to debug again.
If this doesn't help, please post more details (version of C::B & operating system you use), so someone who actually uses Visual Toolkit can help you.

[rennie84]

Yeah I tried that to no evail :p

Im using the latest nightly build with DMD as the compiler - Im actually using Code::Blocks for a D project.

Ive pointed the Debugger to dbc.exe from the Platform SDK.

The problem seems to be that my program isnt actually getting launched by the debugger

[killerbot]

only GDB and CDB as debuggers are supported !

[rennie84]

oops sorry thats what I meant - im using cdb.exe

[killerbot]

cdb.exe is the one from MS isn't it ?
I always used GDB in CB so no idea how well it goes with cdb.
Can cdb do the D language ?

[squizzz]

Might be that C::B doesn't pass some compiler switches (like debug switch) for DMD compiler correctly...

You might try to set Compiler logging to "Full command line" (Settings->Compiler and debugger->Other) and see what parameters are used to invoke compiler. Compare how compiler calls look like when "Produce debugging symbols" property is set and when it is unset. If there is no difference between these two, it's possible that binary being produced by compiler is not suitable for debugging.   (false alarm - this seems to work correctly)

Oh, and that

Can cdb do the D language ?

is also very good question...

[jozzzz]

 I am enter paths :
Debugger:F:\Program Files\Debugging Tools for Windows\cdb.exe
Additional Paths: F:\Program Files\Debugging Tools for Windows\

but no way