At some point, it looks as though coff file generation
was made unconditional, but the code that WRITES to the
file still checks for the argument being specified. As
a result, the coff file is created, but nothing gets
written to it, and we end up with a zero-length foo.coff
after successful assembly.
If the --coff argument is added back in, the filename
argument is ignored and we get foo.coff generated, but
at least it has contents.
Not knowing anything about coff files, I can't tell
whether the coff support is unfinished or just broken.
I can come up with a patch to allow it to be turned on,
but I don't want to do that if the avra code isn't ready
to generate proper coff files anyway.
Logged In: YES
user_id=1044596
I can confirm this behavior and was wondering about this
0-byte .cof file generated every time, too.
As of cf495f37d49c95ef085586e34fb9cab2f5d5fadd version in git AVRA no longer generates an empty COFF file.