Purpose of .COD file

[JBotAlan]

I am just curious: what is the purpose of MPLAB's .COD file? Why does it convert the .COFF to .COD before converting the .COFF to .HEX? Is there another application that looks at the .COD for something? Is there a way to turn off .COD file conversion--I don't think I need it?

JBot

EDIT: Never mind; I found it. Project > Build Options > Project, MPLINK Linker tab, "Surpress COD-file generation" checkbox.

[Joe Ross]

The only reason to generate the COD file (for our purposes) is because it also generates the list file. If you have no reason to look at the list file, you don't have to generate the COD file and can get around the 62 character path limitation.

[JBotAlan]

Originally Posted by Joe Ross

The only reason to generate the COD file (for our purposes) is because it also generates the list file. If you have no reason to look at the list file, you don't have to generate the COD file and can get around the 62 character path limitation.

The list file? That would be the file with how many bytes you have of code, right? Or is it the raw machine code? I don't really have a need to look at either, at least not right now.

I turned it off, and it shaved a whopping *1.24 seconds* off my compile time!! Woo hoo!

Thanks
JBot

[Uberbots]

^That means you have about 1.24 seconds more to finish up a tuned loop before an important match (=

yeah... ive been there.

[Joe Ross]

Originally Posted by JBotAlan

The list file? That would be the file with how many bytes you have of code, right? Or is it the raw machine code? I don't really have a need to look at either, at least not right now.

The list file shows the machine code. It's nice because it's side by side with the C code, so you can see exactly how efficient or inefficient your code is.

The map file shows the memory usage.