8 Commits

Author	SHA1	Message	Date
Stone Tickle	2afcdbdacb	restrict modules to embedded modules ... also alter function syntax	2023-11-25 20:45:55 -05:00
Stone Tickle	d286201f39	rename posix.h to compat.h ... Currently all compat.h does is define the appropriate POSIX macro unless you are on windows, as well as conditionally enabling __attribute__(format...).	2023-03-10 09:35:04 -05:00
Stone Tickle	4298aa2011	make muon reuse compliant ... https://reuse.software	2022-10-25 10:54:31 -04:00
Stone Tickle	b3303d30d1	remove all dependencies from tools/embedder.c ... Remove the need to build the libplatform.a.	2022-09-05 06:50:39 -05:00
Stone Tickle	f12593b0bf	unconditionally define PATH_MAX ... ~lattis/muon#26: PATH_MAX is not always defined > It seems that you unconditionally use PATH_MAX in muon, but POSIX does > not require that macro to be defined, it says that it should only be > defined if the OS has an hard limit on path length. > > From the Posix specification, in <limits.h>, under the section "Pathname > Variable Values": "A definition of one of the symbolic constants in the > following list shall be omitted from the <limits.h> header on specific > implementations where the corresponding value is equal to or greater > than the stated minimum, but where the value can vary depending on the > file to which it is applied." > > For example, GNU Hurd does not define the macro. > > In their guidelines (under the section PATH_MAX, MAX_PATH, MAXPATHLEN, > _POSIX_PATH_MAX) they give some advice about how to handle this > situation, but I believe that setting PATH_MAX to the same size of MacOS > or Linux (with something like #ifndef PATH_MAX ...) should be enough.	2022-01-04 19:01:28 -06:00
Stone Tickle	0b82d64a01	add a terminating null byte to embedded scripts	2021-11-21 07:07:14 -06:00
Stone Tickle	58cccdc5ef	use char arrays to embed strings > 4096 chars	2021-11-17 11:22:23 -06:00
Stone Tickle	3b2dc71025	add a mechanism to embed scripts in the executable	2021-11-05 19:22:17 -05:00