I'm aware of that. Plus, the author of `Bear` is the same author of
`scan-build`. I've had a discussion with him about the duplicity of
those two tools which seem to be doing the same thing. I just think that
such a tool should be an official part of `make`.
I've sent an mail to the Make mailing
This is a tool that generates a compilation database from a make file:
https://github.com/rizsotto/Bear
i
On Sat, Jul 28, 2018 at 2:27 PM Doron Behar wrote:
> On Tue, Jul 24, 2018 at 10:47:20PM +0300, Basin Ilya wrote:
> > Hi Doron.
> >
> > The list of source files and resulting object files
https://gist.github.com/basinilya/9320b806efacece314c2ad16524993c1
сб, 28 июл. 2018 г., 15:27 Doron Behar :
> On Tue, Jul 24, 2018 at 10:47:20PM +0300, Basin Ilya wrote:
> > Hi Doron.
> >
> > The list of source files and resulting object files isn't known until
> `make` is launched. The IDE
On Tue, Jul 24, 2018 at 10:47:20PM +0300, Basin Ilya wrote:
> Hi Doron.
>
> The list of source files and resulting object files isn't known until `make`
> is launched. The IDE should be ready to support a constantly updating
> compilation database.
>
> It is possible to create a wrapper
>> The list of source files and resulting object files isn't known until
>> `make` is launched.
It seems to me that Automake knows more about the build than a generic
system would, and could implement this. Well, at least it could in most
cases, for example those where all the sources are
Hi Doron.
The list of source files and resulting object files isn't known until `make` is
launched. The IDE should be ready to support a constantly updating compilation
database.
It is possible to create a wrapper program for GNU Make that will do the job.
It won't be part of Make, you will
Many build systems, IDEs and text editors plugins, integrate with source
code files using a compilation database. It is `compile_commands.json`
and it is placed in a project's root directory.
It is best explained here:
https://clang.llvm.org/docs/JSONCompilationDatabase.html
As listed here:
