[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250526114424.GE31726@noisy.programming.kicks-ass.net>
Date: Mon, 26 May 2025 13:44:24 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: mingo@...hat.com, juri.lelli@...hat.com, vincent.guittot@...aro.org,
dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
mgorman@...e.de, vschneid@...hat.com, rafael@...nel.org,
viresh.kumar@...aro.org, mathieu.desnoyers@...icios.com,
paulmck@...nel.org, hannes@...xchg.org, surenb@...gle.com
Cc: linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org, tj@...nel.org,
masahiroy@...nel.org
Subject: Re: [PATCH] sched: Make clangd usable
On Mon, May 26, 2025 at 10:59:43AM +0200, Peter Zijlstra wrote:
> I've not been annoyed enough to (or out of diskspace enough) to go stare
> at fixing the Makefiles to make all this easier. But ideally it would be
> possible to do a no-op build to just generate the .cmd files without
> doing any actual compiling -- building allmodconfig is slow, doubly so
> with allmodconfig.
>
> Or maybe this is already possible and I just didn't find the magic
> incantations.
So I had a quick peek at the Makefiles, and while there is a
compile_commands.json target (just not readily accessible without doing
other weird things), it still causes everything to be built :-(
Powered by blists - more mailing lists