On 30.10.21 20:14, Basil Hussain wrote:
Okay, it's not just me:
https://stackoverflow.com/questions/53608761/cant-get-define-working-with-sdasz80-sdcc-assembler
So, apparently it *isn't* supported in SDAS? Why on earth is it
mentioned so frequently in the bundled docs, then? Why do the sdas*
executables have a -b argument for displaying .define substitutions in
source listings?
Regards,
Basil Hussain
On 30/10/2021 16:32, Basil Hussain wrote:
Hi all,
Does the version of ASxxxx used for SDAS assemblers not support
.define directives?
I am tearing my hair out trying to figure out if it doesn't actually
support those directives, or whether I am being a giant idiot and
doing something incorrectly.
My simple scenario: I have two assembly code files, foo.s and bar.s;
in each I want to .define some keywords with a value and then .include
a third file, common.s, where those keywords are to be substituted. An
example of what one of the two files contains:
.define SOME_VALUE "4"
.define aaaa "xxxx"
.define bbbb "yyyy"
.include "common.s"
But SDAS just gives me "Error: <o> .org in REL area or directive /
mnemonic error" for every line containing a .define directive.
I was starting to wonder if it was a feature that was added to only
mainline ASxxxx more recently than when forked, but the .define
directive (and it's siblings, .undefine, .ifdef, .ifndef, etc.) is
actually mentioned in the SDAS docs that are included with SDCC.
So what is going on here?
Regards,
Basil Hussain
[r13056] ported .define, so it’s in the next branch. So far it’s only
enabled in sd6500, but I’m sure it will be enabled for other ports. It
has to be explicitly enabled for each assembler. I don’t want to blindly
enable it for all ports before next is merged back into trunk, which
means after 4.2.0 is released.
--
Freundliche Grüße / Yours sincerely
Sebastian „Baŝto“ Riedel
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user
