Compiling ThinkPHP8 with BPC: From Migration to Running OurBlog

Introduction

BPC is a PHP native compiler that translates PHP source code into C, then builds a dynamic library or executable, and includes a built‑in licensing mechanism for source protection, software authorization, and binary packaging.

1. Understanding ThinkPHP

The author had previously seen requests to compile ThinkPHP and examined its codebase, noting that while ThinkPHP provides test cases, the coverage of functional points is unclear. Because of PHP’s dynamic nature, successful BPC compilation does not guarantee functional parity without running the test suite.

2. Migrating OurBlog to ThinkPHP

The sample blog project “OurBlog”, originally used in the author’s “PHPUnit in Action — The Easy Way” ebook, implements basic CRUD operations and has comprehensive tests. The project was migrated to ThinkPHP to verify compilation, and the source is available at the repository bpc‑thinkphp8‑ourblog.

3. BPC Compilation: Resolving Dependencies

When creating a ThinkPHP8 project with Composer, the following packages are listed:

league/mime-type-detection (1.15.0)
league/flysystem (2.5.0)
psr/container (2.0.2)
psr/http-message (1.1)
psr/simple-cache (3.0.0)
psr/log (3.0.0)
symfony/polyfill-mbstring (v1.29.0)
symfony/var-dumper (v7.1.1)
topthink/think-helper (v3.1.6)
topthink/think-orm (v3.0.20)
topthink/framework (v8.0.3)
topthink/think-filesystem (v2.0.2)
topthink/think-trace (v1.6)

To run the OurBlog test suite only three dependencies are required:

psr/simple-cache (3.0.0)

topthink/think-helper (v3.1.6)

topthink/think-orm (v3.0.20)

For the front‑end of OurBlog the following four packages are sufficient:

psr/container (2.0.2)

psr/http-message (1.1)

psr/log (3.0.0)

topthink/framework (v8.0.3)

Because think\Facade and think\Exception are defined in both topthink/framework and topthink/think-orm, the think-orm/stubs repository must be extracted and combined with the OurBlog source, resulting in nine repositories in total (see the linked repository list).

4. BPC Compilation: Code Adjustments

Achieving a zero‑change compilation is nearly impossible. Adjustments focus on three areas:

Syntax : Unsupported syntax must be converted with phptobpc; any remaining issues require manual code changes.

File existence checks : After compilation the code runs as a binary, so functions like is_file, is_dir, file_exists, and glob must be replaced with BPC‑specific equivalents.

Reflection : BPC does not support PHP’s Reflection API, so any reflection‑based logic must be rewritten using BPC‑compatible approaches.

Detailed modification history can be inspected in the commit logs of each repository.

5. Running the Compiled Binary

Create the required database.

Execute the compiled binary named tp8-ourblog-althttpd-ubuntu-24.04-amd64.

The release is published as bpc‑thinkphp8‑ourblog release v0.1. A video demonstration of the full compilation and execution process is planned.