[Cross Compile with Python] about erdos

[pschafhalter]

I unfortunately wasn't able to replicate the steps (ran into another error on the way -- maybe because I only have access to x86 hardware :)

Are you using the latest version of ERDOS (v0.4.0 was just released)? If so, you may want to try installing the Python API by running the following from the root of the directory (requires maturin installed):

cd python
maturin develop  # --release for release build

[yuanhaorannnnnn]

I unfortunately wasn't able to replicate the steps (ran into another error on the way -- maybe because I only have access to x86 hardware :)

Are you using the latest version of ERDOS (v0.4.0 was just released)? If so, you may want to try installing the Python API by running the following from the root of the directory (requires maturin installed):

cd python
maturin develop  # --release for release build

Thanks anyway, I finally found the bug: if we set another compile chain not default X86, the build process will make a directory named the compile chain for example "aarch64-unknown-gnu" , and make a sub-directory name "debug" to output the built binary. At the end of the building process, the program still try to find the binary at "debug" directory that does't exist, that's it.
The good news is the binary can been built successfully before the crash.