Øyvind Harboe wrote: >> *) The xscale target does something similar with its debug binary, which >> tells me it's acceptable if not preferable. >> > > I vote for keeping it simple & robust. The procedure should be > described and committed > to SVN, but it can be done manually for files which are updated once in a > blue 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! :-) > > > Agreed.
In effect, what you are describing is "maintainer-mode" in other packages. With a slight twist, in "dist-mode" - the openocd "bootstrap" process has been done. For V1.0 - we must run "bootstrap" - and commit with those configured files W.r.t these rlink files - our situation is a bit more complicated, not everyone has every sub-target tool chain to build every sub target binary stub of some sort (ie: the elf files, and various other helper files) so perhaps some items are "super-maintainer-mode". -Duane. _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
