From owner-freebsd-arch Mon Jan 22 19:51:42 2001 Delivered-To: freebsd-arch@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id C283737B699 for ; Mon, 22 Jan 2001 19:51:23 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id B70EA6AB70; Tue, 23 Jan 2001 14:21:21 +1030 (CST) Date: Tue, 23 Jan 2001 14:21:21 +1030 From: Greg Lehey To: arch@FreeBSD.org Subject: TAGS target in sys/Makefile? Message-ID: <20010123142121.L414@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are a number of tools people can use to find their way around the kernel sources: I know of at least ctags, etags and cscope. It would be nice to have build targets for the corresponding data files in sys/Makefile. I'd suggest adding targets 'tags' for ctags, 'TAGS' for etags, and 'cscope.out' (which just creates the cscope.out file) and 'cscope' (which also runs the program) for cscope. Does anybody have any objections? If not, there are a few odds and ends to tie up, like duplicate labels and machine architectures. I'd omit stuff like the boot code, which doesn't really relate to the kernel, but I don't have a really good idea how to tackle that; possibly ignore the machine-dependent stuff unless an environment variable is set. I'm very much open to suggestions here. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message