Cscope.gmk revision 3261
1472N/A# Copyright (c) 1998, 2010, Oracle and/or its affiliates. All rights reserved. 342N/A# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. 342N/A# This code is free software; you can redistribute it and/or modify it 342N/A# under the terms of the GNU General Public License version 2 only, as 342N/A# published by the Free Software Foundation. Oracle designates this 342N/A# particular file as subject to the "Classpath" exception as provided 342N/A# by Oracle in the LICENSE file that accompanied this code. 342N/A# This code is distributed in the hope that it will be useful, but WITHOUT 342N/A# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or 342N/A# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License 342N/A# version 2 for more details (a copy is included in the LICENSE file that 342N/A# accompanied this code). 342N/A# You should have received a copy of the GNU General Public License version 342N/A# 2 along with this work; if not, write to the Free Software Foundation, 1472N/A# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. 1472N/A# Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA 342N/A# The cscope.out file is made in the current directory and spans the entire 350N/A# 1. We use relative names for cscope. # enough to only build what has changed. It can be confused, however, # if files are renamed or removed, so it may be necessary to manually # remove cscope.out if a lot of reorganization has occurred. # Set CSFLAGS env variable to -b when using fast cscope to build the fast # (but large) cscope data bases. # Adding .java files pushes the file count of a full workspace up about 2500 # files, which slows database lookup. Thus allow these files to be added from # the environment (CSCLASSES=yes). # Adding CClassHeaders also pushes the file count of a full workspace up about # 200 files (these files also don't exist in a new workspace, and thus will # cause the recreation of the database as they get created, which might seem # A little confusing). Thus allow these files to be added from the environment # What files should we include? A simple rule might be just those files under # SCM control, however this would miss files we create like the opcodes and # CClassHeaders. The following attempts to find everything that is *useful*. # (demo directories contain many .java files # that probably aren't useful for development, and the pkgarchive may contain # duplicates of files within the source hierarchy). The ordering of the .raw # file is an attempt to make cscope display the most relevant files first. -
type f \( -
name '*.[Ccshlxy]' -o -
name '*.il' -o -
name '*.cc' -o \