On Dec 17, 2008, at 3:01 AM, Øyvind Harboe wrote:
*) The xscale target does something similar with its debug binary, whichtells me it's acceptable if not preferable.I vote for keeping it simple & robust. The procedure should be described and committedto SVN, but it can be done manually for files which are updated once in ablue moon. I'd suggest committing these files to SVN, but keeping them out of the way for the ordinary citizen. A separate folder is nice. Works well for e.g. xscale.We've got lots of other examples, e.g. the at91fr40162 flash driver contains a .elf file that is compiled with an arm-elf toolchain using eCos source.We're *NOT* going to make that part normal OpenOCD builds! :-) -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer
If these are truly infrequent operations, then perhaps moving the generation tool to trunk/tools/{toolname} is probably a better location. The generated files would still live in the interface folder, but the tool doesn't need to be there and isn't really part of the source.
As for whether rlink should be a folder under interface or just in interface, the general rule is if it is simply a single .c and .h, it lives in the interfaces folder. Anything more and it should be in a subfolder. That makes it clear which files belong to which interfaces. If the build system isn't setup to handle this today, I'm certain someone with more automake-fu can help make this happen.
-- Rick Altherr [email protected]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
