Phoenix Network Forums

Can anybody tell me the differences between .obj file and .exe file?
i know that in .obj file addresses of each statement of the program is relative to the starting statement. Is there anything else other than this that makes it not executable as such?
bye
take care
chinnu

the .obj file is the file used in the linking phase (library + binary exec generation).

A good link for more details :
See http://caml.inria.fr/pub/docs/oreilly-b ... ra065.html



.

chinnu wrote:i know that in .obj file addresses of each statement of the program is relative to the starting statement. Is there anything else other than this that makes it not executable as such?

In the final program, addresses are still relative, but OBJ files are incomplete. They only contain code for the part of the program compiled, without any library or system code. Also it's not in an executable format, but rather a linker format. In other words: it's intended to be linked into a final program, not to be run directly.

chinnu wrote:Can anybody tell me the differences between .obj file and .exe file?
i know that in .obj file addresses of each statement of the program is relative to the starting statement. Is there anything else other than this that makes it not executable as such?
bye
take care
chinnu

Basically what mm_freak and bugalinux said, OBJ files can be linked to other files, and DLLs. Its a bit different when you use a engine in ASM. I hope thats not confusing

Xaric wrote:Its a bit different when you use a engine in ASM. I hope thats not confusing :)

What do you mean?

Object files do not have all of their dependencies resolved, and there are still address gaps and unkown addresses for functions that reside in other object files or libraries. Usually object files contain the debugger instrumentation, symbol table, static data and base addresses for functions.


Your executable is where everything is put together and all of the questions are answered about missing addresses, etc. Your exe also contains the bootstrap code and kernel hooks such as opening you input and output streams, loading any dynamic libraries, and setting up your call stacks and dumping your core file if something crashes in your code.

Basically your exe is the interface to the operating system from the user command shell.

Wow, gls is Jesus!

Just look at how he reincarnated this thread