or just use #ccls instead of #clangd :D

I spend a bit of time trying to get various Clang tooling options to generate a JSON compilation database for a project. All the tooling around this seems really complicated and though Bear works well on Linux, it doesn't do much on macOS.

So I wrote a simple tool to swizzle the Clang "-MJ" option and collate the JSON fragments that emits. Super simple, and seems to work really well - I was actually able to get clangd working and resolving most symbols.

#clang #clangd

https://github.com/jpeach/mj

Is it just me, or is there no way to use clangd with the Linux Kernel without doing an entire build to generate compile_commands.json? I don't have hours to wait for a build every time I switch git branches, which I do very often. Just opening random files with vim-lsp and clangd setup for C files doesn't work well. #clangd #ccls #lsp #llvm #kernel

Turns out if you setup vim-lsp with ccls and open a directory with C it... just magically works! No compilation database necessary. Having used this for a couple of days on userspace projects and libraries like SDL2, I can see why people really like this. #Vim #Neovim #LSP #ccls #clangd #CProgramming

I finally got #corfu working with #lsp in #emacs when I realised that the compile_commands database used by #clangd hadn't been updated in ages. I'll have to figure out what to fix for the build when I'm back at work.

I have switched from nixpkgs#clang_13 to nixpgks#clang-tools_13 and everything is fixed.

Reading the derivation source, it looks like the clangd from clang-tools is patched to look for libc & co. where it should.

I'm not entirely sure why we need a separate derivation for clang tools then, but I don't know if/where I should report that issue.

#nixos #nixpkgs #nix #clang #clangd

I have switched from nixpkgs#clang_13 to nixpgks#clang-tools_13 and everything is fixed.

Reading the derivation source, it looks like the clangd from clang-tools is patched to look for libc & co. where it should.

I'm not entirely sure why we need a separate derivation for clang tools then, but I don't know if/where I should report that issue.

#nixos #nixpkgs #nix #clang #clangd

#clangd + #VScode is a way better #Cpp setup than what I expected.
It actually works better than on #neovim (navigating a call hierarchy doesn't crash the server)

I am really battling to get #rust to compile on my #linux box. I think largely because I am using #VSCodium and not #VSCode. Any tips? #clangd

It's alive!

Now my #KissLinux have a barebone graphical session (#sway) and a web browser installed (#qutebrowser).

For now I used #flatpak to provide some binary packages but I'm still thinking if I like it.

That was not as problematic as I anticipated.

But I'm pondering about removing #gcc, as #llvm is dependency of some packages and I use #clangd in my code editor, and compiling both toolchains takes time…

Anyone knows where to find an aarch64 binary of #clangd ? AFAIK it's not available through the #manjaroarm repos or AUR (aarch64) for the #pinebookpro ... Currently building from source but overkill in my opinion #askthefediverse

@merazi@hostux.social did some really quick testing and #clangd bugged out almost immediately 🙄

Using #ccls for now. No issues so far.

Switching from #cedet+#semantic to #lsp. Looking good so far!

But should I use #ccls or #clangd?

#emacs