Skip to content

Commit a499ecf

Browse files
authored
Update README.md
1 parent 4cd707b commit a499ecf

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

README.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
real-time-cpp-toolchains
22
==================
33

4-
This repository provides information and links to `Win*`-ported GNU/GCC toolchains
4+
This repository provides information and links to GNU/GCC toolchains
55
synchronized with [real-time-cpp](https://github.com/ckormanyos/real-time-cpp).
66
They can be used (among other purposes) for building the reference application
7-
(`ref_app`) for embedded targets and the examples on `Win*`.
7+
(`ref_app`) for embedded targets and the examples on `Win*` and/or `*nix`.
88

99
## Supported Toolchain Targets
1010

@@ -21,14 +21,15 @@ They can be used (among other purposes) for building the reference application
2121

2222
## Further details
2323

24-
The references usually include GNU/GCC toolchains are built to run on
25-
both `Win*` as well as `*nix`. The `Win*` versions, in particular,
24+
The references usually include GNU/GCC toolchains built to run on
25+
`Win*` and also toolchains built to run on `*nix` (and maybe others).
26+
The `Win*` versions, in particular,
2627
can be used by developers who optionally run the builds in the
2728
[real-time-cpp](https://github.com/ckormanyos/real-time-cpp)
2829
repository on `Win*` batches or in Microsoft(R) VisualStudio(R).
29-
3030
Other standalone uses for any of these toolchains are, of course, possible.
31-
They are typically completely moveable, entirely dependency-free (no DLLs)
31+
32+
The toolchains are typically completely moveable, entirely dependency-free (no DLLs),
3233
and built to run out-of-the-box.
3334

3435
# Finding/Extracting the GNU/GCC Toolchains

0 commit comments

Comments
 (0)