Better understand the no_std binary use case.

rust-lang / wg-cargo-std-aware

Repo for working on "std aware cargo"

137 stars 8 forks source link

Better understand the no_std binary use case. #36

Open ehuss opened 5 years ago

ehuss commented 5 years ago

Building no_std binaries can be tricky, but it seems like the current implementation is even more tricky. For example, in my tests it required manually linking against libc on Linux which I don't think is normally required. It would be nice if this was a smoother process, and should get a little more investigation to make sure it works.

leo60228 commented 5 years ago

Is this related to std-aware cargo? I think this is a general no_std problem, and I think that implicitly linking against libc would only make the problem worse.

phil-opp commented 5 years ago

As an example use case, I'm using a no_std binary with a custom entry point for my OS blog.

Ericson2314 commented 5 years ago

I wouldn't sweat this to much. There's tons of variation on how one wants to make the binary, and most the complexity is not Cargo's fault.