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