| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also update the Java Tutorial page to say you have
to install the JDK and set JAVA_HOME.
See https://github.com/bazelbuild/bazel/issues/5208
Change-Id: I14b792589c39f03572518aaff6f6f8e5ca8a65c8
Closes #5617.
Change-Id: I45c841189b0c220365ab9aeeb67f26b32059be4a
PiperOrigin-RevId: 206156529
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/5272
Change-Id: Ia49c084f1fe036ff0e5b18fea096f31642cf8b5b
Closes #5280.
Change-Id: Ia49c084f1fe036ff0e5b18fea096f31642cf8b5b
PiperOrigin-RevId: 200005785
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The MarkDown engine we use for the Bazel website
renders the following MarkDown block:
foo:
```sh
bar
```
to HTML as:
foo: <code>sh bar</code>
when in fact it should render it as:
foo: <code class="sh">bar</code>
This resulted in a bad command that the users
couldn't run as it was on the website.
Change-Id: If127ca83375b4d1f8c6403fdec16bbd79498cb5d
Closes #5288.
Change-Id: If127ca83375b4d1f8c6403fdec16bbd79498cb5d
PiperOrigin-RevId: 198380352
|
|
|
|
|
|
|
|
|
| |
Change-Id: Id881cc4381fcd355a3b4a65d9089072e4818aa16
Closes #5159.
Change-Id: If14c9a2e55192f5ee5ab384fad27275a24ec12b1
PiperOrigin-RevId: 196472499
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Simplify the installation and bootstrapping
instruction for Windows.
Fixes https://github.com/bazelbuild/bazel/issues/4784
Change-Id: I564cd6136ac5b2f0661665765b9bb488e23fe6b0
Closes #5152.
Change-Id: I564cd6136ac5b2f0661665765b9bb488e23fe6b0
PiperOrigin-RevId: 195382164
|
|
|
|
|
|
|
|
| |
Updating macOS install instructions together with David.
Closes #5025.
PiperOrigin-RevId: 193374002
|
|
|
|
|
|
|
|
|
|
| |
Update the documentation about:
- compiling Bazel from source (without an existing Bazel binary) on Windows
- OS and software requirements on Windows
Closes #4741.
PiperOrigin-RevId: 187829532
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 178406494
|
|
|
|
|
|
|
|
| |
Explicitly emphasize that the distribution archive is architecture independent. In
particular, users do not have to look for their architecture. This has led to confusions.
Change-Id: If7c75fcde4ec85d5670eb2c893ffcb4be65e3c0c
PiperOrigin-RevId: 177835486
|
|
|
|
|
|
|
|
|
| |
Remove info about older versions' bootstrapping
bugs, because we want people to use the latest
version.
Change-Id: I0639824b9557077062e380996cfc9d2b974778e2
PiperOrigin-RevId: 172297572
|
|
|
|
| |
PiperOrigin-RevId: 170057335
|
|
|
|
|
|
|
|
|
|
| |
While it is not a clear decission what is a dependency
and which programs are expected to be always there (various
systems have differing opinions on this), err on the side
of mentioning more. In any case zip was missing (for any
system). Fixes #3578.
PiperOrigin-RevId: 166489619
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In this change:
- Reword text in windows.md to use active voice
instead of passive voice (so it's clear who the
actor is).
- Update Bash script examples to use cmd.exe
syntax.
- Remove outdated information, such as Bazel being
an msys2 binary.
- Restructure list of requirements to be clearer
and simpler.
RELNOTES: none
PiperOrigin-RevId: 166476459
|
|
|
|
|
|
|
|
|
| |
Since https://github.com/bazelbuild/bazel/commit/4c55898e71d30b32090bef31b43e408d942a24f6 bazel requires python to run create_embedded_tools. This cl
adds it to the affected Dockerfiles. Not to the debian one, since debian has
'python' binary there by default. While add it, sort the packages logically.
RELNOTES: None.
PiperOrigin-RevId: 164574914
|
|
|
|
|
|
|
|
| |
* move Compile requirement and instructions to the "compile from source" page
* remove warning for old versions of Bazel
RELNOTES: None
PiperOrigin-RevId: 160641070
|
|
The new docs/ directory in the bazel source tree will only contain the Bazel
docs site, which is hosted at docs.bazel.build. This change deletes the
marketing site and blog, which have been migrated to the bazel-website and
bazel-blog GitHub repositories respectively.
This change also updates the serve-docs.sh and ci/build.sh under scripts/ in
preparation for publishing the docs site.
Note that to help make reviews more manageable, this change is limited to
moving files to their new locations. Here are the follow-up changes:
* Update all links in docs to remove versions/master in paths and to add
correct bazel.build subdomain when linking to pages on the marketing site
or the blog.
* Set up versioned directories on GCS bucket and add tooling for versioning
docs
This change is also coordinated with
https://bazel-review.googlesource.com/c/11568/ to have the PublishSite job
publish to docs.bazel.build rather than www.bazel.build.
Issue #2397
RELNOTES: None
PiperOrigin-RevId: 157612651
|