mirror of
https://github.com/ahgamut/rust-ape-example.git
synced 2024-11-21 15:30:59 +00:00
Rust decides system constants at compile time
This commit is contained in:
parent
f81a13d73d
commit
9c075456bb
1 changed files with 11 additions and 1 deletions
12
README.md
12
README.md
|
@ -1,4 +1,14 @@
|
|||
# Actually Portable Executables with Cosmopolitan Libc and Rust
|
||||
# Cosmopolitan Libc and Rust
|
||||
|
||||
> Note: the executables built using Cosmo and Rust do not work across the
|
||||
> operating systems supported by Cosmopolitan Libc, because Rust decides system
|
||||
> constants like `EINVAL` [at
|
||||
> compile-time](https://github.com/search?q=repo%3Arust-lang%2Flibc%20EINVAL&type=code),
|
||||
> based on the operating system provided in the compilation target. Thus, I
|
||||
> expect the fat binaries built here will only work on `x86-64-linux` and
|
||||
> `aarch64-linux`. Very well, perhaps in the future we can find a way to have
|
||||
> system constants as `extern` values in Rust, like how [I did it for
|
||||
> C](https://github.com/ahgamut/gcc/tree/portcosmo-11.2).
|
||||
|
||||
This repository contains a simple `Hello world!` example in the [Rust][rust]
|
||||
programming language, that builds with [Cosmopolitan Libc][cosmo]. Now it also
|
||||
|
|
Loading…
Reference in a new issue