zcc: module names in generated libraries are temp file names rather than original filenames about z88dk HOT 5 CLOSED

zcc is going to be passing a mass of files not usually one at a time and quite often as a list of files in a single .lst file to avoid command line limitations. So I don't think there is any way to add a command line parameter sensibly.

Actually that's not right. I couldn't remember if zcc passes files at the .asm stage or the .o stage to z80asm for building a library but it is the .o stage. So that means zcc individually assembles each .asm file and it would be possible to pass the original filename as command line parameter to z80asm.

Right now that parameter would become the module name.

from z88dk.

z80asm MODULE directive does just that. It replaces the source file name by the name given as argument in the linked file. zcc just has to add "MODULE original_file" to every temporary file before assembling.

In my plan for z80asm2 the linked module will be named <source_file>_<module_directive_name>

from z88dk.

Will z80asm be okay with receiving two module directives?

If zcc inserts one in the front and the user has specified one which would appear second, will z80asm be able to use the last one declared?

In my plan for z80asm2 the linked module will be named <source_file>_<module_directive_name>

Yes this is what I was thinking about. In the future, it's the source_file name that zcc should be tweaking and not the module.

from z88dk.

If zcc inserts one in the front and the user has specified one which would appear second, will z80asm be able to use the last one declared?

Today there's an error message on the second module directive. But this can be easily changed, as the module name is not used except for the name in the .o file.

from z88dk.

zcc now inserts a module directive at the start of every file at the .asm stage.

• We've moved away from shell invokes of copy and cp to shell invokes of type and cat for appending
• CRTs must have module directives at the top since they are processed outside zcc's loop

To form the module string, the basename is taken and non-alnum chars are replaced with '_'. So a file "clisp.c" will get module name "clisp_c" and a file "clisp.asm" will get module name "clisp_asm".

Tested on windows and this change fixes the zcc lib issue as well as makes the map file clearer.

from z88dk.