Differences

This shows you the differences between two versions of the page.

--- en:projects:e4thcom [2026-05-11 22:15] – [Installation Notes] mka
+++ en:projects:e4thcom [2026-05-22 19:33] (current) – [Abstract] mm
@@ Line 13: / Line 13: @@
 //Supported Forth Systems://
-// **328eForth, 430CamelForth, 430eForth, 4e4th, AmForth, anyForth, Mecrisp, Mecrisp-Quintus, Mecrisp-Stellaris, noForth, STM8 eForth, SwapForth **//
+// **328eForth, 430CamelForth, 430eForth, 4e4th, AmForth, anyForth, ESP32forth, Mecrisp, Mecrisp-Quintus, Mecrisp-Stellaris, noForth, STM8 eForth, SwapForth **//
 The latest release is
@@ Line 19: / Line 19: @@
 ==== e4thcom-0.9.0 for Linux ====
-  * Bug fix release because with Linux kernel 6. and glibc 2.4 initializing the serial interface fails with e4thcom-0.8.5 (and 0.8.4). With e4thcom-0.9.0 now stty from the GNU Coreutils is used.
+  * 260502 : Bug fix release because with Linux kernel 6. and glibc 2.4 initializing the serial interface fails with e4thcom-0.8.5 (and 0.8.4). With e4thcom-0.9.0 now stty from the GNU Coreutils is used.
+  * **260522 : Plug-in for ESP32forth ( -t esp32forth ) added.**
-{{ :projects:e4thcom:e4thcom-0.9.0-stty-260502.tar.gz | e4thcom-0.9.0-stty.tar.gz }}
+{{ :projects:e4thcom:e4thcom-0.9.0-stty-260522.tar.gz | e4thcom-0.9.0-stty.tar.gz }}
-md5sum: 357a09d61d5d74eb2420652dd8b66089  e4thcom-0.9.0-stty-260502.tar.gz
+md5sum: 1d17517011af15c2f54960d8cd57fb26 e4thcom-0.9.0-stty-260522.tar.gz
 ==== e4thcom-0.8.5.2 ====
@@ Line 181: / Line 182: @@
 ==== Installation Notes ====
+The e4thcom package includes the file ''/doc/e4thcom-x.y.z.pdf''. **Installing e4thcom** is
+described there, however, the explanation is very brief, and for Linux novices like myself, it is not
+immediately obvious why to do it that way. Hence, I included my notes on the subject here. May
+they prove helpful. mk 20250430
 === Brief Introduction ===
@@ Line 220: / Line 226: @@
 Provided it is foreseeable that //e4thcom// will be used on the Linux system by only **one** user—namely you—it is simpler and safer to extract e4thcom into the directory ''/home/user-name/bin'' and to create the link to the e4thcom binary there as well. If this directory does not yet exist, it must be created. All of this can be done here without root privileges—that is, without SUDO—and ''/home/user-name/bin'' is automatically added to the system path. Furthermore, if necessary, you can then recompile e4thcom without root privileges; see ''~/bin/e4thcom-x.y.z/src/README''.
-Incidentally, the e4thcom package also includes a ''/doc/e4thcom-\*.pdf'' file. This procedure is recommended there as well—on page 4, or thereabouts. However, the explanation is very brief, and for Linux novices like myself, it is not immediately obvious *why* this is the case. Hence, I have included my notes on the subject here. May they prove helpful. mk 20250430