Summary: | [Flatpak SDK] Path references shouldn't point to the sandbox in compile_commands.json | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Sergio Villar Senin <svillar> | ||||||
Component: | Tools / Tests | Assignee: | Philippe Normand <pnormand> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | pnormand, webkit-bug-importer, zan | ||||||
Priority: | P2 | Keywords: | InRadar | ||||||
Version: | WebKit Nightly Build | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Attachments: |
|
Description
Sergio Villar Senin
2020-04-02 06:02:52 PDT
BTW for those using VSCode there is a workaround. Just need to use path mappings setting, for example: "ccls.clang.pathMappings": [ "/app/webkit>PATH_TO_YOUR_WEBKIT_CHECKOUT_ROOT" ], Note the ">" in between paths, it's superimportant :) Is there something to fix then? Or this is "only" a matter of documentation :) What's your use-case for this? Are you building WebKit from VSCode? (In reply to Philippe Normand from comment #3) > What's your use-case for this? Are you building WebKit from VSCode? The use case is having semantic autocompletion when using LSP tools with different editors: VSCode, emacs..., is not about building. So you use LSP in Emacs for WebKit dev? Can you share your config? :D Created attachment 398360 [details]
Emacs config
Not my default editor anymore, but here you are the relevant bits. Note that the path mapping setting is not used anymore as I'm using jhbuild again because I could not make it work with flatpak builds.
Perhaps the SDK could ship ccls and have it running in the sandbox. This needs investigation but is down below in my TODO. Created attachment 398863 [details]
Patch
(In reply to Philippe Normand from comment #3) > What's your use-case for this? Are you building WebKit from VSCode? FWIW I now have compilation errors reported in Emacs thanks to LSP/CCLS. Committed r261681: <https://trac.webkit.org/changeset/261681> All reviewed patches have been landed. Closing bug and clearing flags on attachment 398863 [details]. |