[sprange]

Thanks for the reply. I’ve tried a few alternatives to VisualGDB but I think this program is a winner. I tracked down a few problems relating to the verification of the tool chain. I’ve learned that it’ll complain even if there isn’t a problem. For example if I have something like this in the library path of the setup window

(in Configuration Makefile Settings)
Library directions: something$(BINARYDIR)
Library names: something

The test will fail to find libsomething.a but if I ignore the toolchain error I’ll be able build and link against libsomething without a problem.

I’m still having problems with large projects that have multiple executables in the same directory. I either have to use a solution with many different projects (each in their own directory which is not convenient), or I need to master the VGD makefiles. I find it difficult to have more than one target in the makefile. I really wish I could just use the ones in the project (with some modifications) but that is challenging too!

[Author]

Posts