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
Summary:
For executorch users, we see a common pattern that they have to:
```bash
bash install_requirements.sh --pybind xnnpack
cmake -S . -Bcmake-out ...
cmake --build ...
```
This is repeating cmake build twice, the first one is inside setup.py.
Here I'm adding a way to allow setup.py to install the libraries
seperately, by passing `CMAKE_ARGS` and `CMAKE_BUILD_ARGS` into
setup.py, through `install_requirements.sh`.
After this change, user can do:
```bash
export CMAKE_ARGS="-DCMAKE_INSTALL_PREFIX=<install dir> \
-DEXECUTORCH_BUILD_OPTIMIZED=ON \
..."
export CMAKE_BUILD_ARGS="--target install"
bash install_requirements.sh --pybind xnnpack
```
Then we should be able to find `libxnnpack.a` `liboptimized_ops_lib.a`
etc under install dir.
Test Plan:
Reviewers:
Subscribers:
Tasks:
Tags:
0 commit comments