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
# Install ExecuTorch pip package and its dependencies, as well as
58
65
# development tools like CMake.
59
66
# If developing on a Mac, make sure to install the Xcode Command Line Tools first.
60
67
./install_executorch.sh
61
68
```
62
69
63
-
Use the [`--pybind` flag](https://github.com/pytorch/executorch/blob/main/install_executorch.sh#L26-L29) to install with pybindings and dependencies for other backends.
70
+
Use the [`--pybind` flag](https://github.com/pytorch/executorch/blob/main/install_executorch.sh#L26-L29) to install with pybindings and dependencies for other backends.
ExecuTorch's CMake build system covers the pieces of the runtime that are
107
114
likely to be useful to embedded systems users.
@@ -121,17 +128,8 @@ likely to be useful to embedded systems users.
121
128
`libportable_kernels.a`, so the program may use any of the operators it
122
129
implements.
123
130
124
-
## One-time setup to prepare for CMake Build
125
-
126
-
Follow the steps below to have the tools ready before using CMake to build on your machine.
127
-
128
-
1. If your system's version of python3 is older than 3.11:
129
-
- Run `pip install tomli`
130
-
3. Install CMake version 3.19 or later:
131
-
- Run `conda install cmake` or `pip install cmake`.
132
-
133
131
134
-
## Configure the CMake Build
132
+
### Configure the CMake build
135
133
136
134
Follow these steps after cloning or pulling the upstream repo, since the build
137
135
dependencies may have changed.
@@ -148,7 +146,7 @@ cd executorch
148
146
149
147
Once this is done, you don't need to do it again until you pull from the upstream repo again, or if you modify any CMake-related files.
150
148
151
-
### CMake Build Options
149
+
### CMake build options
152
150
153
151
The release build offers optimizations intended to improve performance and reduce binary size. It disables program verification and executorch logging, and adds optimizations flags.
154
152
```bash
@@ -163,7 +161,7 @@ To further optimize the release build for size, use both:
163
161
164
162
See [CMakeLists.txt](https://github.com/pytorch/executorch/blob/main/CMakeLists.txt)
165
163
166
-
## Build the runtime components
164
+
### Build the runtime components
167
165
168
166
Build all targets with
169
167
@@ -180,7 +178,7 @@ cd executorch
180
178
cmake --build cmake-out -j9
181
179
```
182
180
183
-
## Use an example app`executor_runner` to execute a .pte file
181
+
## Use an example binary`executor_runner` to execute a .pte file
184
182
185
183
First, generate an `add.pte` or other ExecuTorch program file using the
186
184
instructions as described in
@@ -192,7 +190,7 @@ Then, pass it to the command line tool:
0 commit comments