Prim aims to be a process imager and loader. Right now it's junk.
Prim is built with Cmake.
You can build Prim by running running:
Prim$ cmake -B build .
Prim$ cmake --build buildThe build can be customized and controlled through standard Cmake configuration and options.
Prim expects all code contributions to pass Continuous Integration (CI) testing which enforces code style and correctness. We recommend you save time by checking your code meets our standards before pushing it. You can use the following commands to check code your code.
You can check your code is formatted to meets our style guide using:
$ find src include -name *.h -o -name *.c | xargs clang-format --style=file -dry-run -Werrorclang-format should produce no errors, returning status code 0.
You can automatically reformat any problematic files to meet our style guide using:
$ clang-format --style=file -i file/to/format$ find src include -name *.c -o -name *.h | xargs -i clang-tidy --config="" {} -- -Iincludeclang-tidy should produce no errors or warnings (suppressed warning from non-user code are okay,) returning status code 0.
$ mkdir build
$ CFLAGS='-W -Wall -Wextra -Wpedantic -std=c99` cmake -B build .
$ cmake --build build [-j8]Your code should compile under GCC or Clang with strict C99 errors enabled.
Prim initially aims to support loading statically linked ELF64 executable, from userspace, on a Linux x86-64 machine.
The aim is to enable performance comparisons between current kernel loaders, and Prim.
The minimum viable produced aims to demonstrate basic loading from userspace.
- Static loading only.
- ELF64 binaries only.
- Userspace Linux x86-64 platform.
Further development may include:
- Dynamic loading and linking.
- Additional binary formats.
- Ports to other platforms, including kernel modules.
- Generating process images. (Core dumps on demand.)
- Generating binaries from raw data (Object file generation...)