Hey guys,
I'm getting an issue with multilevel include statements (include statement within included files) where it puts the include path in the resulting executable, all compiles fine and everything but it's making my exes big.... Any idea how to stop this?
Quote from: oex on February 26, 2010, 02:10:07 PM
Any idea how to stop this?
Turn off the debug options in ML and LINK? Kind of assuming the only place the include file names/paths get into the EXE is via the debug records, or are you seeing it somewhere else?
-Clive
Using Masm32 default build options so no debug I dont think.... The paths are actually in the .exe when I open it in notepad
EDIT: To clarify and expand on the issue the includes are in the .code portion of the app and contain procs
If you forget to take out the debug macros, there will be paths in you exe.. If you use PrintStringByAddr, PrintDec and such, see if you left them in your code.
I must have done, I made some severe mods last night and they disappeared, not sure which debug macro I used but they are gone now :) ty for your help guys