Closed #546.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/546#event-5177519238
The problem solved, thanks.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/546#issuecomment-901482402
@ya0guang @mssun Thank you for the clarification. However, I still see some
workspaces, e.g. `executor` which didn't get indexed either way because they
seems not be included in both Cargo.toml files as workspace members.
--
You are receiving this because you are subscribed to this thread.
Re
Hi, this is not feasible right now. Teaclave uses two set of Rust dependencies
for SGX enclave and untrusted normal world separately. We haven't consolidated
these into one. Therefore, we have to compile code in different worlds
separately with different `Cargo.toml` files. You can find there he
The trusted part and untrusted part use different set of crates. So we provide
a script to prepare analyzer's essentials. You may check [this
doc](https://teaclave.apache.org/docs/development-tips/) and try with the
script to see if it can solve your concern.
--
You are receiving this because
### Motivation & problem statement
The code analyzer cannot correctly identify this rust project and its
workspaces corresponding to each subdirectories.
### Proposed solution
Adding a top-level Cargo.toml, this configures a virtual workspace – a
workspace that is only a container for member pa
