From: ol.sc@web.de   
      
   Hi Colin,   
      
      
   >Hi again Oliver,   
   >   
   >> There's no point in having a target definition (-t apple2) beside a   
   >> linker configuration file on a link-only command line.   
   >>   
   >> In general, there's no need for separate compile and link command   
   >> lines when just generating a program from a single source file.   
      
   [...]   
      
   >I use both -t and -C because if removing -t apple2, I'm getting errors   
   >which makes me think it's trying to compile for c64? :   
      
   Please note that I was talking about compile-only and linky-only   
   command lines. For compile-and-link command lines, it makes of course   
   sense to have both -t ... and -C ...   
      
   For the cc65 compiler, -t ... does all sorts of things you certainly   
   want to have.   
      
   For the ld65 linker, -t xyz is just a shorthand to -C xyz.cfg so it   
   doesn't like to be given both.   
      
   The cl65 tool is clever enough to pass the -t ... only to the linker   
   if there's no -C ... given.   
      
   >(The differences between apple2.cfg and loader.cfg are:   
   >-    __HIMEM__:     type = weak, value = $9600; # Presumed RAM end   
   >+    __HIMEM__:     type = weak, value = $BF00; # Presumed RAM end   
      
   cc65 linker configurations aren't 100% stable. So you are strongly   
   advised to _not_ copy one, just edit a value or two and use the copy.   
   This tends to make your build break in ways you don't understand with   
   later cc65 versions. You're far better off with setting __HIMEM__ from   
   the command line as shown in the documentation.   
      
   Note: If you use, cl65 you need to use -Wl (aka --ld-args) to set   
   __HIMEM__ from the command line - see   
   https://cc65.github.io/doc/cl65.html#s2.   
      
   Regards,   
   Oliver   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)