Well, you *can* compile with SDCC and link with SDLD, but that would be more complicated - SDCC "autogenerates" a whole set of switches for SDLD (in xxx.lnk file, which is passed as input to SDLD).

With Keil, you usually use the IDE (uVision) to "hide" the details of preprocessor-compiler-assembler-linker invocation.

With SDCC, it is SDCC itself supposed to do this "hiding". This works well for a single-source-file case, "SDCC source.c" indeed produces directly "source.hex"; but SDCC is not perfect enough to do the same with multiple sources.

With many "traditional" C compilers, the "integrating" "main" executable doing the "hiding" allows simply to enter many c sources and performs all the compilation and linking, i.e "cc main.c sub1.c sub2.c sub3.c" results directly in "main.hex" or whatever. SDCC can't do this [so far].

I see how this is confusing for somebody with experience with other C compilers, but by now you have already managed, I suppose?

Jan