search

ajh123 / gtmos

My rust based hobby os.
Apache License 2.0
0 stars 0 forks source link

Make `cargo test` / `cargo build` work again #6

Open ajh123 opened 1 year ago

ajh123 commented 1 year ago

Work started in 9c45fe11460f5f521135d4112a8f7f52ae091e54

ajh123 commented 1 year ago

cargo test or cargo build fails with:

   Compiling gtmos_tools v0.1.0 (F:\rust\gtmos\tools)
error: language item required, but not found: `eh_personality`
  |
  = note: this can occur when a binary crate with `#![no_std]` is compiled for a target where `eh_personality` is defined in the standard library
  = help: you may be able to compile for a target that doesn't need `eh_personality`, specify a target with `--target` or in `.cargo/config`

error: could not compile `gtmos_kernel` (bin "gtmos_kernel") due to previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `gtmos_kernel` (bin "gtmos_kernel" test) due to previous error
error: could not compile `gtmos_kernel` (test "basic_boot") due to previous error
error: could not compile `gtmos_kernel` (test "should_panic") due to previous error
error: could not compile `gtmos_kernel` (lib test) due to previous error

However, cargo run still works. I'm not sure how I can fix this issue ¯\(ツ)/¯

ajh123 commented 1 year ago

When cargo test is ran it should compile correctly and run the operating system's test runner which will run all the tests. The test runner will output its own serial output. The QEMU Exit device should be implemented again. More info: https://os.phil-opp.com/testing/