-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should use use path joining as the path separator, instead of hard-codes / . #71
Comments
As for building it here: yeah, sure, that's marginally a bug since we give it to other programs. Can you try the current |
If the downstream you're building is still on embed-resource 2, test with |
Thanks for your quick response. |
So, you should have something like gpui = { git = "https://github.com/zed-industries/zed" } in your Cargo.toml (and this fails to build for you) If you replace it with gpui = { git = "https://github.com/nabijaczleweli/zed" } then you'll use https://github.com/nabijaczleweli/zed with https://github.com/nabijaczleweli/zed/commit/c49760a6645d37a1c9d11f2525c2f46eb4a30a52 that will use the |
OK.
|
…1288) Accd'g to #9009 (comment) the manifest is required Followup for nabijaczleweli/rust-embed-resource#71 Release Notes: - N/A
…d-industries#21288) Accd'g to zed-industries#9009 (comment) the manifest is required Followup for nabijaczleweli/rust-embed-resource#71 Release Notes: - N/A
Link
Win10 system, build a project which depends on gpui,
after
rustup overfide set nightly
andrustup update
to 1.84-nighglyOn pwsh 7.4.6,
cargo build
panic:A rust lang member said, it (embed-resource) does not use path joining and instead hard-codes / as the path separator, which is wrong for \?\ paths. here and here
On powershell 6 ,
cargo
is working correctly with 1.84 nightly.The text was updated successfully, but these errors were encountered: