Cc Build

C/C++ Compiler (clang)

**🔨 Construct tier — this skill produces an artifact, it doesn't read a sample.**

Purpose

cc-build creates the native artifacts RE work needs: PoCs, test harnesses, decompiler fixtures, and shared libraries. It compiles but does not run the result. Use exec-observe for an executable or emulate-code for shellcode and object bytes.

What it does

Thin, honest wrapper over clang (falls back to cc/gcc): picks a compiler, builds the argv, runs it, and reports the artifact path/size plus the compiler diagnostics.

• --emit exe|obj|asm|ir — link an executable, a .o, assembly (.s), or LLVM IR

(.ll, clang only). asm/ir are great for seeing what the compiler generates.

• Cross-compile with --target and/or --arch.
• --std, --opt, --shared, --static, and --cflags "…" for anything else.

Prerequisites

• A C compiler — clang (macOS: xcode-select --install; Linux: install clang/LLVM)

or gcc. Checked flexibly (clang || cc || gcc); absent → honest install hint.

Safety

executes_input: no — the produced binary is never run. Caveat: compiling untrusted source still invokes a compiler, so it's tier 1, not 0. The usual input is your own trusted PoC source.

Usage

rekit run cc-build poc.c --out poc                       # build an exe
rekit run cc-build shellcode_stub.c --emit obj           # → .o for emulate-code
rekit run cc-build foo.c --emit asm --opt 0              # see the codegen
rekit run cc-build mod.c --shared --target aarch64-linux-gnu   # cross-compiled .so

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: batteryshark
• Source: batteryshark/rekit
• License: Apache-2.0

Install and usage instructions live in the source repository linked above.