JLoc: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
Content added Content deleted
No edit summary |
m (download is still available...) |
||
| Line 1: | Line 1: | ||
JLoc was written by John Fines |
JLoc was written by John Fines. It is available from [http://my.execpc.com/~geezer/johnfine/#zero here]. |
||
:"This program is a linker/locator for use when you need more control over placement of sections within the image, than a standard linker provides." |
:"This program is a linker/locator for use when you need more control over placement of sections within the image, than a standard linker provides." |
||
Revision as of 22:10, 8 September 2007
JLoc was written by John Fines. It is available from here.
- "This program is a linker/locator for use when you need more control over placement of sections within the image, than a standard linker provides."
JLoc can be tricky to use for first timers. Carefull reading of the documentation is required. Its not a get-up-and-go linker like all the other linkers. JLoc requires you to write a custome script for each "executable" image you want to link. JLoc gives you flexibility over HOW the object files are linked, regarding loaded addresses and so-forth.
- Pros
- Supports OMF/OBJ, DJGPP/COFF
- Supports 32bit code
- Supports flat binary file generation
- Handles library files (OMF/OBJ)
- OMF/OBJ debugging information
- Free
- Cons
- Does not support any output file formats other than flat binary and DOS/COM
- Confusing to use for beginners
- Can't create shared libraries