Hello,
Is there a way to get the XDC build process to build .s or .asm files? When I include one in the add objects list, it claims that there is no rule to make it. I'm just looking to include the ethernet boot done code.
Thanks
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello,
Is there a way to get the XDC build process to build .s or .asm files? When I include one in the add objects list, it claims that there is no rule to make it. I'm just looking to include the ethernet boot done code.
Thanks
The XDC build engine looks for more specific suffix extensions so it knows which ISA assembler to use. For example, if you working with a C64+ architecture device, use the .s64P suffix on your assembly code source file instead of just .s or .asm.
Mark
Most of XDCtools targets recognize .asm as an extension for assembly files. If you have "hello.asm" and "hello.c" in your package, and you add "hello" to the object list, "hello.asm" gets used. Can you post your package.bld? What's your target?
When I went to change the extension of the file in the package.bld, I also noticed I had misspelled the file name. Once I corrected it it appears to work with .asm as well.