[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190620205406.GY137143@google.com>
Date: Thu, 20 Jun 2019 13:54:06 -0700
From: Matthias Kaehlcke <mka@...omium.org>
To: Nick Desaulniers <ndesaulniers@...gle.com>
Cc: Tom Roeder <tmroeder@...gle.com>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
LKML <linux-kernel@...r.kernel.org>,
Raul E Rangel <rrangel@...omium.org>,
Tom Hughes <tomhughes@...omium.org>,
Douglas Anderson <dianders@...omium.org>,
Ryan Case <ryandcase@...omium.org>,
Yu Liu <yudiliu@...gle.com>,
Doug Anderson <dianders@...gle.com>
Subject: Re: [PATCH] gen_compile_command: Add support for separate
KBUILD_OUTPUT directory
On Thu, Jun 20, 2019 at 12:53:22PM -0700, Nick Desaulniers wrote:
> On Thu, Jun 20, 2019 at 11:45 AM Matthias Kaehlcke <mka@...omium.org> wrote:
> >
> > gen_compile_command.py currently assumes that the .cmd files and the
> > source code live in the same directory, which is not the case when
> > a separate KBUILD_OUTPUT directory is used.
>
> Great point; android builds the kernel outside of the source dir
> (`make O=/non-source/path ...`). Thanks for the patch! BTW if CrOS is
> doing cool stuff with compile_commands.json; I'd like to know!
> Particularly; I'm curious if it's possible to generate Ninja build
> files from compile_commands.json; I do miss Doug's Kbuild caching
> patches' speedup.
> Acked-by: Nick Desaulniers <ndesaulniers@...gle.com>
At this point Chrome OS doesn't do anything with compile_commands.json
for the kernel. I was just toying around a bit after a presentation
from Tom Hughes about IDE integration and encountered this limitation.
Powered by blists - more mailing lists