Re: [cc65] --create-dep for ca65?

From: "Oliver Schmidt"; on Sat., April 24, 2010; at 04:04 AM -0400
>
> One would need to distinguish between several scenarios:
>
> a) Individual calls to compile a C file:
>
> make calls cc65 with --create-dep; it writes it's "<file>.s: <file>.c
> <incl>.h" to the .u file (it embeds them, as well, into the .s file
> where they don't hurt).

Cc65 already does some of that kind of embedding when you use
the "-g" ("--debug-info") option.

>
> make calls ca65 without --create-dep, as the cc65-generated .s files
> don't have includes anyway.
>
> b) Assemble an asm. file:
>
> make calls ca65 with --create-dep; it writes it's "<file>.o: <file>.s
> <incl>.inc" to the .u file.
>
> c) Compile a C file through cl65:
>
> 1. make calls cl65, which calls cc65 without --create-dep;
> it only embeds its dependencies into the .s file.
>
> 2. make calls cl65, which calls ca65 with --create-dep; it finds the
> embedded dependencies, and writes "<file>.o: <file>.c <incl>.h"
> to the .u file.

"c) 2." is redundant!  Make should run cl65 only once.
Cl65 automatically will run both cc65 and ca65.

It should be made smart enough to know how to generate the appropriate
dependency file.

----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.