Commit 1003c0bc authored by xiaoyin.l's avatar xiaoyin.l Committed by Commit bot

Use HTTPS links for Google domains in docs

Since almost all Google domains support HTTPS, and it is a good practice to
use HTTPS wherever possible, thus in this patch, I changed most HTTP links
to https whose domains are known to support HTTPS well.

Modifications are generated by running these commands in src/docs directory:
sed -i 's/http:\/\/www.chromium.org/https:\/\/www.chromium.org/g' *.md
sed -i 's/http:\/\/developer.android.com/https:\/\/developer.android.com/g' *.md
sed -i 's/http:\/\/dev.chromium.org/https:\/\/dev.chromium.org/g' *.md
sed -i 's/http:\/\/build.chromium.org/https:\/\/build.chromium.org/g' *.md
sed -i 's/http:\/\/src.chromium.org/https:\/\/src.chromium.org/g' *.md
sed -i 's/http:\/\/crbug.com/https:\/\/crbug.com/g' *.md
sed -i 's/http:\/\/groups.google.com/https:\/\/groups.google.com/g' *.md
sed -i 's/http:\/\/cs.chromium.org/https:\/\/cs.chromium.org/g' *.md
sed -i 's/http:\/\/codereview.chromium.org/https:\/\/codereview.chromium.org/g' *.md

BUG=

Review-Url: https://codereview.chromium.org/2545363002
Cr-Commit-Position: refs/heads/master@{#436501}
parent 1bd1f12d
......@@ -223,7 +223,7 @@ The app will appear on the device as "Chromium".
### Build Content shell
Wraps the content module (but not the /chrome embedder). See
[http://www.chromium.org/developers/content-module](http://www.chromium.org/developers/content-module)
[https://www.chromium.org/developers/content-module](https://www.chromium.org/developers/content-module)
for details on the content module and content shell.
```shell
......@@ -244,9 +244,9 @@ export CHROMIUM_OUT_DIR=out_android
### Build WebView shell
[Android WebView](http://developer.android.com/reference/android/webkit/WebView.html)
[Android WebView](https://developer.android.com/reference/android/webkit/WebView.html)
is a system framework component. Since Android KitKat, it is implemented using
Chromium code (based off the [content module](http://dev.chromium.org/developers/content-module)).
Chromium code (based off the [content module](https://dev.chromium.org/developers/content-module)).
It is possible to test modifications to WebView using a simple test shell. The
WebView shell is a view with a URL bar at the top (see [code](https://code.google.com/p/chromium/codesearch#chromium/src/android_webview/test/shell/src/org/chromium/android_webview/test/AwTestContainerView.java))
and is **independent** of the WebView **implementation in the Android system** (
......@@ -258,7 +258,7 @@ ninja -C out/Release android_webview_apk
build/android/adb_install_apk.py out/Release/apks/AndroidWebView.apk
```
If, instead, you want to build the complete Android WebView framework component and test the effect of your chromium changes in other Android app using the WebView, you should follow the [Android AOSP + chromium WebView instructions](http://www.chromium.org/developers/how-tos/build-instructions-android-webview)
If, instead, you want to build the complete Android WebView framework component and test the effect of your chromium changes in other Android app using the WebView, you should follow the [Android AOSP + chromium WebView instructions](https://www.chromium.org/developers/how-tos/build-instructions-android-webview)
### Running
......@@ -286,7 +286,7 @@ build/android/adb_run_android_webview_shell http://example.com
Logging is often the easiest way to understand code flow. In C++ you can print
log statements using the LOG macro or printf(). In Java, you can print log
statements using [android.util.Log](http://developer.android.com/reference/android/util/Log.html):
statements using [android.util.Log](https://developer.android.com/reference/android/util/Log.html):
`Log.d("sometag", "Reticulating splines progress = " + progress);`
......
......@@ -6,7 +6,7 @@
## Overview
Logging used to be done using Android's [android.util.Log]
(http://developer.android.com/reference/android/util/Log.html).
(https://developer.android.com/reference/android/util/Log.html).
A wrapper on that is now available: org.chromium.base.Log. It is designed to
write logs as belonging to logical groups going beyond single classes, and to
......@@ -205,7 +205,7 @@ for all tags. Please use `grep` or a similar tool to refine your filters
further.
For more, see the [related page on developer.android.com]
(http://developer.android.com/tools/debugging/debugging-log.html#filteringOutput)
(https://developer.android.com/tools/debugging/debugging-log.html#filteringOutput)
## Logs in JUnit tests
......
......@@ -141,7 +141,7 @@ Note that tests are sharded across all attached devices unless explicitly told
to do otherwise by `-d/--device`.
The commands used by the buildbots are printed in the logs. Look at
http://build.chromium.org/ to duplicate the same test command as a particular
https://build.chromium.org/ to duplicate the same test command as a particular
builder.
### INSTALL\_FAILED\_CONTAINER\_ERROR or INSTALL\_FAILED\_INSUFFICIENT\_STORAGE
......@@ -304,6 +304,6 @@ See [Layout Tests](testing/layout_tests.md).
(e.g. the "Android Debug (Nexus 7)" bot on the chromium.gpu waterfall)
See http://www.chromium.org/developers/testing/gpu-testing for details. Use
See https://www.chromium.org/developers/testing/gpu-testing for details. Use
`--browser=android-content-shell`. Examine the stdio from the test invocation on
the bots to see arguments to pass to `src/content/test/gpu/run_gpu_test.py`.
......@@ -76,7 +76,7 @@ dynamic bottom view) in two different and distinct ways.
For the cases where there is a dynamic view at the bottom of the browser view, a
new view class (named `BrowserResizerView`) inheriting from
[views::View](http://src.chromium.org/svn/trunk/src/chrome/views/view.h) is used
[views::View](https://src.chromium.org/svn/trunk/src/chrome/views/view.h) is used
to display the resize widget. It is set as a child of the dynamic view laid at
the bottom of the browser view. The Browser view takes care of properly setting
the bounds of the resize widget view, based on the language direction.
......@@ -111,7 +111,7 @@ resize widget area.
## Implementation
You can find the changes made to make this work in patch
[16488](http://codereview.chromium.org/16488).
[16488](https://codereview.chromium.org/16488).
## Alternatives Considered
......
......@@ -47,4 +47,4 @@ builds **on Linux**.
http://googlechromereleases.blogspot.com/, http://omahaproxy.appspot.com/
and http://gsdview.appspot.com/chromium-browser-official/
* Google API keys depend on the distribution
* See http://www.chromium.org/developers/how-tos/api-keys
* See https://www.chromium.org/developers/how-tos/api-keys
......@@ -21,7 +21,7 @@ display log messages to the `LogCat` pane.
### Eclipse
1. Go to http://developer.android.com/sdk/index.html and click "Download the
1. Go to https://developer.android.com/sdk/index.html and click "Download the
SDK ADT Bundle for Linux"
1. Configure eclipse
1. Select General > Workspace from the tree on the left.
......
......@@ -36,12 +36,12 @@ false`.
## Mailing List
http://groups.google.com/a/chromium.org/group/clang/topics
https://groups.google.com/a/chromium.org/group/clang/topics
## Using plugins
The
[chromium style plugin](http://dev.chromium.org/developers/coding-style/chromium-style-checker-errors)
[chromium style plugin](https://dev.chromium.org/developers/coding-style/chromium-style-checker-errors)
is used by default when clang is used.
If you're working on the plugin, you can build it locally like so:
......@@ -68,7 +68,7 @@ SDK, so you still need to have Visual Studio installed.
Things should compile, and all tests should pass. You can check these bots for
how things are currently looking:
http://build.chromium.org/p/chromium.fyi/console?category=win%20clang
https://build.chromium.org/p/chromium.fyi/console?category=win%20clang
```shell
python tools\clang\scripts\update.py
......
......@@ -3,7 +3,7 @@
## Easiest usage, from the command line
To automatically format a pending patch according to
[Chromium style](http://www.chromium.org/developers/coding-style), from
[Chromium style](https://www.chromium.org/developers/coding-style), from
the command line, simply run: ``` git cl format ``` This should work on all
platforms _(yes, even Windows)_ without any set up or configuration: the tool
comes with your checkout. Like other `git-cl` commands, this operates on a diff
......@@ -33,7 +33,7 @@ work.
For further guidance on editor integration, see these specific pages:
* [Sublime Text](http://www.chromium.org/developers/sublime-text#TOC-Format-selection-or-area-around-cursor-using-clang-format)
* [Sublime Text](https://www.chromium.org/developers/sublime-text#TOC-Format-selection-or-area-around-cursor-using-clang-format)
* [llvm's guidelines for vim, emacs, and bbedit](http://clang.llvm.org/docs/ClangFormat.html)
* For vim, `:so tools/vim/clang-format.vim` and then hit cmd-shift-i (mac)
ctrl-shift-i (elsewhere) to indent the current line or current selection.
......
......@@ -116,7 +116,7 @@ With these contents:
You can locally test that your code compiles on Linux or Mac. This requires
[Java](http://www.oracle.com/technetwork/java/javase/downloads/index.html) and a
[Chrome checkout](http://www.chromium.org/developers/how-tos/get-the-code) (i.e.
[Chrome checkout](https://www.chromium.org/developers/how-tos/get-the-code) (i.e.
python, depot_tools). Note: on Ubuntu, you can probably just run `sudo apt-get
install openjdk-7-jre`.
......@@ -194,5 +194,5 @@ in `src/third_party/closure_compiler/compiled_resources2.gyp`:
```
This file is used by the
[Closure compiler bot](http://build.chromium.org/p/chromium.fyi/builders/Closure%20Compilation%20Linux)
[Closure compiler bot](https://build.chromium.org/p/chromium.fyi/builders/Closure%20Compilation%20Linux)
to automatically compile your code on every commit.
......@@ -9,7 +9,7 @@ If you're new to Chromium development, read the
[getting started guides](https://www.chromium.org/developers/how-tos/get-the-code).
There is some additional documentation on
[setting GYP build parameters](http://dev.chromium.org/developers/gyp-environment-variables).
[setting GYP build parameters](https://dev.chromium.org/developers/gyp-environment-variables).
[TOC]
......@@ -21,7 +21,7 @@ A non-standard build configuration is to use dynamic linking instead of static
linking for the various modules in the Chromium codebase. This results in
significantly faster link times, but is a divergence from what is shipped and
primarily tested. To enable the
[component build](http://www.chromium.org/developers/how-tos/component-build):
[component build](https://www.chromium.org/developers/how-tos/component-build):
$ GYP_DEFINES="component=shared_library" gclient runhooks
......
......@@ -241,7 +241,7 @@ Date: Mon Jul 19 19:09:41 2010 +0000
BUG=38992
Review URL: http://codereview.chromium.org/3036004
Review URL: https://codereview.chromium.org/3036004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@52935 0039d316-1c4b-4281-b951-d872f2087c98
```
......@@ -268,7 +268,7 @@ from that one then adjust it to point it at the real upstream one.
1. Clone a nearby copy of the code you want: `git clone coworker-machine:/path/to/repo`
1. Change the URL your copy fetches from to point at the real git repo:
`git set-url origin http://src.chromium.org/git/chromium.git`
`git set-url origin https://src.chromium.org/git/chromium.git`
1. Update your copy: `git fetch`
1. Delete any extra branches that you picked up in the initial clone:
`git prune origin`
......@@ -23,9 +23,9 @@
* Native feel layout
* Font size changes (e.g., changing the system font size will apply to our
dialogs)
* Better RTL (e.g., http://crbug.com/2822 http://crbug.com/5729
http://crbug.com/6082 http://crbug.com/6103 http://crbug.com/6125
http://crbug.com/8686 http://crbug.com/8649)
* Better RTL (e.g., https://crbug.com/2822 https://crbug.com/5729
https://crbug.com/6082 https://crbug.com/6103 https://crbug.com/6125
https://crbug.com/8686 https://crbug.com/8649)
* Being able to obey the user's system theme
* Accessibility for buttons and dialogs (but not for tabstrip and bookmarks)
* A better change at good remote X performance?
......
......@@ -142,7 +142,7 @@ hooks as needed.
If you have problems building, join us in `#chromium` on `irc.freenode.net` and
ask there. As mentioned above, be sure that the
[waterfall](http://build.chromium.org/buildbot/waterfall/) is green and the tree
[waterfall](https://build.chromium.org/buildbot/waterfall/) is green and the tree
is open before checking out. This will increase your chances of success.
### Improving performance of `git status`
......
......@@ -46,8 +46,8 @@ Chromium's testing infrastructure for ARM/Linux is somewhat limited.
There are currently two builders setup, one on the FYI waterfall and one
the the try bot waterfall:
* [Linux ARM](http://build.chromium.org/p/chromium.fyi/builders/Linux%20ARM)
* [linux_arm](http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_arm)
* [Linux ARM](https://build.chromium.org/p/chromium.fyi/builders/Linux%20ARM)
* [linux_arm](https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_arm)
These bots run x86-64 linux and cross-compile the ARM targets. Tests are
run on ARM hardware via swarming.
......
......@@ -80,7 +80,7 @@ which is rather annoying.
You can also use `--renderer-startup-dialog` and attach to the process in order
to debug the renderer code. Go to
http://www.chromium.org/blink/getting-started-with-blink-debugging for more
https://www.chromium.org/blink/getting-started-with-blink-debugging for more
information on how this can be done.
#### Choosing which renderers to debug
......@@ -196,7 +196,7 @@ just run gdb on the main process.
Currently, the `--disable-gpu` flag is also required, as there are known crashes
that occur under TextureImageTransportSurface without it. The crash described in
http://crbug.com/361689 can also sometimes occur, but that crash can be
https://crbug.com/361689 can also sometimes occur, but that crash can be
continued from without harm.
Note that for technical reasons plugins cannot be in-process, so
......@@ -394,7 +394,7 @@ Default log level hides `LOG(INFO)`. Run with `--log-level=0` and
`--enable-logging=stderr` flags.
Newer versions of Chromium with VLOG may need --v=1 too. For more VLOG tips, see
[the chromium-dev thread](http://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/dcd0cd7752b35de6?pli=1).
[the chromium-dev thread](https://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/dcd0cd7752b35de6?pli=1).
### Seeing IPC debug messages
......@@ -485,7 +485,7 @@ this, run via `Xephyr`. Instructions for how to use `Xephyr` are on the
### Isolating Regressions
Old builds are archived here:
http://build.chromium.org/buildbot/snapshots/chromium-rel-linux/
https://build.chromium.org/buildbot/snapshots/chromium-rel-linux/
(TODO: does not exist).
`tools/bisect-builds.py` in the tree automates bisecting through the archived
......
......@@ -33,7 +33,7 @@ issues. If you can't find a related bug, please create a
## Contributing code
See [Contributing code](http://dev.chromium.org/developers/contributing-code).
See [Contributing code](https://dev.chromium.org/developers/contributing-code).
## Debugging
......
......@@ -103,6 +103,6 @@ Then use gdb as normal.
## Other resources
For more discussion on this process see
[Debugging a Minidump](http://www.chromium.org/chromium-os/how-tos-and-troubleshooting/crash-reporting/debugging-a-minidump).
[Debugging a Minidump](https://www.chromium.org/chromium-os/how-tos-and-troubleshooting/crash-reporting/debugging-a-minidump).
This page discusses the same process in the context of ChromeOS and many of the
concepts and techniques overlap.
......@@ -14,7 +14,7 @@
### Chromium-specific
* [Chromium's plugin architecture](http://dev.chromium.org/developers/design-documents/plugin-architecture)
* [Chromium's plugin architecture](https://dev.chromium.org/developers/design-documents/plugin-architecture)
-- may be out of date but will be worth reading
## Code to reference
......
......@@ -164,7 +164,7 @@ http://google-perftools.googlecode.com/svn/trunk/doc/heapprofile.html.
### Massif
[Massif](http://valgrind.org/docs/manual/mc-manual.html) is a
[Valgrind](http://www.chromium.org/developers/how-tos/using-valgrind)-based heap
[Valgrind](https://www.chromium.org/developers/how-tos/using-valgrind)-based heap
profiler. It is much slower than the heap profiler from google-perftools, but it
may have some advantages. (In particular, it handles the multi-process
executables well).
......@@ -173,7 +173,7 @@ First, you will need to build massif from valgrind-variant project yourself,
it's [easy](http://code.google.com/p/valgrind-variant/wiki/HowTo).
Then, make sure your Chromium is built using the
[valgrind instructions](http://www.chromium.org/developers/how-tos/using-valgrind).
[valgrind instructions](https://www.chromium.org/developers/how-tos/using-valgrind).
Now, you can run massif like this:
```
......
......@@ -6,7 +6,7 @@ renderers to run with a limited set of privileges since they process untrusted
input and are likely to be compromised. Renderers will use an IPC mechanism to
request access to resource from a more privileged (browser process).
You can find more about this general design
[here](http://dev.chromium.org/developers/design-documents/sandbox).
[here](https://dev.chromium.org/developers/design-documents/sandbox).
We use different sandboxing techniques on Linux and Chrome OS, in combination,
to achieve a good level of sandboxing. You can see which sandboxes are currently
......@@ -41,9 +41,9 @@ network, something that is difficult to perform at the layer-2.
| **Name** | **Layer and process** | **Linux flavors where available** | **State** |
|:---------|:----------------------|:----------------------------------|:----------|
| [Setuid sandbox](#The_setuid_sandbox.md) | Layer-1 in Zygote processes (renderers, PPAPI, [NaCl](http://www.chromium.org/nativeclient), some utility processes) | Linux distributions and Chrome OS | Enabled by default (old kernels) and maintained |
| [User namespaces sandbox](#User_namespaces_sandbox.md) | Modern alternative to the setuid sandbox. Layer-1 in Zygote processes (renderers, PPAPI, [NaCl](http://www.chromium.org/nativeclient), some utility processes) | Linux distributions and Chrome OS (kernel >= 3.8) | Enabled by default (modern kernels) and actively developed |
| [Seccomp-BPF](#The_seccomp-bpf_sandbox.md) | Layer-2 in some Zygote processes (renderers, PPAPI, [NaCl](http://www.chromium.org/nativeclient)), Layer-1 + Layer-2 in GPU process | Linux kernel >= 3.5, Chrome OS and Ubuntu | Enabled by default and actively developed |
| [Setuid sandbox](#The_setuid_sandbox.md) | Layer-1 in Zygote processes (renderers, PPAPI, [NaCl](https://www.chromium.org/nativeclient), some utility processes) | Linux distributions and Chrome OS | Enabled by default (old kernels) and maintained |
| [User namespaces sandbox](#User_namespaces_sandbox.md) | Modern alternative to the setuid sandbox. Layer-1 in Zygote processes (renderers, PPAPI, [NaCl](https://www.chromium.org/nativeclient), some utility processes) | Linux distributions and Chrome OS (kernel >= 3.8) | Enabled by default (modern kernels) and actively developed |
| [Seccomp-BPF](#The_seccomp-bpf_sandbox.md) | Layer-2 in some Zygote processes (renderers, PPAPI, [NaCl](https://www.chromium.org/nativeclient)), Layer-1 + Layer-2 in GPU process | Linux kernel >= 3.5, Chrome OS and Ubuntu | Enabled by default and actively developed |
| [Seccomp-legacy](#The_seccomp_sandbox.md) | Layer-2 in renderers | All | [Deprecated](https://src.chromium.org/viewvc/chrome?revision=197301&view=revision) |
| [SELinux](#SELinux.md) | Layer-1 in Zygote processes (renderers, PPAPI) | SELinux distributions | [Deprecated](https://src.chromium.org/viewvc/chrome?revision=200838&view=revision) |
| AppArmor | Outer layer-1 in Zygote processes (renderers, PPAPI) | Not used | Deprecated |
......@@ -131,7 +131,7 @@ renderers and PPAPI processes) will do a dynamic transition. audit2allow will
quickly build a usable module.
Available since
[r26257](http://src.chromium.org/viewvc/chrome?view=rev&revision=26257),
[r26257](https://src.chromium.org/viewvc/chrome?view=rev&revision=26257),
more information in
[this blog post](http://www.imperialviolet.org/2009/07/14/selinux.html) (grep
for 'dynamic' since dynamic transitions are a little obscure in SELinux)
......@@ -141,7 +141,7 @@ for 'dynamic' since dynamic transitions are a little obscure in SELinux)
Sandboxing can make developing harder, see:
* [this page](linux_suid_sandbox_development.md) for the `setuid` sandbox
* [this page](http://www.chromium.org/for-testers/bug-reporting-guidelines/hanging-tabs)
* [this page](https://www.chromium.org/for-testers/bug-reporting-guidelines/hanging-tabs)
for triggering crashes
* [this page for debugging tricks](linux_debugging.md)
......
......@@ -131,4 +131,4 @@ Chromium binary somewhere else you need to modify this string.
* [LinuxSUIDSandboxDevelopment](linux_suid_sandbox_development.md)
* [LinuxSandboxing](linux_sandboxing.md)
* General information on Chromium sandboxing:
http://dev.chromium.org/developers/design-documents/sandbox
https://dev.chromium.org/developers/design-documents/sandbox
......@@ -170,10 +170,10 @@ You can find out more about GoogleTest at its
## Debugging
Good debugging tips can be found
[here](http://dev.chromium.org/developers/how-tos/debugging-on-os-x). If you
[here](https://dev.chromium.org/developers/how-tos/debugging-on-os-x). If you
would like to debug in a graphical environment, rather than using `lldb` at the
command line, that is possible without building in Xcode (see
[Debugging in Xcode](http://www.chromium.org/developers/how-tos/debugging-on-os-x/building-with-ninja-debugging-with-xcode)).
[Debugging in Xcode](https://www.chromium.org/developers/how-tos/debugging-on-os-x/building-with-ninja-debugging-with-xcode)).
## Update your checkout
......@@ -226,7 +226,7 @@ gets interpreted as a URL to open.
If you have problems building, join us in `#chromium` on `irc.freenode.net` and
ask there. Be sure that the
[waterfall](http://build.chromium.org/buildbot/waterfall/) is green and the
[waterfall](https://build.chromium.org/buildbot/waterfall/) is green and the
tree is open before checking out. This will increase your chances of success.
### Improving performance of `git status`
......
......@@ -122,4 +122,4 @@ The following areas have insufficient memory instrumentation.
1. DisplayLists - DisplayLists can be quite large and are currently
un-instrumented. These use malloc memory and currently contribute to
malloc/allocated_objects/<unspecified>. [BUG](http://crbug.com/567465)
malloc/allocated_objects/<unspecified>. [BUG](https://crbug.com/567465)
......@@ -38,7 +38,7 @@ build using the API keys you just generated.
1. [Install the build dependencies](linux_build_instructions_prerequisites.md).
1. Install the depot\_tools utilities, a process that is documented at
http://dev.chromium.org/developers/how-tos/install-depot-tools.
https://dev.chromium.org/developers/how-tos/install-depot-tools.
1. Download the Chromium source code by running:
`$ fetch chromium --nosvn=True`
......
......@@ -118,7 +118,7 @@ through creating a new ozone platform called `foo`.
## Building with Ozone
### ChromeOS - ([waterfall](http://build.chromium.org/p/chromium.chromiumos/waterfall?builder=Linux+ChromiumOS+Ozone+Builder&builder=Linux+ChromiumOS+Ozone+Tests+%281%29&builder=Linux+ChromiumOS+Ozone+Tests+%282%29&reload=none))
### ChromeOS - ([waterfall](https://build.chromium.org/p/chromium.chromiumos/waterfall?builder=Linux+ChromiumOS+Ozone+Builder&builder=Linux+ChromiumOS+Ozone+Tests+%281%29&builder=Linux+ChromiumOS+Ozone+Tests+%282%29&reload=none))
To build `chrome`, do this from the `src` directory:
......@@ -160,7 +160,7 @@ Then to run for example the headless platform:
```
### Linux Desktop - ([waterfall](https://build.chromium.org/p/chromium.fyi/builders/Ozone%20Linux/))
Support for Linux Desktop is currently [in-progress](http://crbug.com/295089).
Support for Linux Desktop is currently [in-progress](https://crbug.com/295089).
The following targets are currently working:
......@@ -234,7 +234,7 @@ content_shell --ozone-platform=headless \
This is Linux direct rending with acceleration via mesa GBM & linux DRM/KMS
(EGL/GLES2 accelerated rendering & modesetting in GPU process) and is in
production use on [ChromeOS](http://www.chromium.org/chromium-os).
production use on [ChromeOS](https://www.chromium.org/chromium-os).
Note that all ChromeOS builds of Chrome will compile and attempt to use this.
See [Building Chromium for Chromium OS](https://www.chromium.org/chromium-os/how-tos-and-troubleshooting/building-chromium-browser) for build instructions.
......
......@@ -46,7 +46,7 @@ architecture should look like now that the spec is relatively stable.
## Deliverables
1. Project code name: Piranha Plant.
1. A [design document](http://www.chromium.org/developers/design-documents/idealized-mediastream-design)
1. A [design document](https://www.chromium.org/developers/design-documents/idealized-mediastream-design)
for the idealized future design (work in progress).
1. A document laying out a plan for incremental steps to achieve as much of the
idealized design as is pragmatic. See below for current draft.
......
......@@ -94,7 +94,7 @@ You can run any Telemetry benchmark with `--profiler=perf`, and it will:
4. Setup symlinks to work with the `--symfs` parameter
You can also run "manual" tests with Telemetry, more information here:
http://www.chromium.org/developers/telemetry/profiling#TOC-Manual-Profiling---Android
https://www.chromium.org/developers/telemetry/profiling#TOC-Manual-Profiling---Android
The following steps describe building `perf`, which is no longer necessary if
you use Telemetry.
......
......@@ -4,7 +4,7 @@ Several times a day the Chromium code base is built with Microsoft VC++'s
`/analyze` compile option. This does static code analysis which has found
numerous bugs (see https://crbug.com/427616). While it is possible to visit the
`/analyze` builder page and look at the raw results
(http://build.chromium.org/p/chromium.fyi/builders/Chromium%20Windows%20Analyze)
(https://build.chromium.org/p/chromium.fyi/builders/Chromium%20Windows%20Analyze)
this works very poorly.
As of this writing there are 2,702 unique warnings. Some of these are in header
......
......@@ -57,7 +57,7 @@ This is a list of current and planned Chrome OS security features. Each feature
## Chrome OS specific features
* We use `minijail` for sandboxing:
* [Design doc](http://www.chromium.org/chromium-os/chromiumos-design-docs/system-hardening#Detailed_Design_73859539098644_6227793370126997)
* [Design doc](https://www.chromium.org/chromium-os/chromiumos-design-docs/system-hardening#Detailed_Design_73859539098644_6227793370126997)
* Issue 380 (on Google Code)
* Current sandboxing status:
......
......@@ -306,7 +306,7 @@ with the following exceptions.
constructs that target old browsers.
* Per the JavaScript guide, new tests should also follow any per-project
style guide, such as the
[ServiceWorker Tests Style guide](http://www.chromium.org/blink/serviceworker/testing).
[ServiceWorker Tests Style guide](https://www.chromium.org/blink/serviceworker/testing).
## JavaScript Tests
......
......@@ -43,7 +43,7 @@ to enforce chromium specific Java rules. It currently detects:
[FindBugs](http://findbugs.sourceforge.net) is configured to run on:
* [android_clang_dbg_recipe](http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_dbg_recipe)
* [android_clang_dbg_recipe](https://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_dbg_recipe)
on the commit queue
* [Android Clang Builder (dbg)](http://build.chromium.org/p/chromium.linux/builders/Android%20Clang%20Builder%20\(dbg\))
* [Android Clang Builder (dbg)](https://build.chromium.org/p/chromium.linux/builders/Android%20Clang%20Builder%20\(dbg\))
on the main waterfall
......@@ -5,22 +5,22 @@ This page aims to be a repository of useful links that people may find useful.
## Build Status
* [Main buildbot waterfall](http://build.chromium.org/p/chromium/console)
* [Main buildbot waterfall](https://build.chromium.org/p/chromium/console)
* [Last Known Good Revision](http://chromium-status.appspot.com/lkgr) : Try bots pull this revision from trunk
* [List of the last 100 potential LKGRs](http://chromium-status.appspot.com/revisions)
* [Status dashboard for LKGR](http://build.chromium.org/p/chromium/lkgr-status/)
* http://build.chromium.org/p/tryserver.chromium/waterfall?committer=developer@chromium.org : Try bot runs, by developer
* [Status dashboard for LKGR](https://build.chromium.org/p/chromium/lkgr-status/)
* https://build.chromium.org/p/tryserver.chromium/waterfall?committer=developer@chromium.org : Try bot runs, by developer
* [Tree uptime stats](http://chromium-status.appspot.com/status_viewer)
* [Commit queue status](http://chromium-cq-status.appspot.com)
* [Pending commit queue jobs](http://codereview.chromium.org/search?closed=3&commit=2&limit=50)
* [Pending commit queue jobs](https://codereview.chromium.org/search?closed=3&commit=2&limit=50)
* [Search for historical test failures by test name](http://chromium-build-logs.appspot.com/)
* [Filterable list of most recent build logs](http://chromium-build-logs.appspot.com/list)
## For Sheriffs
* http://build.chromium.org/p/chromium.chromiumos/waterfall?show_events=true&reload=120&failures_only=true : List of failing bots for a waterfall(chromium.chromiumos as an example)
* http://build.chromium.org/p/chromium.linux/waterfall?show_events=true&reload=120&builder=Linux%20Builder%20x64&builder=Linux%20Builder%20(dbg) : Monitor one or multiple bots(Linux Builder x64 and Linux Builder (dbg) on chromium.linux as an example)
* http://build.chromium.org/p/chromium.win/waterfall/help : Customize the waterfall view for a waterfall(using chromium.win as an example)
* https://build.chromium.org/p/chromium.chromiumos/waterfall?show_events=true&reload=120&failures_only=true : List of failing bots for a waterfall(chromium.chromiumos as an example)
* https://build.chromium.org/p/chromium.linux/waterfall?show_events=true&reload=120&builder=Linux%20Builder%20x64&builder=Linux%20Builder%20(dbg) : Monitor one or multiple bots(Linux Builder x64 and Linux Builder (dbg) on chromium.linux as an example)
* https://build.chromium.org/p/chromium.win/waterfall/help : Customize the waterfall view for a waterfall(using chromium.win as an example)
* [Alternate waterfall view that helps with test failure triage](http://chromium-sheriffing.appspot.com)
* [Lists historical test results for the bots](http://test-results.appspot.com/dashboards/flakiness_dashboard.html)
......@@ -31,14 +31,14 @@ This page aims to be a repository of useful links that people may find useful.
## Source Information
* [Code Search](http://cs.chromium.org/)
* http://cs.chromium.org/SEARCH_TERM : Code Search for a specific SEARCH\_TERM
* [Code Search](https://cs.chromium.org/)
* https://cs.chromium.org/SEARCH_TERM : Code Search for a specific SEARCH\_TERM
* [Gitiles Source Code Browser](https://chromium.googlesource.com/chromium/src/)
* https://chromium.googlesource.com/chromium/src/+log/b6cfa6a..9a2e0a8?pretty=fuller : Git changes in revision range(also works for build numbers)
* http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog.html?url=/trunk/src&mode=html&range=SUCCESS_REV:FAILURE_REV : SVN changes in revision range
* http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=/trunk&mode=html&range=SUCCESS_REV:FAILURE_REV : Blink changes in revision range
* https://build.chromium.org/f/chromium/perf/dashboard/ui/changelog.html?url=/trunk/src&mode=html&range=SUCCESS_REV:FAILURE_REV : SVN changes in revision range
* https://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=/trunk&mode=html&range=SUCCESS_REV:FAILURE_REV : Blink changes in revision range
## Communication
* [Chromium Developers List](http://groups.google.com/a/chromium.org/group/chromium-dev/topics)
* [Chromium Users List](http://groups.google.com/a/chromium.org/group/chromium-discuss/topics)
* [Chromium Developers List](https://groups.google.com/a/chromium.org/group/chromium-dev/topics)
* [Chromium Users List](https://groups.google.com/a/chromium.org/group/chromium-discuss/topics)
......@@ -17,6 +17,6 @@ App Restrictions.
Please see the [Policy List on chromium.org][2] for more information and the
list of supported policies.
[3]: http://developer.android.com/training/enterprise/work-policy-ctrl.html#apply_restrictions
[1]: http://developer.android.com/training/enterprise/app-restrictions.html
[3]: https://developer.android.com/training/enterprise/work-policy-ctrl.html#apply_restrictions
[1]: https://developer.android.com/training/enterprise/app-restrictions.html
[2]: https://www.chromium.org/administrators/policy-list-3
......@@ -147,7 +147,7 @@ $ gn gen out/Default
If you want to use the Visual Studio IDE, use the `--ide` command line
argument to `gn gen` when you generate your output directory (as described on
the [get the code](http://dev.chromium.org/developers/how-tos/get-the-code)
the [get the code](https://dev.chromium.org/developers/how-tos/get-the-code)
page):
```shell
......
......@@ -46,13 +46,13 @@ import/export, however it cannot work for data export.
There are relatively few instances where data exports are required across the
DLL boundary. The waterfall builder
http://build.chromium.org/p/chromium/waterfall?show=Win%20Split will detect when
https://build.chromium.org/p/chromium/waterfall?show=Win%20Split will detect when
new data exports are added, and these will need to be repaired. For constants,
the data can be duplicated to both DLLs, but for writeable data, a wrapping
set/get function will need to be added.
http://build.chromium.org/p/chromium/waterfall?show=Win%20Split does not exist.
https://build.chromium.org/p/chromium/waterfall?show=Win%20Split does not exist.
Some more details can be found on the initial commit of the split_link script
http://src.chromium.org/viewvc/chrome?revision=200049&view=revision and the
associated bugs: http://crbug.com/237249 http://crbug.com/237267.
https://src.chromium.org/viewvc/chrome?revision=200049&view=revision and the
associated bugs: https://crbug.com/237249 https://crbug.com/237267.
......@@ -17,7 +17,7 @@ Valid reasons for writing a plugin are for example:
* You want to write an automatic code rewriter.
In both cases, please inform
[clang@chromium.org](http://groups.google.com/a/chromium.org/group/clang/topics)
[clang@chromium.org](https://groups.google.com/a/chromium.org/group/clang/topics)
of your plans before you pursue them.
# Having said that
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment