Roger Breton wrote:
I'm trying to compile Argyll 0.60 using the Microsoft Visual C++ Express. I'm trying to understand the various dependencies in your source and my c is very rusted. But I'm in no rush. This is fun. I looked at Jam. The thing is I'd like to step through your code, once compiled, to execute it for my own understanding but I don't think that can be done with Jam?
I'm not familiar enough with VC++ Express to know how much it differs from VCPP 6.0, which Argyll does compile under. Typically, on a directory by directory basis I will enable debugging by changing the top of the Jamfile from: CCFLAGS += $(CCOPTFLAG) ; # Turn optimization on #CCFLAGS += $(CCDEBUGFLAG) ; # Debugging flags to #CCFLAGS += $(CCOPTFLAG) ; # Turn optimization on CCFLAGS += $(CCDEBUGFLAG) ; # Debugging flags and trigger a recompile, either by "touch"ing the sources, or removing *.obj *.lib So it's a bit tedious to turn debugging symbols on for everything, and I would just recompile the libraries and application directories as I need them. If the compiler needs other options, then the procedure would be to modify the Jambase file being used to add a sections that is used for that particular compiler, and modify the definitions of CCOPTFLAG and/or CCDEBUGFLAG. Graeme Gill.
Roger Breton