[clangd-dev] Multi-project workflow via multiple CDBs

Ilya Biryukov via clangd-dev clangd-dev at lists.llvm.org
Tue Mar 12 23:49:30 PDT 2019

Ah, sorry for missing the context. Makes sense and for multi-configuration
use-case we might need some extra stuff too, e.g. in addition
to loading the index for the new configuration I'd expect clangd to unload
the index for the old configuration, etc.

On Tue, Mar 12, 2019 at 7:36 PM Nathan Ridge <zeratul976 at hotmail.com> wrote:

> > Unless there are issues that would prevent auto-discovery from working,
> > I think we should prefer it instead.
> > One strong reason is that auto-discovery would work regardless of the
> > client support.
> Of course, auto-discovery should be the default. This is about providing
> another option.
> My understanding is that the motivation for another option, is building in
> multiple configurations. If you have multiple configurations, the CDBs need
> to go somewhere other than the source folder, as there is only one source
> folder.
> > +1 to Doug's suggestion, if we there's a client that has a legitimate
> need
> > to send all CDBs upfront, let's extend LSP
> > to allow this instead of assigning our own semantics to the existing
> methods.
> Agreed, that sounds reasonable to me.
> Thanks,
> Nate

Ilya Biryukov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/clangd-dev/attachments/20190313/8e31e713/attachment.html>

More information about the clangd-dev mailing list