User forums > Using Code::Blocks

Windows resource problem

<< < (2/2)

RandomMan:
And the tooltip problem ended up being the fact that MS had superceded the 'TOOLTIPTEXT' structure with the 'NMTTDISPINFO' structure, and of course, the newer headers illuminated this.

Does anyone know of a good tutorial on using WinDbg for normal debugging?  I was unable to even figure out how to get WinDbg to find the symbols for my app, although the file had been created.  (Or at least I think it wasn't finding the symbols.  It is slightly overwhelming to a beginner.)

David

Vampyre_Dark:
I never had to mess around with the linker commands, I just had to make sure all the proper stuff had it's folder included. I think CB had some problem wanting everything to be under the same folder, when the platform SDK has it's own bin folder or something like that.

mandrav:

--- Quote from: Vampyre_Dark on October 20, 2005, 06:26:19 pm ---I never had to mess around with the linker commands, I just had to make sure all the proper stuff had it's folder included. I think CB had some problem wanting everything to be under the same folder, when the platform SDK has it's own bin folder or something like that.

--- End quote ---

That was true at some point, but since mid-summer C::B supported compiler programs residing in multiple paths (see Settings->Compiler->Programs->Additional paths).

The problem discussed here was a wrong compilation command-line, which has been fixed in CVS.

Vampyre_Dark:

--- Quote from: mandrav on October 20, 2005, 07:28:33 pm ---
--- Quote from: Vampyre_Dark on October 20, 2005, 06:26:19 pm ---I never had to mess around with the linker commands, I just had to make sure all the proper stuff had it's folder included. I think CB had some problem wanting everything to be under the same folder, when the platform SDK has it's own bin folder or something like that.

--- End quote ---

That was true at some point, but since mid-summer C::B supported compiler programs residing in multiple paths (see Settings->Compiler->Programs->Additional paths).

The problem discussed here was a wrong compilation command-line, which has been fixed in CVS.

--- End quote ---

I think I remember better... the problem was that the program looked for the resrouce stuff in the compiler's bin folder even when extra folders were specified. You had to put the whle path for it to work.

Navigation

[0] Message Index

[*] Previous page