Home /Modules/build/PRODUCTS.md

PRODUCTS.md

build/PRODUCTS.md · 144 line(s) · markdown

SLeeLa Product Build Appropriation

The build/ tree is the native product-build boundary for SLeeLa. Product builds remain separate from source, generated build trees, caches, and runtime state.

Products

SLeeLa Regex

Source: regex/

Purpose:

Build entry point:

make -C regex test

Focused native targets:

make -C regex c make -C regex cpp make -C regex clean

Build output is isolated under:

regex/build/

The native implementation remains authoritative under regex/src/. The lib/regex/ tree represents SLeeLa language objects and integration metadata; it does not duplicate the native implementation.

Slecompiler™

Source: decompiler/

Purpose:

Platform entry points:

Build output is placed under:

The scripts configure and build the existing decompiler/CMakeLists.txt. They do not replace or regenerate the Slecompiler source tree.

Slecompiler™ API exemplars

The decompiler CMake project provides focused executable exemplars for the public analysis surface:

ExemplarDemonstrates
slecompiler-api-inspectArtifact opening, identification, and metadata inspection
slecompiler-api-cfgDecode-oriented analysis and control-flow graph work
slecompiler-api-libraryLibrary/archive metadata inspection
slecompiler-api-graphLibrary-family dependency graph analysis
slecompiler-api-slir-vmSLIR/lifted representation and VM-oriented analysis

These examples are deliberately small entry points for application developers. They are documentation-by-execution: each should remain buildable with the same CMake target used by the product library.

Skya

Source: telephony-skya/native/

Existing platform entry points:

Build boundary

Each product receives:

  1. Its own source-of-truth directory.
  2. Platform-specific build entry points.
  3. A product-specific output directory.
  4. No execution of analyzed native artifacts as part of Slecompiler builds.
  5. A path for later packaging/signing without mixing package output into source.

For Regex specifically, the native source-of-truth directory is regex/; the language object surface is lib/regex/; and native build output is regex/build/.

Documentation boundary

Slecompiler documentation is split by purpose:

The tutorial and exemplars are intentionally aligned with the CMake targets rather than inventing a second build system.

Future product build layers

The build appropriation is intentionally extensible for:

Generated build trees are disposable. Product source remains authoritative in its product directory.

Windows 10+ and macOS portability

Slecompiler's build boundary is explicitly cross-platform:

Windows 10+

Example with Visual Studio 2022:

powershell -ExecutionPolicy Bypass -File .\\build\\slecompiler-windows.ps1 -Generator "Visual Studio 17 2022" -Architecture x64

macOS

The portability boundary applies to the build system as well as the product source: platform-specific build mechanics stay in build/, while Slecompiler source remains authoritative under decompiler/.