Right. Once you get used to the VC debugger's quirks though, it's very
>I'm also new to VC++, but I have had an uninstalled VC 5.0 for a few years.
>When I use it to debug the ABI_OPT_DEBUG=1 build of AbiWord, the debugger
>continually asks me to locate source files for it.
Yep, that's exactly how it works. Actually, this process isn't as bad as
you may think. IIRC, VC only asks once per directory, and it'll remember
those locations across sessions if you save the workspace.
>There does not appear to
>be a "the source tree is rooted here" command.
If there is, let us know. :-)
>It seems as if I need to
>build .sbr files by giving the -Fr flag to cl, then using bscmake. Before I
>launch into doing that, let me ask: is that the correct way to make
>debugging "just work"?
If you try that you're likely to run into a similar problem. The diving
makefiles which recurse across a bunch of different modules will cause
headaches for bscmake, which prefers to only analyze one directory at a
In a prior lifetime, Jeff managed to coerce a similar diving make system
into generating one big bad bsc file for the entire product, but it took a
fair amount of makefile tweaking, and increased build times by approximately
a factor of two (or was it four?). Blech.