public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Peng Yu <pengyu.ut@gmail.com>
To: Konstantin Kharlamov <hi-angel@yandex.ru>
Cc: libc-help <libc-help@sourceware.org>
Subject: Re: How to look up where a structure is defined?
Date: Wed, 3 Mar 2021 13:51:02 -0600	[thread overview]
Message-ID: <CABrM6wk7tanXGPQRaL_T1BoL0_ThLESF1uNzhCcGBETba_2Bgg@mail.gmail.com> (raw)
In-Reply-To: <9f1dbafc6d1184d9ca07bdea98f696e0ca65b9e2.camel@yandex.ru>

This seems to be a complicated solution. I just want to get a database
(a TSV file should be fine) of types and the header they appear. I
don't want to build the project just to get this info.

It seems that this database could be made and hosted online for easy
download or lookup.

On Wed, Mar 3, 2021 at 8:55 AM Konstantin Kharlamov <hi-angel@yandex.ru> wrote:
>
> On Wed, 2021-03-03 at 17:26 +0300, Konstantin Kharlamov wrote:
> > there's `bear` utility, which takes a make command as input, and parses it
> > output while it builds the project, and stores the output into
> > `compile_commands.json` file. So for example: if you usually build glibc with
> > `make`, then to generate the file you have to use a `bear -- make` instead.
>
> To clarify: if you already built the project you'll need somehow to re-build it
> with bear. So, for example, you can call a `find -type f -exec touch {} \;` in
> the source tree to cause timestamps of all files to get bumped, and then running
> a make command will trigger a full rebuild.

-- 
Regards,
Peng

  reply	other threads:[~2021-03-03 19:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03 14:12 Peng Yu
2021-03-03 14:26 ` Konstantin Kharlamov
2021-03-03 14:55   ` Konstantin Kharlamov
2021-03-03 19:51     ` Peng Yu [this message]
2021-03-03 20:09       ` Konstantin Kharlamov
2021-03-03 20:23         ` Konstantin Kharlamov
2021-03-03 22:24           ` Peng Yu
2021-03-03 22:45             ` Konstantin Kharlamov
2021-03-03 22:46               ` Peng Yu
2021-03-03 22:57                 ` Konstantin Kharlamov
     [not found]                   ` <CABrM6wkdp_WB5_XT9-TyzjwqPTAz5eNX=NiWL2XhfXEUsm976Q@mail.gmail.com>
     [not found]                     ` <947e1677c982b59d21fc4507f5cf6b284b3c8355.camel@yandex.ru>
2021-03-03 23:21                       ` Peng Yu

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABrM6wk7tanXGPQRaL_T1BoL0_ThLESF1uNzhCcGBETba_2Bgg@mail.gmail.com \
    --to=pengyu.ut@gmail.com \
    --cc=hi-angel@yandex.ru \
    --cc=libc-help@sourceware.org \
    /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.
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).