X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=doc%2Fld65.sgml;h=0230b517fbc4969c148b91e44ef9672bd7aefe35;hb=e767c8990d07003d9c91a6151cc61f0ea28639ea;hp=f4cbebbe9601ac51d3bbcaa112758fcd039ead9a;hpb=d8ad89c4b4e3ee92ad128193f2cd3fab41f5b6cf;p=cc65 diff --git a/doc/ld65.sgml b/doc/ld65.sgml index f4cbebbe9..0230b517f 100644 --- a/doc/ld65.sgml +++ b/doc/ld65.sgml @@ -3,7 +3,6 @@
ld65 Users Guide <author><url url="mailto:uz@cc65.org" name="Ullrich von Bassewitz"> -<date>2014-04-20 <abstract> The ld65 linker combines object files into an executable file. ld65 is highly @@ -67,7 +66,7 @@ Short options: -m name Create a map file -o name Name the default output file -t sys Set the target system - -u sym Force an import of symbol `sym' + -u sym Force an import of symbol 'sym' -v Verbose mode -vm Verbose map file @@ -77,7 +76,7 @@ Long options: --dbgfile name Generate debug information --define sym=val Define a symbol --end-group End a library group - --force-import sym Force an import of symbol `sym' + --force-import sym Force an import of symbol 'sym' --help Help (this text) --lib file Link this library --lib-path path Specify a library search path @@ -175,6 +174,7 @@ Here is a description of all of the command-line options: <item>sim6502 <item>sim65c02 <item>supervision + <item>telestrat <item>vic20 </itemize> @@ -487,7 +487,7 @@ There are of course more attributes for a memory section than just start and size. Start and size are mandatory attributes, that means, each memory area defined <em/must/ have these attributes given (the linker will check that). I will cover other attributes later. As you may have noticed, I've used a -comment in the example above. Comments start with a hash mark (`#'), the +comment in the example above. Comments start with a hash mark ('#'), the remainder of the line is ignored if this character is found. @@ -572,7 +572,7 @@ default behaviour is OK for our purposes, I did not use the attribute in the example above. Let's have a look at it now. The "file" attribute (the keyword may also be written as "FILE" if you like -that better) takes a string enclosed in double quotes (`&dquot;') that specifies the +that better) takes a string enclosed in double quotes ('&dquot;') that specifies the file, where the data is written. You may specify the same file several times, in that case the data for all memory areas having this file name is written into this file, in the order of the memory areas defined in the <tt/MEMORY/ @@ -894,7 +894,7 @@ look like this: } </verb></tscreen> -The only other available output format is the o65 format specified by Andre +There are two other available formats, one is the o65 format specified by Andre Fachat (see the <url url="http://www.6502.org/users/andre/o65/fileformat.html" name="6502 binary relocation format specification">). It is defined like this: @@ -904,7 +904,20 @@ name="6502 binary relocation format specification">). It is defined like this: } </verb></tscreen> -The necessary o65 attributes are defined in a special section labeled +The other format available is the Atari (xex) segmented file format, this is +the standard format used by Atari DOS 2.0 and upward file managers in the Atari +8-bit computers, and it is defined like this: + +<tscreen><verb> + FILES { + %O: format = atari; + } +</verb></tscreen> + +In the Atari segmented file format, the linker will write each <tt/MEMORY/ area +as a new segment, including a header with the start and end address. + +The necessary o65 or Atari attributes are defined in a special section labeled <ref id="FORMAT" name="FORMAT">. @@ -925,6 +938,15 @@ has several attributes that may be defined here. } </verb></tscreen> +The Atari file format has only one attribute, <tt/RUNAD/ that allows to specify +a symbol as the run address of the binary. If the attribute is omiteed, no run +address is specified. + +<tscreen><verb> + FORMATS { + atari: runad = _start; + } +</verb></tscreen> <sect1>The FEATURES section<label id="FEATURES"><p>