From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 53C026DE0164 for ; Thu, 24 Aug 2017 02:13:28 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.013 X-Spam-Level: X-Spam-Status: No, score=-0.013 tagged_above=-999 required=5 tests=[AWL=0.107, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y972ntnVYmY4 for ; Thu, 24 Aug 2017 02:13:27 -0700 (PDT) Received: from mail-wm0-f66.google.com (mail-wm0-f66.google.com [74.125.82.66]) by arlo.cworth.org (Postfix) with ESMTPS id 26E476DE00E6 for ; Thu, 24 Aug 2017 02:13:27 -0700 (PDT) Received: by mail-wm0-f66.google.com with SMTP id b79so2105777wmf.0 for ; Thu, 24 Aug 2017 02:13:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:in-reply-to:references:date:message-id:mime-version; bh=yq0ZT34M+LU3Cl9zCIME0r3ClDGVUwbKNFrAdRS9/jE=; b=bi+04TqEckuRVXbtJF4aV/pskH9dBwMGUcZS//qmtuaWGjuuP26oaRwo/C26BEZpdg DexLnpEJ8PHx0DbjC2W+WE9koJ/wVdtzGoB6VG5/IO11yiLXp0GCjXAlW56tIMCYwBv3 3C2Ssgr3Qmxyoyv4ouLrxBIA4V6SRs7aBnhmhDO05pAYeNlEQJpkTkQ4P4bnTAgI8gEq TgTPQIKv6e9tsHK3Q+4dx3ZRI/VUz7EfUBOiwd9Q5GhwxxHQb0KO8Z88mqp3vF3oMYWb ZZ3hw5XOIH3WGronVSPKkxPYwRB7hx5aBarS1tcPHPtD4u/H7U+BU6epgDlQjnW+bO7M KUbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:references:date :message-id:mime-version; bh=yq0ZT34M+LU3Cl9zCIME0r3ClDGVUwbKNFrAdRS9/jE=; b=jHsrVCXKBYsAa/0FlfZLah7iTCSRHrCFodaHPAuuZTz5PiwUhauW/XOl425GQ6j43E BVl8D/akN/pT6X3mgwPIV0PJ+CiTFXepH0FVZjkyf5/2bjmNQ3njH/fg3W3N7b27bkJS 08yAlnvZFeGuUpYq8ulk/2BysNfEznKUZjoordh3ax3hZCC4uez5fZoOphaFjnowgb4x /dmb18gvkGqaPkXQrWVj0+AnZPHIP3DxVqexK8RSVYfLEOU9ms6YcKWsfv30UMzxvbOS nf0vwecQ5dugB9N+H4iMrQbXGNrFZPUtY87xgm7aGkdgN7u/XKo24oYftrZOooRrVFlk Ewrw== X-Gm-Message-State: AHYfb5iswP1Debd9N2rQSRENTR336z1g1S7uNSZINqMOa5qKo/YGQnsJ jgh2qTYyeUXYKA== X-Received: by 10.28.145.2 with SMTP id t2mr3079392wmd.179.1503566005437; Thu, 24 Aug 2017 02:13:25 -0700 (PDT) Received: from localhost (mito.neclab.eu. [195.37.70.39]) by smtp.gmail.com with ESMTPSA id n67sm4256002wmi.43.2017.08.24.02.13.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Aug 2017 02:13:24 -0700 (PDT) From: Yuri Volchkov To: Tomi Ollila , Jani Nikula , notmuch@notmuchmail.org Subject: Re: [PATCH] build: generate cscope and etags source indexes In-Reply-To: References: <1503521740-32330-1-git-send-email-yuri.volchkov@gmail.com> <87d17lqzr5.fsf@nikula.org> Date: Thu, 24 Aug 2017 11:13:08 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Aug 2017 09:13:28 -0000 to Jani: >> What's the point in adding these to configure? Or, to be honest, to the >> build at all? Ok, modifying configure was probably unnecessary. >> I guess I'm also biased because I use gnu global [1] instead. And for >> that I have a script of my own that basically boils down to: >> >> $ git ls-files | gtags -f - I was trying to adapt developing patterns from the linux kernel, to which I used to. This was my bias :) The good thing about this approach is that only those files will be indexed, which are actually build in the current configuration. For linux it is absolutely must, because there is a huge number of functions, implemented differently for different architecture or configuration option. So only relevant files are getting into the index. However, I agree, a relatively small project as notmuch, almost does not suffer from this problem. >> In theory you'll be able to look at $(SRCS) for indexing... but those >> are only the .c/.cc files. Are your tools clever enough to follow >> #include directives to index the headers as well? Oops. Honestly this thing have slipped from my mind. I'll fix this if we decided this feature is needed, and if the result will not look too ugly. to Tomi: > I agree with Jani about configure and build steps, but could tolerate > convenience goals like `cscope` and `tags` (and something `global` !) > which would build corresponding files for developers to utilize (provided > those are accurate enough, we don't want to lessen general quality (from > what it is now) of the system due to too bad quality tags files > (content-wise)... Sorry, I did not get what is accurate enough, what is lessen quality and what is too bad? Could you please explain a little more detailed? Also I have never tried gnu global. I need to check it out too. And again, if decided this helper is needed, I'll add gnu global too.