mirror of https://github.com/carbon-language/carbon-lang.git synced 2026-09-24 22:02:23 +01:00

Files

T

Jon Ross-PerkinsandChandler Carruth 9af06cc988 Adjust some build troubleshooting notes (#4471 )

Came up due to [libc++ install
issues](https://discord.com/channels/655572317891461132/655577725347561492/1302023663155023905)

We've discussed clang version verification, and adding that as long as
I'm in here. The more significant bit is the libc++ check, which if it's
not installed should fail like:

```
(tons of output)
ignoring nonexistent directory "/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/lib/llvm-16/lib/clang/16/include
 /usr/local/include
 /usr/include/x86_64-linux-gnu
 /usr/include
End of search list.
/usr/local/google/home/jperkins/.cache/bazel/_bazel_jperkins/85deb7d9d96f7e0e80b42618a55969d7/external/_main~clang_toolchain_extension~bazel_cc_toolchain/_temp:6:2: error: "No libc++ install found!"
#error "No libc++ install found!"
 ^
1 error generated.
ERROR: Analysis of target '//toolchain:toolchain' failed; build aborted: Analysis failed
INFO: Elapsed time: 0.265s, Critical Path: 0.08s
INFO: 1 process: 1 internal.
ERROR: Build did NOT complete successfully
```

pre-commit runs bazel, and GitHub runners have an old clang by default
(caught by the new check), so I'm installing here for a consistent
version.

---------

Co-authored-by: Chandler Carruth <chandlerc@gmail.com>

2024-11-04 16:03:09 +00:00

design

Document that extend base must appear early in a class definition (#4401 )

2024-10-11 19:51:15 +00:00

guides

Fix minor grammatical error in docs (#3537 )

2023-12-21 22:05:47 +00:00

images

Build a website. (#4189 )

2024-08-20 17:53:06 +00:00

project

Adjust some build troubleshooting notes (#4471 )

2024-11-04 16:03:09 +00:00

spec

Initial rough framework for specification. (#140 )

2022-03-16 15:43:09 -07:00

README.md

Fix grammar errors (#1648 )

2022-07-24 12:37:00 -07:00

README.md

Docs

This directory contains current, accepted documentation underpinning Carbon. These documents cover all aspects of Carbon ranging from the project down to detailed designs for specific language features.

If you're trying to learn more about Carbon, we recommend starting at /README.md.

Design

Carbon language's design and rationale are documented in the design/ directory. This documentation is intended to support the following audiences:

People who wish to determine whether Carbon would be the right choice for a project compared to other existing languages.
People working on the evolution of the Carbon language who wish to understand the rationale and motivation for existing design decisions.
People working on a specification or implementation of the Carbon language who need a detailed understanding of the intended design.
People writing Carbon code who wish to understand why the language rules are the way they are.

This is in contrast to proposals, which document the individual decisions that led to this design (along with other changes to the Carbon project), including the rationale and alternatives considered.

Project

The project/ directory contains project-related documentation for Carbon, including:

goals, and the principles and roadmap derived from those goals,
how the project works, and
how to contribute.

Guides

The guides/ directory contains to-be-written end-user documentation for developers writing programs in Carbon.

Spec

The spec/ directory contains the to-be-written formal specification of the Carbon language. This is for implementers of compilers or other tooling. This is intended to complement the interactive language explorer tool.