Skip to content

Integration Guide

Equis is designed to operate primarily as a native subset executable within conventional systems or as a standalone toolchain.

Standalone Pipeline

For direct script interactions:

  1. Write Example Definitions Include standard library modules using the -I flag.
    • Linux/macOS: ./eq compile main.equis -I std/
    • Windows: .\eq compile main.equis -I std\
  2. Execution Context The produced binary expects the host environment to fulfill all defined dependencies labeled extern fn.

Professional Hosting

The Equis compiler runs natively as a pre-built binary. When integrating into larger systems, invoke the eq CLI directly or link against the compiled LLVM object files (.o). This ensures consistency across production nodes.

Bridging C/FFI

All components are C-ABI compliant by default through LLVM mapping. When an Equis extern fn sys_malloc(size) is invoked, it links to the standard libc export unless intercepted by your specific runtime framework.

To handle complex external bindings, ensure your host target (clang or gcc) links the corresponding symbols statically alongside the IR generated by Equis. On Windows, use -lws2_32 for networking support.