microsoft / microsoft/edit

Build Instructions Failed

Open
#88 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-task E-needs-discussion
Dominant language
Rust
Stars
14.6k
Forks
734
Avg merge
8h 40m
Merged PRs (30d)
4

Description

When I compile Microsoft Edit repository I receive the following error:

~/Downloads/edit$ cargo build --config .cargo/release.toml --release
Compiling edit v1.0.0 (/home/robert/Downloads/edit)
error[E0554]: #![feature] may not be used on the stable release channel
--> src/lib.rs:4:1
|
4 | / #![feature(
5 | | allocator_api,
6 | | breakpoint,
7 | | cold_path,
... |
14 | | os_string_truncate
15 | | )]
| |__^

For more information about this error, try rustc --explain E0554.
error: could not compile edit (lib) due to 1 previous error

==================================================================
I am running Linux Mint 22.1

I installed Rust:
~/Downloads/edit$ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
~/Downloads/edit$ rustup install nightly

I tried to compile Edit:
~/Downloads/edit$ cargo build --config .cargo/release.toml --release

Failed to compile as shown above.

What is the correct procedure to compile Microsoft Edit?
Perhaps the Build Instructions need to be updated?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the repository's build instructions and checking the documented toolchain against the failing cargo build command using .cargo/release.toml; the error points to the feature declarations in src/lib.rs. Reproduce the stable-channel error, document the correct procedure, and verify the instructions with the reported command.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.