Skip to content

Commit

Permalink
Workaround for fbs file not found (#3855)
Browse files Browse the repository at this point in the history
Summary: Pull Request resolved: #3855

Reviewed By: cccclai

Differential Revision: D58206698

Pulled By: kirklandsign

fbshipit-source-id: f5e70d38f39860e9ca4e8e1d0b4fd697445fdbe8
  • Loading branch information
kirklandsign authored and facebook-github-bot committed Jun 5, 2024
1 parent 7bb2c58 commit 13dcf10
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions backends/qualcomm/setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,13 @@ export LD_LIBRARY_PATH=$QNN_SDK_ROOT/lib/x86_64-linux-clang/:$LD_LIBRARY_PATH
export PYTHONPATH=$EXECUTORCH_ROOT/..
```

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


## End to End Inference

Expand Down

0 comments on commit 13dcf10

Please sign in to comment.