Overview
| Comment: | README.md: Fix a weird line break |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
eb5856147302c4f1380396e983d0fb81 |
| User & Date: | js on 2020-06-01 18:29:29 |
| Other Links: | manifest | tags |
Context
|
2020-06-01
| ||
| 19:31 | PLATFORMS.md: Add Windows 98 SE and NT 4.0 check-in: 97007c865f user: js tags: trunk | |
| 18:29 | README.md: Fix a weird line break check-in: eb58561473 user: js tags: trunk | |
| 00:17 | README.md: Add documentation section check-in: 1d627ae293 user: js tags: trunk | |
Changes
Modified README.md from [95380e6631] to [d6ae3e7b42].
| ︙ | ︙ | |||
239 240 241 242 243 244 245 |
$ pacman -S mingw-w64-i686-clang mingw-w64-i686-gcc-objc
For 64 bit binaries:
$ pacman -S mingw-w64-x86_64-clang mingw-w64-x86_64-gcc-objc
There is nothing wrong with installing them both, as MSYS2 has created two
| | | | | 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 |
$ pacman -S mingw-w64-i686-clang mingw-w64-i686-gcc-objc
For 64 bit binaries:
$ pacman -S mingw-w64-x86_64-clang mingw-w64-x86_64-gcc-objc
There is nothing wrong with installing them both, as MSYS2 has created two
entries in your start menu: `MinGW-w64 Win32 Shell` and
`MinGW-w64 Win64 Shell`. So if you want to build for 32 or 64 bit, you just
start the correct shell.
Finally, install a few more things needed to build ObjFW:
$ pacman -S autoconf automake fossil make
<h3 id="steps-windows">Getting, building and installing ObjFW</h3>
|
| ︙ | ︙ |