You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: mcwin32/doc/INSTALL.md
+30-16Lines changed: 30 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,7 @@ To build and install mcwin32, you shall need:
23
23
* Git tooling for windows.
24
24
* Perl 5 with core modules, see [NOTES-PERL.md](doc/NOTES-PERL.md).
25
25
* CoreUtils, includes various text and system utilities.
26
+
* Gettext
26
27
* Make.
27
28
* An ANSI C/C++ compiler.
28
29
* A development environment in the form of development libraries and C header files.
@@ -79,7 +80,7 @@ Several alternative profiles are available:
79
80
* Open-Watcom (OWC) 1.9 or 2.0; or
80
81
81
82
* owcconfig - Open Watcom 1.9
82
-
* owc20config - Open Watcom 2.0
83
+
* owc20config - Open Watcom 2.0
83
84
84
85
* MingW64, both 32 and 64 bit targets.
85
86
@@ -169,10 +170,10 @@ The follow offers a more detailed discussion of the requirements and instruction
169
170
-[Native builds using Visual C++](#native-builds-using-visual-c-c)
170
171
-[Native builds using MinGW64](#native-builds-using-mingw)
171
172
172
-
Finally, please review the packaged example alternative configurations as win32 development environments can be problematic, dependent on the host setup:
173
+
Finally, please review the packaged example alternative configurations as win32 development environments can be problematic, dependent on the host setup:
173
174
174
175
- .github/workflows, github build actions for owc, msvc and mingw64 toolchains.
175
-
- Appveyor CI integration notes [Appveyor CI](CINotes.md).
176
+
- Appveyor CI integration notes [Appveyor CI](CINotes.md).
176
177
177
178
Native builds using Open-Watcom C/C++
178
179
====================================
@@ -226,6 +227,14 @@ Minimal tools required are:
226
227
227
228
Once installed the required commands should be visible within the path.
228
229
230
+
* gettext - gettext utilities are a set of tools that provides a framework to help packages produce multi-lingual messages.
*[gettext for windows](https://github.com/mlocati/gettext-iconv-windows)
237
+
229
238
To support native Windows builds, the make tool ``gmake-42``, web tool ``wget`` and the shell support tool ``busybox`` are bundled within the source repository sub-directory ``win32/``.
230
239
231
240
-``gmake`` was built from its original source available from [GNU binutils](https://www.gnu.org/software/binutils/).
@@ -266,7 +275,7 @@ Quick start
266
275
From the source root, a suitable environment can be setup using the one of the following dependent on the desired toolchain, were ``C:\Watcom`` is the toolchain installation directory.
267
276
268
277
* owcconfig- Open Watcom 1.9
269
-
* owc20config - Open Watcom 2.0
278
+
* owc20config - Open Watcom 2.0
270
279
271
280
* From the root of the source directory perform the following:
272
281
@@ -314,7 +323,7 @@ The resulting work flow could look like the following, inside a Open Watcom 1.9
314
323
cd c:\projects
315
324
316
325
git clone https://github.com/adamyg/mcwin32.git mc
317
-
326
+
318
327
cd c:\projects\mc\mcwin32
319
328
320
329
git submodule update --init --recursive
@@ -338,18 +347,18 @@ Microsoft Visual is available in several, all are suitable:
338
347
339
348
* Microsoft Visual C++ 2015 - 2002 Professional -
340
349
341
-
Standard Microsoft Visual C++ installations.
350
+
Standard Microsoft Visual C++ installations.
342
351
343
352
* Microsoft Visual C++ 2015 - 2022 Community Edition -
344
353
345
-
These free versions of Visual C++ 2015-2022 Professional contain the same compilers and linkers that ship with the full versions,
354
+
These free versions of Visual C++ 2015-2022 Professional contain the same compilers and linkers that ship with the full versions,
346
355
and also contain everything necessary to build mcwin32.
347
-
348
-
* Microsoft C++ Build Tools -
356
+
357
+
* Microsoft C++ Build Tools -
349
358
350
359
There's also a standalone (IDE-less) version of the build tools mentioned above containing the MSVC compiler
351
360
available for download from https://visualstudio.microsoft.com/visual-cpp-build-tools/.
352
-
361
+
353
362
Note: Since these are proprietary and ever-changing I cannot test them all. Older versions may not work, it is recommended to use a recent version wherever possible.
354
363
355
364
* Install _Perl_
@@ -393,7 +402,7 @@ The resulting work flow could look like the following, inside a 2019 developer p
393
402
cd c:\projects
394
403
395
404
git clone https://github.com/adamyg/mcwin32.git mc
396
-
405
+
397
406
cd c:\projects\mc\mcwin32
398
407
399
408
git submodule update --init --recursive
@@ -412,8 +421,8 @@ Native builds using Mingw
412
421
413
422
Mingw64 (32/64) offers another alternative way to build native __mcwin32__, similar to Open-Watcom C/C++ builds.
414
423
415
-
MSYS2 provides GNU tools, a Unix-like command prompt, and a UNIX compatibility layer for applications,
416
-
available from https://www.mingw-w64.org. However, in this context it is only used for building mcwin32.
424
+
MSYS2 provides GNU tools, a Unix-like command prompt, and a UNIX compatibility layer for applications,
425
+
available from https://www.mingw-w64.org. However, in this context it is only used for building mcwin32.
417
426
The resulting application does not rely on MSYS2 to run and is fully native.
418
427
419
428
*_MSYS2_ shell, from https://www.msys2.org/
@@ -433,9 +442,14 @@ The resulting application does not rely on MSYS2 to run and is fully native.
433
442
$ pacman --noconfirm -S mingw-w64-x86_64-gcc
434
443
$ pacman --noconfirm -S mingw-w64-i686-gcc
435
444
436
-
These compilers must be on your MSYS2 \$PATH, example below assuming the default installation path ``c:/msys64/``.
445
+
These compilers must be on your MSYS2 \$PATH, example below assuming the default installation path ``c:/msys64/``.
437
446
A common error is to not have these on your \$PATH. The MSYS2 version of gcc will not work correctly here.
0 commit comments