-
Notifications
You must be signed in to change notification settings - Fork 45
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
Minimum version of Rust required to build? #47
Comments
OK, I tracked this one down shortly after posting up and it's not the Rust version that's the problem - it's the Makefile's use of echo that's causing the build failure. At lines 80, 88 and 96, the Makefile has this code: echo -n '\nfirmware-manager ... This is incorrect quoting - single quotes override any backslash escaping and put the literal backslash and n in the output instead. The fix I tried (that worked) was to remove the \n and put it as a separate echo statement of its own on the line above. So for example, line 80/81 becomes: echo >> gtk/Cargo.toml Once I fixed the 3 sections of the Makefile with the problem, I got further (but hit a git snag almost straight away that I'll post up as a separate issue). |
Rust projects define the minimum Rust version through the rust-toolchain file |
Why is this issue closed when the cause was not addressed?
Line 27 ends up like this:
|
What shell does your Make use by default? It works on our build server, and on my two development machines. Otherwise we wouldn't have packages being built. |
I'm using |
See if the latest commit fixes your issue. The default shell used on the debian platform is |
Yes, that worked. Thank you. |
Looking at README.md, I see no mention of what the minimum version of Rust is required to build Firmware Manager.
I just tried building it on CentOS 7 (after a "yum install cargo") and cargo threw out an error:
cargo run -p tools --bin desktop-entry --
--appid com.system76.FirmwareManager
--name "Firmware Manager"
--icon firmware-manager
--comment "Manage system and device firmware"
--keywords firmware
--keywords system76
--keywords fwupd
--keywords lvfs
--categories System
--categories GTK
--binary com.system76.FirmwareManager
--prefix /usr
--startup-notify
error: failed to parse manifest at
/tmp/firmware-manager-master/gtk/Cargo.toml
Caused by:
could not parse input as TOML
Caused by:
unexpected character found:
\\
at line 22EPEL for CentOS 7 only has Rust 1.36.0, which presumably isn't recent enough - could you please add the minimum Rust version requirement to README.md?
The text was updated successfully, but these errors were encountered: