Skip to content

Commit 68ae9d8

Browse files
kirklandsignpytorchbot
authored andcommitted
Workaround for fbs file not found (#3855)
Summary: Pull Request resolved: #3855 Reviewed By: cccclai Differential Revision: D58206698 Pulled By: kirklandsign fbshipit-source-id: f5e70d38f39860e9ca4e8e1d0b4fd697445fdbe8 (cherry picked from commit 13dcf10)
1 parent 2a4043a commit 68ae9d8

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

backends/qualcomm/setup.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,13 @@ export LD_LIBRARY_PATH=$QNN_SDK_ROOT/lib/x86_64-linux-clang/:$LD_LIBRARY_PATH
5555
export PYTHONPATH=$EXECUTORCH_ROOT/..
5656
```
5757

58+
Note: Since we set `PYTHONPATH`, we may have issue with finding `program.fbs`
59+
and `scalar_type.fbs` when we export a model, because they are installed into
60+
`pip-out` directory with the same package name pattern. A workaround is that
61+
we copy `$EXECUTORCH_ROOT/pip-out/lib.linux-x86_64-cpython-310/executorch/exir/_serialize/program.fbs`
62+
and `$EXECUTORCH_ROOT/pip-out/lib.linux-x86_64-cpython-310/executorch/exir/_serialize/scalar_type.fbs`
63+
to `$EXECUTORCH_ROOT/exir/_serialize/`.
64+
5865

5966
## End to End Inference
6067

0 commit comments

Comments
 (0)