X-Git-Url: https://git.sur5r.net/?p=cc65;a=blobdiff_plain;f=doc%2Fcl65.sgml;h=0291f2eb31cc22ab423cab2b07459006f7868b09;hp=c6761ed9e14b01a13aa336f103e5ccb2695dadba;hb=74455508314bc2b007e812ec5f9429496b9fbd5f;hpb=b9ea77b18588d24a8bc84f10db7c73f5fceca4f5 diff --git a/doc/cl65.sgml b/doc/cl65.sgml index c6761ed9e..0291f2eb3 100644 --- a/doc/cl65.sgml +++ b/doc/cl65.sgml @@ -236,14 +236,14 @@ package, it tries to be smart about several things. - If you don't give a target system on the command line, cl65 - defaults to the C64. + If you don't give a target system on the command line, cl65 + defaults to the C64. When linking, cl65 will supply the name of the library file for the target system to the linker; so, you don't have to do that. - If the final step is the linker, and the name of the output file was - not explicitly given, cl65 will use the name of the first input file + If the final step is the linker, and the name of the output file was + not explicitly given, cl65 will use the name of the first input file without the extension, provided that the name of that file has an extension. So, you don't need to give the executable name in most cases; just give the name of your "main" file as the first input file. @@ -284,24 +284,24 @@ assembler file (irq.s) will need the following separate steps to compile into an executable named morse: - cc65 -g -Oi -t c64 morse.c - ca65 -g morse.s - ca65 -g irq.s - ld65 -o morse -t c64 c64.o morse.o irq.o c64.lib + cc65 -g -Oi -t c64 morse.c + ca65 -g morse.s + ca65 -g irq.s + ld65 -o morse -t c64 c64.o morse.o irq.o c64.lib When using cl65, this is simplified to - cl65 -g -Oi morse.c irq.s + cl65 -g -Oi morse.c irq.s As a general rule, you may use cl65 instead of cc65 at most times, especially in makefiles to build object files directly from C files. Use - .c.o: - cl65 -g -Oi $< + .c.o: + cl65 -g -Oi $< to do this. @@ -323,14 +323,14 @@ including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: - The origin of this software must not be misrepresented; you must not - claim that you wrote the original software. If you use this software - in a product, an acknowledgment in the product documentation would be - appreciated but is not required. - Altered source versions must be plainly marked as such, and must not - be misrepresented as being the original software. - This notice may not be removed or altered from any source - distribution. + The origin of this software must not be misrepresented; you must not + claim that you wrote the original software. If you use this software + in a product, an acknowledgment in the product documentation would be + appreciated but is not required. + Altered source versions must be plainly marked as such, and must not + be misrepresented as being the original software. + This notice may not be removed or altered from any source + distribution.