Files
carbon-lang/utils/vscode
Chandler CarruthandJon Ross-Perkins 13502b7c89 Replace #4505 with a different set of workarounds (#4527)
This restores the symlinks for the installation, but teaches the busybox
info search to look for a relative path to the busybox binary itself
before walking through symlinks. This let's it find the tree structure
when directly invoking `prefix_root/bin/carbon` or similar, either
inside of a Bazel rule or from the command line, and mirrors how we
expect the installed tree to look. This works even when Bazel resolves
the symlink target fully, and potentially to something nonsensical like
a CAS file.

In order to make a convenient Bazel target that can be used with `bazel
run //toolchain`, this adds an override to explicitly set the desired
argv[0] to use when selecting a mode for the busybox and a busybox
binary. Currently, the workaround uses an environment variable because
that required the least amount of plumbing, and seems a useful override
mechanism generally, but I'm open to other approaches.

This should allow a few things to work a bit more nicely:
- It should handle sibling symlinks like `clang++` to `clang` or
  `ld.lld` to `lld`, where that symlink in turn points at the busybox.
  We want to use *initial* `argv[0]` value to select the mode there.
- It avoids bouncing through Python (or other subprocesses) when
  invoking the `carbon` binary in Bazel rules, which will be nice for
  building the example code and benchmarking.

It does come at a cost of removing one feature: the initial symlink
can't be some unrelated alias like `my_carbon_symlink` -- we expect the
*first* argv[0] name to have the meaningful filename for selecting
a busybox mode.

It also trades the complexity of the Python script for some complexity
in the busybox search in order to look for a relative `carbon-busybox`
binary. On the whole, I think that tradeoff is worthwhile, but it isn't
free.

---------

Co-authored-by: Jon Ross-Perkins <jperkins@google.com>
2024-12-20 00:33:29 +00:00
..

Carbon Language

This extension provides support for the Carbon Language.

This extension is currently experimental, and being developed alongside Carbon.

Quickstart

  1. Download and install a carbon release.
    • By default, the extension will look for carbon under ./bazel-bin. This is for developers actively working on Carbon and running VS Code inside a carbon-lang clone.
  2. Install the Carbon Language extension.
  3. Configure the installed path to carbon.

Configuration

The configuration is under carbon-vscode.*. At present, the only configuration is the path to the carbon binary. This looks like:

"carbon.carbonPath": "/path/to/carbon"

Communication

See Carbon's collaboration systems. We're most active on Discord and have a #editor-integrations channel. We'll also respond to questions on GitHub Discussions.

Documentation

Carbon currently only has project-level documentation. See the GitHub repository.