You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 14, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -1,25 +1,25 @@
1
1
# What is this
2
-
This is a single click installer for mbed CLI on OSX. If you want the installer please see the Releases page for the latest download link.
3
-
Included in the installer is the latest stable version of all tools required to develop in the mbed Ecosystem with mbed CLI.
2
+
This is a single click installer for Mbed CLI on OS X. If you want the installer please see the Releases page for the latest download link.
3
+
Included in the installer is the latest stable version of all tools required to develop in the Mbed Ecosystem with Mbed CLI.
4
4
- Python 2.7.x
5
-
-GCC ARM compiler
6
-
-mbed CLI
5
+
-GNU Arm Embedded Toolchain (GCC)
6
+
-Mbed CLI
7
7
- mbedls
8
8
- mbed-greentea
9
9
- mbed-host-tests
10
-
- any other relevant mbed python utilities
10
+
- any other relevant Mbed Python utilities
11
11
12
12
## How to use
13
13
Download the .dmg file, open it. Copy the app to your applications folder. Run application from your applications folder.
14
14
15
15
## How does it work
16
-
When you run the app a Terminal is opened with modified local session variables that link to the versions of python, gcc compiler and mbed tools included in the installer.
16
+
When you run the app a Terminal is opened with modified local session variables that link to the versions of Python, the GCC toolchain and Mbed tools included in the installer.
17
17
18
18
## Why?
19
-
Because we want something that 'just works' for users in a consistent, reproducable way.
19
+
Because we want something that "just works" for users in a consistent, reproducable way.
20
20
21
21
## But I like installing my tools myself
22
-
Cool, you can do that too. See the instructions [here](TODO) for how to install all the tools individually on your system.
22
+
See the instructions [here](TODO) for how to install all the tools individually on your system.
23
23
24
24
## Whats next?
25
25
Go build awesome.
@@ -29,7 +29,7 @@ Go build awesome.
29
29
30
30
# How to Build
31
31
1) Update all dependencies in repo (GCC, Python Eggs, ...etc)
32
-
- For compiler updates, unzip the folder into the gcc folder, then modify the setup.py and run-mbed-cli.sh files config section to trace the new path
32
+
- For compiler updates, unzip the folder into the GCC folder, then modify the setup.py and run-mbed-cli.sh files config section to trace the new path
33
33
- for adding new tools like mbedls and mbed-cli that should have user available calls from the command like `$mbed` you should add them to the `bin` folder. Make sure to modify the shebang to be similar to existing aliases in the bin folder.
0 commit comments