Skip to content

Commit 45c4057

Browse files
author
Mihail Stoyanov
authored
Merge pull request #800 from bridadan/fix_readme_links
Updating links in README
2 parents 10be76e + a33adbe commit 45c4057

File tree

1 file changed

+21
-21
lines changed

1 file changed

+21
-21
lines changed

README.md

+21-21
Original file line numberDiff line numberDiff line change
@@ -189,11 +189,11 @@ $ cd mbed-os
189189
$ mbed releases
190190
mbed-os (#182bbd51bc8d, tags: latest, mbed-os-5.6.5)
191191
...
192-
* mbed-os-5.6.0
193-
* mbed-os-5.6.1
194-
* mbed-os-5.6.2
195-
* mbed-os-5.6.3
196-
* mbed-os-5.6.4
192+
* mbed-os-5.6.0
193+
* mbed-os-5.6.1
194+
* mbed-os-5.6.2
195+
* mbed-os-5.6.3
196+
* mbed-os-5.6.4
197197
* mbed-os-5.6.5 <- current
198198
```
199199

@@ -300,21 +300,21 @@ Removing a library from your program is not the same as deleting the library dir
300300
Use `mbed add` to add the latest revision of a library:
301301

302302
```
303-
$ mbed add https://developer.mbed.org/users/wim/code/TextLCD/
303+
$ mbed add https://os.mbed.com/users/wim/code/TextLCD/
304304
```
305305

306306
Use the `URL#hash` format to add a library from a URL at a specific revision hash:
307307

308308
```
309-
$ mbed add https://developer.mbed.org/users/wim/code/TextLCD/#e5a0dcb43ecc
309+
$ mbed add https://os.mbed.com/users/wim/code/TextLCD/#e5a0dcb43ecc
310310
```
311311

312312
#### Specifying a destination directory
313313

314314
If you want to specify a directory to which to add your library, you can give an additional argument to ``add``, which names that directory. For example, If you'd rather add the previous library in a directory called "text-lcd" (instead of TextLCD):
315315

316316
```
317-
$ mbed add https://developer.mbed.org/users/wim/code/TextLCD/ text-lcd
317+
$ mbed add https://os.mbed.com/users/wim/code/TextLCD/ text-lcd
318318
```
319319

320320
Although Mbed CLI supports this functionality, we don't encourage it. Adding a library with a name that differs from its source repository can lead to confusion.
@@ -443,7 +443,7 @@ The arguments for *compile* are:
443443

444444
You can find the compiled binary, ELF image, memory usage and link statistics in the `BUILD` subdirectory of your program.
445445

446-
For more information on build profiles, see [our build profiles](https://docs.mbed.com/docs/mbed-os-handbook/en/latest/dev_tools/build_profiles/) and [toolchain profiles](https://docs.mbed.com/docs/mbed-os-handbook/en/latest/advanced/toolchain_profiles/) pages.
446+
For more information on build profiles, see [our build profiles](https://os.mbed.com/docs/latest/tools/build-profiles.html) and [toolchain profiles](https://os.mbed.com/docs/latest/tools/toolchain-profiles.html) pages.
447447

448448
### Compiling static libraries
449449

@@ -475,7 +475,7 @@ Image: ../threaded_blinky-out/threaded_blinky.bin
475475

476476
### Compile configuration system
477477

478-
The [compile configuration system](https://docs.mbed.com/docs/mbed-os-handbook/en/5.3/advanced/config_system/) provides a flexible mechanism for configuring the Mbed program, its libraries and the build target.
478+
The [compile configuration system](https://os.mbed.com/docs/v5.10/reference/configuration.html) provides a flexible mechanism for configuring the Mbed program, its libraries and the build target.
479479

480480
#### Inspecting the configuration
481481

@@ -965,7 +965,7 @@ The update command fails if there are changes in your program or library that `m
965965

966966
### Updating to an upstream version
967967

968-
Before updating a program or a library, it's good to know the names of the stable releases, usually marked with a tag using a common format, such as `1.2`, `v1.0.1`, `r5.6`, `mbed-os-5.6` and so on.
968+
Before updating a program or a library, it's good to know the names of the stable releases, usually marked with a tag using a common format, such as `1.2`, `v1.0.1`, `r5.6`, `mbed-os-5.6` and so on.
969969

970970
You can find stable release versions of a program or a library using the `mbed releases` command:
971971

@@ -974,11 +974,11 @@ $ cd mbed-os
974974
$ mbed releases
975975
mbed-os (#182bbd51bc8d, tags: latest, mbed-os-5.6.5)
976976
...
977-
* mbed-os-5.6.0
978-
* mbed-os-5.6.1
979-
* mbed-os-5.6.2
980-
* mbed-os-5.6.3
981-
* mbed-os-5.6.4
977+
* mbed-os-5.6.0
978+
* mbed-os-5.6.1
979+
* mbed-os-5.6.2
980+
* mbed-os-5.6.3
981+
* mbed-os-5.6.4
982982
* mbed-os-5.6.5 <- current
983983
```
984984

@@ -990,12 +990,12 @@ Lastly, you can list unstable releases, such as release candidates, alphas and b
990990
$ cd mbed-client
991991
$ mbed releases -u
992992
mbed-client (#31e5ce203cc0, tags: v3.0.0)
993-
* mbed-os-5.0-rc1
994-
* mbed-os-5.0-rc2
995-
* r0.5-rc4
993+
* mbed-os-5.0-rc1
994+
* mbed-os-5.0-rc2
995+
* r0.5-rc4
996996
...
997-
* v2.2.0
998-
* v2.2.1
997+
* v2.2.0
998+
* v2.2.1
999999
* v3.0.0 <- current
10001000
```
10011001

0 commit comments

Comments
 (0)