From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Philippe Blain via GitGitGadget <gitgitgadget@gmail.com>,
Git mailing list <git@vger.kernel.org>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Jeff King <peff@peff.net>
Subject: Re: [PATCH v2] Makefile: add support for generating JSON compilation database
Date: Thu, 3 Sep 2020 18:04:04 -0400 [thread overview]
Message-ID: <98711D92-AE89-46B4-A749-89F85A9A87A7@gmail.com> (raw)
In-Reply-To: <xmqqpn728s3f.fsf@gitster.c.googlers.com>
> Le 3 sept. 2020 à 17:31, Junio C Hamano <gitster@pobox.com> a écrit :
>
> Philippe Blain <levraiphilippeblain@gmail.com> writes:
>
>> This addition to the .gitignore is for the individual JSON files (one per source file),
>> that are placed in the $(compdb_dir).
>> I think naming "rebase.o.json" the JSON file that describes how to compile "rebase.c"
>> into "rebase.o" makes sense. I don't know what is the convention for other projects.
>
> I agree rebase.o.$somesuffix does make sense, but I do not know
> 'json' is a great value for $somesuffix. I wouldn't be surprised if
> 'cdb' or some other silly abbreviation for "compilation database" is
> how other people use this feature.
>
> Those watching from the sidelines. Does anybody know if there is an
> established convention used by other projects? If we hear nothing
> by early next week, let's declare 'json' is good enough and move on.
>
>> The name `compile_commands.json` for the database itself is standard.
>> The name of the directory where the '*.o.json' files are placed is a name
>> I chose, and I don't feel strongly about it. I thought it made sense to name
>> it like that, then its purpose is clear. We could make it a hidden directory
>> if we don't want to add a new folder to the root of the repo when using this feature.
>
> I think both of these are sensible. Again if we hear nothing about
> common practice, let's move on with these constants as-is.
OK.
>
>>>> +ifdef GENERATE_COMPILATION_DATABASE
>>>> +compdb_check = $(shell $(CC) $(ALL_CFLAGS) \
>>>> + -c -MJ /dev/null \
>>>> + -x c /dev/null -o /dev/null 2>&1; \
>>>> + echo $$?)
>>>> +ifeq ($(compdb_check),0)
>>>> +override GENERATE_COMPILATION_DATABASE = yes
>>>
>>> This feels strange. If the end user said to GENERATE and we find we
>>> are capable, we still override to 'yes'? What if the end user set
>>> 'no' to the GENERATE_COMPILATION_DATABASE macro? Shouldn't we be
>>> honoring that wish?
>>
>> We should. I'll tweak (and simplify) that for v3.
>
> I think
>
> - GENERATE_COMPILATION_DATABASE is set to 'no': don't even probe
>
> - GENERATE_COMPILATION_DATABASE is set to 'yes': probe and turn it
> to 'no' if unavailable.
>
> - GENERATE_COMPILATION_DATABASE is set to anything else: either
> error out, or turn it into 'no' (I have no preference between
> them).
>
> would cover all the cases.
I agree. I'll do that.
>
>>>> +compdb_file = $(compdb_dir)$(subst .-,,$(subst /,-,$(dir $@)))$(notdir $@).json
>>>
>>> This detail does not matter as long as the end result ensures unique
>>> output for all source files, but I am having trouble guessing what
>>> the outermost subst, which removes ".-" sequence, is trying to make
>>> prettier. Care to explain?
>>
>> Yes, it is because the `$(dir $@)` Makefile function will return `./` for source files
>> at the base of the repo, so the JSON files get named eg. `.-rebase.o.json` and then they are
>> hidden. So it's just to make them non-hidden, so as not to confuse someone that would
>> count the number of source files and compare with the number of (non-hidden)
>> '*.o.json' files in $(comdb_dir) and get a different number.
>
> Hmph. Would $(subst /,-,$@) instead of "only substitute leading
> directory part, and concatenate the basename part unmolested" work
> better then? After all, by definition the basename part would not
> have a slash in it, so substituting all '/' to '-' in the whole
> pathname should do the same thing and we won't have to worry about
> the spurious './', no?
This indeed works, and reads better. Thanks!
next prev parent reply other threads:[~2020-09-03 22:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 19:28 [PATCH] Makefile: add support for generating JSON compilation database Philippe Blain via GitGitGadget
2020-08-30 22:10 ` brian m. carlson
2020-08-31 2:37 ` Philippe Blain
2020-08-31 4:24 ` Junio C Hamano
2020-09-01 7:38 ` Jeff King
2020-09-01 13:18 ` Philippe Blain
2020-09-02 1:33 ` brian m. carlson
2020-09-02 8:04 ` Jeff King
2020-08-30 22:17 ` Philippe Blain
2020-09-01 23:09 ` [PATCH v2] " Philippe Blain via GitGitGadget
2020-09-02 17:21 ` Junio C Hamano
2020-09-03 21:17 ` Philippe Blain
2020-09-03 21:31 ` Junio C Hamano
2020-09-03 22:04 ` Philippe Blain [this message]
2020-09-03 22:13 ` [PATCH v3] " Philippe Blain via GitGitGadget
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=98711D92-AE89-46B4-A749-89F85A9A87A7@gmail.com \
--to=levraiphilippeblain@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).