Cannot compile a debug DLL

[Admiral Armada]

Im trying to bug hunt, and so im trying to make a debug DLL, everything goes fine until it gets to CyCityInterface1.cpp, then i get this error

1>c:\Program Files\Microsoft Visual C++ Toolkit 2003\include\memory(498) : fatal error C1067: compiler limit : debug information module size exceeded
1>NMAKE : fatal error U1077: '"C:/Program Files/Microsoft Visual C++ Toolkit 2003/bin/cl.exe"' : return code '0x2'
1>Stop.

How can i fix this?

 

[davidlallen]

You did not mention which mod(s) you are compiling. I assume that you can compile a debug dll for vanilla without this problem. Even in vanilla, some classes are split into multiple files, such as CyGlobalContextInterface1,2,3,4.cpp. This split is done to avoid the problem you describe. My guess is that whatever mod you are compiling, went just slightly above this limit and the mod's author did not need to compile debug.

If the mod's author is not available or not responding, you can try moving a chunk of functions from CyCityInterface1.cpp into CyCityInterface2.cpp.

 

[Admiral Armada]

Thanks, ill give it a shot.

 

[Baldyr]

Is it even necessary to make a debug DLL? Because I remember reading in another thread that you could just skip it, especially if you're having issues with it. (Or was that just when doing minor changes or edits? I don't remember.)

But nothing wrong with trying to learn how to do things proper!

 

[NotSoGood]

Is it even necessary to make a debug DLL? Because I remember reading in another thread that you could just skip it, especially if you're having issues with it. (Or was that just when doing minor changes or edits? I don't remember.)

But nothing wrong with trying to learn how to do things proper!

No, it's not necessary but it helps a lot when trying to figure out why your mod crashes.

 

[Fimbulvetr]

I still have the same problem as ever, even after I finally updated my VS 2003 to SP1.
Python fails to initialise, debug msg tells me exe C++ exception: boost::python::error_already_set @ 0x0013ecb8
Does anyone know have any idea what I could be doing wrong? Am I missing something like a newer PSDK since only .Net 1.1 came with VS2003?

Well, at least "Final Debug" is running. No call stacks but I still get Asserts.