1
0

refinement

This commit is contained in:
dtb 2023-01-07 17:39:01 -05:00
parent 65fb6c194e
commit c00d19e7ff

View File

@ -8,33 +8,43 @@ I won't sue you.
## Files
Simexec is a single C file (`simexec.c`) that builds to a single executable,
which should be named `simexec` and placed in a user-accessible binaries
directory. A `Makefile` is provided as courtesy but isn't really necessary.
- `src/simexec`
- Can be moved to a system sources directory if it's desirable to keep
system sources on hand. Doesn't reference anything else in the
repository.
The `src/simexec` directory can be moved to a system sources directory if you
wish to keep the source on hand; it doesn't reference anything else in the
repository.
- `simexec.1`
- Included manual page for `simexec`. Can be placed in the appropriate
manual pages directory. If it displays weirdly and your fix is
portable, mail me and I'll probably bring it upstream.
- `simexec.c`
- A single C file that builds to a single executable, which should be
named `simexec`.
The included manual page, `simexec.1` can be placed in the appropriate manual
pages directory. If it displays weirdly feel free to e-mail me and I'll attempt
to fix it.
- `simexec`
- Program binary. Should be placed in a user-accessible binaries
directory.
## Dependencies
- `<sysexits.h>`
- Ignored if `EX_USAGE` is already defined.
- C standard library
## Compilation
On systems that provide `<sysexits.h>`, the following is all that's needed:
```
cc -o simexec simexec.c
```
If you're not sure whether your system provides `<sysexits.h>`, try it and see.
If it doesn't work, compile `simexec.c` with the following:
Or without `<sysexits.h>`:
```
cc -DEX_USAGE=1 -o simexec simexec.c
```
Other than `<sysexits.h>` simexec(1) only relies on headers found in the C
standard library. Outside of POSIX environments `simexec.c` probably won't work
but it wouldn't be of much use anyway.
## Known packages
- [On the Arch User Repository](https://aur.archlinux.org/packages/simexec-git).