summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorBill Richardson <wfrichar@chromium.org>2013-10-30 22:49:38 -0700
committerchrome-internal-fetch <chrome-internal-fetch@google.com>2013-10-31 18:43:46 +0000
commit9fd4258f365c6c74114c34dbe56e85819a585208 (patch)
tree57a4c364492696d0a2cbf4d65c97c68e3171d161 /include
parent2dc1418ccdad1b06f686cddc717e02bcb80ff648 (diff)
downloadchrome-ec-9fd4258f365c6c74114c34dbe56e85819a585208.tar.gz
Replace Makefile 'tags' target with 'xrefs', clean it up
This adds a 'xrefs' target to create various cross-reference files from the EC sources. In particular, it generates these files in the target build directory: cscope.files - for the cscope browsing tool TAGS - for emacs tags - for vi It parses the dependency files generated by a build, so that only those source files actually used to create the EC binary are scanned. BUG=chrome-os-partner:18343 BRANCH=none TEST=manual Inside the chroot: make BOARD=link xrefs ls -l build/link/cscope.files If you install the ctags and etags programs in the chroot, you should also see build/$BOARD/tags or build/$BOARD/TAGS, respectively. If those programs don't exist, those steps will be silently skipped. Note: You can install ctags with "sudo emerge ctags". AFAICT, installing etags requires the entire emacs suite, so it's probably simpler to just copy the etags binary from your build host into the chroot's /opt/bin/ If you don't have ctags or etags in the chroot, you can still run make BOARD=link CROSS_COMPILE= xrefs outside the chroot, provided you've built the EC image first. Change-Id: I8e16ef19b0f4e79aba887c308e58982fef8fa21f Signed-off-by: Bill Richardson <wfrichar@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/175224
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions