From: "kjtsanaktsidis (KJ Tsanaktsidis)" <noreply@ruby-lang.org>
To: ruby-core@neon.ruby-lang.org
Subject: [ruby-core:110679] [Ruby master Feature#19011] Improve LSP support in CRuby development itself
Date: Thu, 10 Nov 2022 09:42:32 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-100022.20221110094232.73@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-19011.20220919162648.73@ruby-lang.org
Issue #19011 has been updated by kjtsanaktsidis (KJ Tsanaktsidis).
I've been using Bear https://github.com/rizsotto/Bear for this - running `bear -- make` generates a _passable_ compile_commands.json file that sort-of works. It doesn't handle some of the trickier things though, e.g. files like vm_insnhelper.c which are not themselves compiled as a translation unit, but rather `#include`'d in vm.c. So having some better built-in support for this in the cruby development toolchain would be ace.
----------------------------------------
Feature #19011: Improve LSP support in CRuby development itself
https://bugs.ruby-lang.org/issues/19011#change-100022
* Author: tenderlovemaking (Aaron Patterson)
* Status: Open
* Priority: Normal
----------------------------------------
I would like to add a new configure option for improve working with language servers inside CRuby itself.
The summary is like this:
```
$ ./autogen.sh
$ ./configure --enable-compile-commands
$ make -j compile_commands.json
# Now use LSP
```
`clangd` uses `compile_commands.json` to understand how to compile files inside CRuby. We can use `clang` itself to generate this file, but we have to pass special compile options to clang. Unfortunately the compile options generate many small JSON files, so we also need a way to concatenate them in to `compile_commands.json`.
Ideally I would like `make miniruby` to build `miniruby` *and* `compile_commands.json`, but I don't know how to do that yet. 😅
I've send a patch [here](https://github.com/ruby/ruby/pull/6352)
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2022-11-10 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 16:26 [ruby-core:109957] [Ruby master Feature#19011] Improve LSP support in CRuby development itself tenderlovemaking (Aaron Patterson)
2022-11-10 9:42 ` kjtsanaktsidis (KJ Tsanaktsidis) [this message]
2022-11-10 11:35 ` [ruby-core:110680] " eightbitraptor (Matthew Valentine-House)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-100022.20221110094232.73@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=ruby-core@neon.ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).