Skip to content

Commit f97f65e

Browse files
author
B I Mohammed Abbas
committed
Add myself as VxWorks target maintainer
1 parent 83dcdb3 commit f97f65e

File tree

1 file changed

+51
-0
lines changed

1 file changed

+51
-0
lines changed
Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
# `*-wrs-vxworks`
2+
3+
**Tier: 3**
4+
5+
Targets for the VxWorks operating
6+
system.
7+
8+
Target triplets available:
9+
10+
- `x86_64-wrs-vxworks`
11+
- `aarch64-wrs-vxworks`
12+
- `i686-wrs-vxworks`
13+
- `armv7-wrs-vxworks-eabihf`
14+
- `powerpc-wrs-vxworks`
15+
- `powerpc-wrs-vxworks-spe`
16+
17+
## Target maintainers
18+
19+
- B I Mohammed Abbas ([@biabbas](https://github.com/biabbas))
20+
21+
## Requirements
22+
23+
These targets can be cross-compiled with a target vsb. Std is partially supported.
24+
25+
## Building the target
26+
27+
You can build Rust with support for the targets by adding it to the `target` list in `config.toml`. In addition the workbench and wr-cc have to configured and activated.
28+
29+
```toml
30+
[build]
31+
build-stage = 1
32+
target = [
33+
"<HOST_TARGET>",
34+
"x86_64-wrs-vxworks",
35+
"aarch64-wrs-vxworks",
36+
"i686-wrs-vxworks",
37+
"armv7-wrs-vxworks-eabihf",
38+
"powerpc-wrs-vxworks",
39+
"powerpc-wrs-vxworks-spe",
40+
]
41+
```
42+
43+
## Building Rust programs
44+
45+
Rust does not yet ship pre-compiled artifacts for VxWorks.
46+
47+
The easiest way to build and test programs for VxWorks is to use the shipped pre compiled rustc and cargo in VxWorks workbench, following the official windriver guidelines on this.
48+
49+
## Cross-compilation toolchains and C code
50+
51+
The target supports C code. Pre-compiled C toolchains can be found in provided VxWorks workbench.

0 commit comments

Comments
 (0)