You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like it's no longer possible to build cargo-megadrive, as an inner dependency (once_cell) uses features that require a newer rust version (1.60).
I get the error namespaced features with the dep: prefix are only allowed on the nightly channel when running docker build -t rust-mega-drive:latest -f Dockerfile.megadrive .
(This command is btw also missing from the docs, but from what I can tell it is needed to make the next step work)
Edit: It works with using --locked on cargo install
The text was updated successfully, but these errors were encountered:
No its still doesn't work, I got the following error:
8.547 Compiling megadrive-graphics v0.1.0 (/rust-mega-drive/libs/megadrive-graphics)
8.789 error: couldn't read /rust-mega-drive/target/release/build/megadrive-graphics-a4b44804dd37a11d/out/default_ascii.rs: No such file or directory (os error 2)
8.789 --> libs/megadrive-graphics/src/lib.rs:8:5
8.789 |
8.789 8 | include!(concat!(env!("OUT_DIR"), "/default_ascii.rs"));
8.789 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8.789 |
8.789 = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
8.789
8.789 error: aborting due to previous error
8.789
8.790 error: could not compile `megadrive-graphics`
8.790
8.790 To learn more, run the command again with --verbose.
8.790 warning: build failed, waiting for other jobs to finish...
10.97 error: build failed
It seems like it's no longer possible to build cargo-megadrive, as an inner dependency (once_cell) uses features that require a newer rust version (1.60).
I get the error
namespaced features with the
dep:prefix are only allowed on the nightly channel
when runningdocker build -t rust-mega-drive:latest -f Dockerfile.megadrive .
(This command is btw also missing from the docs, but from what I can tell it is needed to make the next step work)
Edit: It works with using
--locked
on cargo installThe text was updated successfully, but these errors were encountered: