chore(cli): do not look up target

[clearloop]

Resolves #17

The problem is that the target folder does not exist before we can cargo build or cargo test that we got look up failed on jade build, now we switch to looking up Cargo.toml for the workspace root

[danicuki]

I also have a similar issue here:

 /private/tmp/service-test/my-service (main)₿ cargo build
   Compiling stoken v0.0.13 (/private/tmp/service-test/my-service)
error: failed to run custom build command for `stoken v0.0.13 (/private/tmp/service-test/my-service)`

Caused by:
  process didn't exit successfully: `/private/tmp/service-test/my-service/target/debug/build/stoken-c4ea432329ae096c/build-script-build` (exit status: 101)
  --- stdout
  rerun-if-changed=build.rs
  rerun-if-changed=src
  🪤 PVM module type: Service
  🎯 Target name: riscv64emac-unknown-none-polkavm

  --- stderr

  thread 'main' panicked at /Users/danicuki/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/cjam-0.0.13/src/builder.rs:141:17:
  `rust-src` component of 1.90.0 is required to build the PVM binary.
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[Timosdev99]

I also have a similar issue here:

 /private/tmp/service-test/my-service (main)₿ cargo build
   Compiling stoken v0.0.13 (/private/tmp/service-test/my-service)
error: failed to run custom build command for `stoken v0.0.13 (/private/tmp/service-test/my-service)`

Caused by:
  process didn't exit successfully: `/private/tmp/service-test/my-service/target/debug/build/stoken-c4ea432329ae096c/build-script-build` (exit status: 101)
  --- stdout
  rerun-if-changed=build.rs
  rerun-if-changed=src
  🪤 PVM module type: Service
  🎯 Target name: riscv64emac-unknown-none-polkavm

  --- stderr

  thread 'main' panicked at /Users/danicuki/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/cjam-0.0.13/src/builder.rs:141:17:
  `rust-src` component of 1.90.0 is required to build the PVM binary.
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I encountered similar issues too. Try updating or adding the rust-src component. And it will be resolved

[clearloop]

thanks for the reports! will add

jade/.github/workflows/main.yml

Lines 18 to 22 in 9d51dfe

	- name: Install Toolchain
	run: |
	rustup toolchain install 1.90.0
	rustup component add rust-src --toolchain 1.90.0
	rustup update stable && rustup default stable

to the README (or in the pre-build checks, seems more reasonable) as well in this PR!

[danicuki]

even after adding the 1.90.0 toolchain, now I get:

 /private/tmp/service-test/my-service (main)₿ jade build
🪤 PVM module type: Service
🎯 Target name: riscv64emac-unknown-none-polkavm
ℹ️ `rustup` and toolchain installed. Continuing build process...
📦 Crate name: stoken
🏷️ Build profile: release
error: the 'cargo' binary, normally provided by the 'cargo' component, is not applicable to the '1.90.0-aarch64-apple-darwin' toolchain
Failed to build RISC-V ELF due to cargo execution error

[Timosdev99]

even after adding the 1.90.0 toolchain, now I get:

 /private/tmp/service-test/my-service (main)₿ jade build
🪤 PVM module type: Service
🎯 Target name: riscv64emac-unknown-none-polkavm
ℹ️ `rustup` and toolchain installed. Continuing build process...
📦 Crate name: stoken
🏷️ Build profile: release
error: the 'cargo' binary, normally provided by the 'cargo' component, is not applicable to the '1.90.0-aarch64-apple-darwin' toolchain
Failed to build RISC-V ELF due to cargo execution error

did you try running cargo clean after adding the toolchain?

[clearloop]

even after adding the 1.90.0 toolchain, now I get:

 /private/tmp/service-test/my-service (main)₿ jade build
🪤 PVM module type: Service
🎯 Target name: riscv64emac-unknown-none-polkavm
ℹ️ `rustup` and toolchain installed. Continuing build process...
📦 Crate name: stoken
🏷️ Build profile: release
error: the 'cargo' binary, normally provided by the 'cargo' component, is not applicable to the '1.90.0-aarch64-apple-darwin' toolchain
Failed to build RISC-V ELF due to cargo execution error

interesting, I'll add macos CI as well in this PR, just back to my keyboard today, will update our implementation to 0.7.1 / 0.7.2 first