Glenn Linderman wrote:
So I installed MS VC++ 6.0, the MSDN of the same era, and the XP SP2
Platform SDK and (comes with it I guess) MS Visual C++ Toolkit 2003.
I reinstalled Tortoise CVS, checked out a new Win32-GUI directory, and
tried a compile. It failed to compile AxWindow.dll, proclaiming that:
uuid.lib(servprov_i.obj) : fatal error LNK1103: debugging information
corrupt; recompile module.
Vague memories. Some time ago Microsoft made a non backwards compatible
change to the debug info format, meaning that they don't work with VC6.
There are a number of ways around this.
(1) Install old PSDK (Feb 200? was the last one MS claimed compatibility
with VC6, sorry but I don't remember the exact year).
(2) Use the VC2003 compiler. There are reports that this can cause
problems, as it links with a different version of the C-runtime, but I
have made it work by copying msvcrt.lib from my VC6 lib directory, and
putting it in the VC2003 lib directory.
(3) {This is how I currently build Win32::GUI with VC6 and the Win2003
Server SP1 PSDK):
- set the INCLUDE environment variable to point to the following
directories:
PSDK\Include;PSDK\Include\mfc;VC98\ATL\INCLUDE;VC98\INCLUDE;VC98\MFC\INCLUDE
- set the LIB environment variable to point to the following directories:
VC98\LIB;VC98\MFC\LIB;PSDK\Lib
where PSDK is the root of your PSDK install, and VC98 is the root of
your VC6 install. The search order is important.
(4) I suspect that you could set the search order for libs to be PSDK
then VC98, and delete/rename any .lib files that give problems from the
PSDK Lib directory.
(5) (Possibly easiest, but I never tried this): edit the makefile
(CFLAGS, LDFLAGS, LDDLFLAGS, OPTIMIZE) to remove the -debug and -Zi
options (maybe others?), so that you are not requesting the debug
information.
Regards,
Rob.
