-
-
-
-
- | Extension Name |
- Linux |
- macOS |
- FreeBSD |
- Windows |
-
-
-
-
- | {{ item.name }} |
-
- {{ item.name }}
- |
- {{ item.linux }} |
- {{ item.macos }} |
- {{ item.freebsd }} |
- {{ item.windows }} |
-
-
-
-
- No result, please try another keyword.
+
+
WARNING
+
Extension list is not generated yet. Run bin/spc dev:gen-ext-docs to generate it.
+
+
+
+
+
+ | Extension Name |
+ Linux |
+ macOS |
+ Windows |
+ Website |
+
+
+
+
+ |
+ {{ item.name }}
+ {{ item.name }}
+ |
+ {{ item.linux ? '✅' : '' }} |
+ {{ item.macos ? '✅' : '' }} |
+ {{ item.windows ? '✅' : '' }} |
+
+
+
+
+ |
+
+
+
+
+ No result, please try another keyword.
+
+
@@ -41,34 +51,22 @@ export default {
@@ -76,4 +74,14 @@ const doFilter = () => {
.searchinput {
border: 1px solid var(--vp-c-divider);
}
-
\ No newline at end of file
+.ext-source-link {
+ color: var(--vp-c-text-3);
+ vertical-align: middle;
+ opacity: 0.6;
+ transition: opacity 0.2s;
+}
+.ext-source-link:hover {
+ opacity: 1;
+ color: var(--vp-c-brand-1);
+}
+
diff --git a/docs/.vitepress/config.ts b/docs/.vitepress/config.ts
index 8ddc9c1f2..df95955d1 100644
--- a/docs/.vitepress/config.ts
+++ b/docs/.vitepress/config.ts
@@ -1,65 +1,84 @@
import sidebarEn from "./sidebar.en";
import sidebarZh from "./sidebar.zh";
-
// https://vitepress.dev/reference/site-config
export default {
- title: "Static PHP",
- description: "Build single static PHP binary, with PHP project together, with popular extensions included.",
+ title: "StaticPHP",
+ description: "A powerful tool designed for building portable executables including PHP, extensions, and more.",
locales: {
en: {
label: 'English',
lang: 'en',
themeConfig: {
nav: [
- {text: 'Guide', link: '/en/guide/',},
- {text: 'Advanced', link: '/en/develop/'},
- {text: 'Contributing', link: '/en/contributing/'},
- {text: 'FAQ', link: '/en/faq/'},
+ { text: 'Guide', link: '/en/guide/' },
+ { text: 'Develop', link: '/en/develop/' },
+ { text: 'Contributing', link: '/en/contributing/' },
+ { text: 'FAQ', link: '/en/faq/' },
+ {
+ text: 'v3 (alpha)',
+ items: [
+ { text: 'v3 (alpha)', link: '/en/' },
+ { text: 'v2', link: 'https://static-php.github.io/v2-docs/' },
+ ],
+ },
],
sidebar: sidebarEn,
footer: {
message: 'Released under the MIT License.',
- copyright: 'Copyright © 2023-present crazywhalecc'
- }
+ copyright: 'Copyright © 2023-present crazywhalecc',
+ },
},
},
zh: {
label: '简体中文',
- lang: 'zh', // optional, will be added as `lang` attribute on `html` tag
+ lang: 'zh',
themeConfig: {
nav: [
- {text: '构建指南', link: '/zh/guide/'},
- {text: '进阶', link: '/zh/develop/'},
- {text: '贡献', link: '/zh/contributing/'},
- {text: 'FAQ', link: '/zh/faq/'},
+ { text: '构建指南', link: '/zh/guide/' },
+ { text: '开发者', link: '/zh/develop/' },
+ { text: '贡献', link: '/zh/contributing/' },
+ { text: 'FAQ', link: '/zh/faq/' },
+ {
+ text: 'v3 (alpha)',
+ items: [
+ { text: 'v3 (alpha)', link: '/zh/' },
+ { text: 'v2', link: 'https://static-php.github.io/v2-docs/' },
+ ],
+ },
],
sidebar: sidebarZh,
footer: {
message: 'Released under the MIT License.',
- copyright: 'Copyright © 2023-present crazywhalecc'
- }
+ copyright: 'Copyright © 2023-present crazywhalecc',
+ },
},
- }
+ },
},
themeConfig: {
- // https://vitepress.dev/reference/default-theme-config
logo: '/images/static-php_nobg.png',
nav: [],
socialLinks: [
- {icon: 'github', link: 'https://github.com/crazywhalecc/static-php-cli'}
+ { icon: 'github', link: 'https://github.com/crazywhalecc/static-php-cli' },
],
footer: {
message: 'Released under the MIT License.',
- copyright: 'Copyright © 2023-present crazywhalecc'
+ copyright: 'Copyright © 2023-present crazywhalecc',
},
+ externalLinkIcon: true,
search: {
provider: 'algolia',
options: {
appId: 'IHJHUB1SF1',
apiKey: '8266d31cc2ffbd0e059f1c6e5bdaf8fc',
indexName: 'static-php docs',
+ askAi: {
+ assistantId: 'b72369b2-60a5-461d-902c-5c18d8c05902',
+ agentStudio: true,
+ sidePanel: true,
+ },
},
},
- }
+ },
}
+
diff --git a/docs/.vitepress/deps-map.data.js b/docs/.vitepress/deps-map.data.js
new file mode 100644
index 000000000..1a26aab7e
--- /dev/null
+++ b/docs/.vitepress/deps-map.data.js
@@ -0,0 +1,23 @@
+import { readFileSync, existsSync } from 'node:fs'
+import { resolve, dirname } from 'node:path'
+import { fileURLToPath } from 'node:url'
+
+const __dirname = dirname(fileURLToPath(import.meta.url))
+const DATA_PATH = resolve(__dirname, 'deps-data.json')
+
+export default {
+ watch: [DATA_PATH],
+
+ load() {
+ if (!existsSync(DATA_PATH)) {
+ console.warn(
+ '[deps-map.data.js] deps-data.json not found. ' +
+ 'Run `bin/spc dev:gen-deps-data` to generate it.'
+ )
+ return { packages: {}, missing: true }
+ }
+
+ const raw = JSON.parse(readFileSync(DATA_PATH, 'utf-8'))
+ return { packages: raw.packages ?? {}, missing: false }
+ },
+}
diff --git a/docs/.vitepress/extensions.data.js b/docs/.vitepress/extensions.data.js
new file mode 100644
index 000000000..22d1ae3aa
--- /dev/null
+++ b/docs/.vitepress/extensions.data.js
@@ -0,0 +1,40 @@
+import { readFileSync, existsSync } from 'node:fs'
+import { resolve, dirname } from 'node:path'
+import { fileURLToPath } from 'node:url'
+
+const __dirname = dirname(fileURLToPath(import.meta.url))
+const DATA_PATH = resolve(__dirname, 'ext-data.json')
+const NOTES_PATH = resolve(__dirname, '../en/guide/extension-notes.md')
+
+export default {
+ watch: [DATA_PATH, NOTES_PATH],
+
+ load() {
+ if (!existsSync(DATA_PATH)) {
+ console.warn(
+ '[extensions.data.js] ext-data.json not found. ' +
+ 'Run `bin/spc dev:gen-ext-docs` to generate it.'
+ )
+ return { extensions: [], missing: true }
+ }
+
+ const raw = JSON.parse(readFileSync(DATA_PATH, 'utf-8'))
+
+ // Build the set of extension names that have a section in extension-notes.md.
+ // Headings at level 2 or 3 are matched; leading/trailing whitespace is stripped.
+ const notesSet = new Set()
+ if (existsSync(NOTES_PATH)) {
+ const notesContent = readFileSync(NOTES_PATH, 'utf-8')
+ for (const match of notesContent.matchAll(/^#{2,3}\s+(\S+)/gm)) {
+ notesSet.add(match[1].toLowerCase())
+ }
+ }
+
+ const extensions = raw.extensions.map(ext => ({
+ ...ext,
+ hasNotes: notesSet.has(ext.name.toLowerCase()),
+ }))
+
+ return { extensions, missing: false }
+ },
+}
diff --git a/docs/.vitepress/gen-meta.js b/docs/.vitepress/gen-meta.js
new file mode 100644
index 000000000..e2d305853
--- /dev/null
+++ b/docs/.vitepress/gen-meta.js
@@ -0,0 +1,118 @@
+#!/usr/bin/env node
+/**
+ * docs:gen-meta — Pre-build metadata generator for VitePress docs.
+ *
+ * Checks that the environment is ready (PHP installed, composer dependencies
+ * present, bin/spc executable), then runs:
+ * bin/spc dev:gen-deps-data → docs/.vitepress/deps-data.json
+ * bin/spc dev:gen-ext-docs → docs/.vitepress/ext-data.json
+ */
+
+'use strict'
+
+const { execSync, spawnSync } = require('child_process')
+const fs = require('fs')
+const path = require('path')
+
+// __dirname is docs/.vitepress/, so two levels up is the project root
+const ROOT = path.resolve(__dirname, '../..')
+
+function fail(msg) {
+ console.error(`\x1b[31m[gen-meta] ERROR: ${msg}\x1b[0m`)
+ process.exit(1)
+}
+
+function info(msg) {
+ console.log(`\x1b[36m[gen-meta] ${msg}\x1b[0m`)
+}
+
+function ok(msg) {
+ console.log(`\x1b[32m[gen-meta] ${msg}\x1b[0m`)
+}
+
+// --- 1. Check PHP ------------------------------------------------------------
+info('Checking PHP installation...')
+const phpResult = spawnSync('php', ['--version'], { encoding: 'utf8' })
+if (phpResult.status !== 0 || phpResult.error) {
+ fail(
+ 'PHP is not installed or not in PATH.\n' +
+ ' Please install PHP 8.1+ and ensure it is available in your PATH.'
+ )
+}
+const phpVersion = phpResult.stdout.split('\n')[0].trim()
+ok(`Found: ${phpVersion}`)
+
+// --- 2. Check composer CLI ---------------------------------------------------
+info('Checking composer...')
+const composerCheck = spawnSync('composer', ['--version'], { encoding: 'utf8' })
+if (composerCheck.status !== 0 || composerCheck.error) {
+ fail(
+ 'composer is not installed or not in PATH.\n' +
+ ' Please install Composer: https://getcomposer.org/download/'
+ )
+}
+ok(`Found: ${composerCheck.stdout.split('\n')[0].trim()}`)
+
+// --- 3. Install composer dependencies if missing ----------------------------
+info('Checking composer dependencies...')
+const autoload = path.join(ROOT, 'vendor', 'autoload.php')
+if (!fs.existsSync(autoload)) {
+ info('vendor/autoload.php not found — running composer install --no-dev ...')
+ const installResult = spawnSync('composer', ['install', '--no-dev'], {
+ cwd: ROOT,
+ stdio: 'inherit',
+ })
+ if (installResult.status !== 0) {
+ fail('composer install --no-dev failed (exit code ' + installResult.status + ').')
+ }
+ ok('Composer dependencies installed.')
+} else {
+ ok('Composer vendor directory found.')
+}
+
+// --- 4. Check bin/spc --------------------------------------------------------
+info('Checking bin/spc...')
+const spc = path.join(ROOT, 'bin', 'spc')
+if (!fs.existsSync(spc)) {
+ fail('bin/spc not found. Make sure you are in the project root.')
+}
+// Quick sanity check — list commands
+const spcCheck = spawnSync('php', [spc, 'list', '--format=txt'], {
+ cwd: ROOT,
+ encoding: 'utf8',
+ env: { ...process.env, SPC_EXECUTION_SOURCE: '1' },
+})
+if (spcCheck.status !== 0) {
+ fail(
+ 'bin/spc failed to run.\n' +
+ (spcCheck.stderr ?? '') +
+ '\n Make sure PHP extensions required by static-php-cli are available.'
+ )
+}
+ok('bin/spc is operational.')
+
+// --- 5. Run dev:gen-deps-data ------------------------------------------------
+info('Running bin/spc dev:gen-deps-data ...')
+const depsResult = spawnSync('php', [spc, 'dev:gen-deps-data'], {
+ cwd: ROOT,
+ stdio: 'inherit',
+ env: { ...process.env, SPC_EXECUTION_SOURCE: '1' },
+})
+if (depsResult.status !== 0) {
+ fail('dev:gen-deps-data failed (exit code ' + depsResult.status + ').')
+}
+ok('deps-data.json generated.')
+
+// --- 6. Run dev:gen-ext-docs -------------------------------------------------
+info('Running bin/spc dev:gen-ext-docs ...')
+const extResult = spawnSync('php', [spc, 'dev:gen-ext-docs'], {
+ cwd: ROOT,
+ stdio: 'inherit',
+ env: { ...process.env, SPC_EXECUTION_SOURCE: '1' },
+})
+if (extResult.status !== 0) {
+ fail('dev:gen-ext-docs failed (exit code ' + extResult.status + ').')
+}
+ok('ext-data.json generated.')
+
+ok('Metadata generation complete. Proceeding to VitePress build...')
diff --git a/docs/.vitepress/sidebar.en.ts b/docs/.vitepress/sidebar.en.ts
index 54bcb0e1a..0ec00d052 100644
--- a/docs/.vitepress/sidebar.en.ts
+++ b/docs/.vitepress/sidebar.en.ts
@@ -1,57 +1,83 @@
export default {
- '/en/guide/': [
- {
- text: 'Basic Build Guides',
- items: [
- {text: 'Guide', link: '/en/guide/'},
- {text: 'Build (Local)', link: '/en/guide/manual-build'},
- {text: 'Build (CI)', link: '/en/guide/action-build'},
- {text: 'Supported Extensions', link: '/en/guide/extensions'},
- {text: 'Extension Notes', link: '/en/guide/extension-notes'},
- {text: 'Build Command Generator', link: '/en/guide/cli-generator'},
- {text: 'Environment Variables', link: '/en/guide/env-vars', collapsed: true,},
- {text: 'Dependency Table', link: '/en/guide/deps-map'},
- ]
- },
- {
- text: 'Extended Build Guides',
- items: [
- {text: 'Troubleshooting', link: '/en/guide/troubleshooting'},
- {text: 'Build on Windows', link: '/en/guide/build-on-windows'},
- {text: 'Build with GNU libc', link: '/en/guide/build-with-glibc'},
- ],
- }
- ],
- '/en/develop/': [
- {
- text: 'Development',
- items: [
- {text: 'Get Started', link: '/en/develop/'},
- {text: 'Project Structure', link: '/en/develop/structure'},
- {text: 'PHP Source Modification', link: '/en/develop/php-src-changes'},
- ],
- },
- {
- text: 'Module',
- items: [
- {text: 'Doctor ', link: '/en/develop/doctor-module'},
- {text: 'Source', link: '/en/develop/source-module'},
- ]
- },
- {
- text: 'Extra',
- items: [
- {text: 'Compilation Tools', link: '/en/develop/system-build-tools'},
- {text: 'craft.yml Configuration', link: '/zh/develop/craft-yml'},
- ]
- }
- ],
- '/en/contributing/': [
- {
- text: 'Contributing',
- items: [
- {text: 'Contributing', link: '/en/contributing/'},
- ],
- }
- ],
+ '/en/guide/': [
+ {
+ text: 'Getting Started',
+ items: [
+ { text: 'Overview', link: '/en/guide/' },
+ { text: 'Installation', link: '/en/guide/installation' },
+ { text: 'First Build', link: '/en/guide/first-build' },
+ { text: 'PHP SAPI Reference', link: '/en/guide/sapi-reference' },
+ { text: 'CLI Reference', link: '/en/guide/cli-reference' },
+ ],
+ },
+ {
+ text: 'Extensions',
+ items: [
+ { text: 'Supported Extensions', link: '/en/guide/extensions' },
+ { text: 'Extension Notes', link: '/en/guide/extension-notes' },
+ { text: 'Build Command Generator', link: '/en/guide/cli-generator' },
+ ],
+ },
+ {
+ text: 'Reference',
+ items: [
+ { text: 'Environment Variables', link: '/en/guide/env-vars' },
+ { text: 'Dependency Table', link: '/en/guide/deps-map' },
+ { text: 'Troubleshooting', link: '/en/guide/troubleshooting' },
+ ],
+ },
+ ],
+ '/en/develop/': [
+ {
+ text: 'Developer Guide',
+ items: [
+ { text: 'Get Started', link: '/en/develop/' },
+ { text: 'Project Structure', link: '/en/develop/structure' },
+ { text: 'PHP Source Modifications', link: '/en/develop/php-src-changes' },
+ ],
+ },
+ {
+ text: 'Concepts',
+ items: [
+ { text: 'Package Model', link: '/en/develop/package-model' },
+ { text: 'Registry & Plugin System', link: '/en/develop/registry' },
+ { text: 'Build Lifecycle', link: '/en/develop/build-lifecycle' },
+ ],
+ },
+ {
+ text: 'Modules',
+ items: [
+ { text: 'Doctor', link: '/en/develop/doctor-module' },
+ { text: 'Source', link: '/en/develop/source-module' },
+ { text: 'craft.yml', link: '/en/develop/craft-yml' },
+ { text: 'Compilation Tools', link: '/en/develop/system-build-tools' },
+ ],
+ },
+ {
+ text: 'Vendor Mode',
+ items: [
+ { text: 'Introduction', link: '/en/develop/vendor-mode/' },
+ { text: 'Writing Package Classes', link: '/en/develop/vendor-mode/package-classes' },
+ { text: 'Annotations Reference', link: '/en/develop/vendor-mode/annotations' },
+ { text: 'Dependency Injection', link: '/en/develop/vendor-mode/dependency-injection' },
+ { text: 'Lifecycle Hooks', link: '/en/develop/vendor-mode/lifecycle-hooks' },
+ ],
+ },
+ ],
+ '/en/contributing/': [
+ {
+ text: 'Contributing',
+ items: [
+ { text: 'Contributing Guide', link: '/en/contributing/' },
+ ],
+ },
+ ],
+ '/en/faq/': [
+ {
+ text: 'FAQ',
+ items: [
+ { text: 'Frequently Asked Questions', link: '/en/faq/' },
+ ],
+ },
+ ],
};
diff --git a/docs/.vitepress/sidebar.zh.ts b/docs/.vitepress/sidebar.zh.ts
index 63592b93b..8c84f6457 100644
--- a/docs/.vitepress/sidebar.zh.ts
+++ b/docs/.vitepress/sidebar.zh.ts
@@ -1,57 +1,83 @@
export default {
- '/zh/guide/': [
- {
- text: '构建指南',
- items: [
- {text: '指南', link: '/zh/guide/'},
- {text: '本地构建', link: '/zh/guide/manual-build'},
- {text: 'Actions 构建', link: '/zh/guide/action-build'},
- {text: '扩展列表', link: '/zh/guide/extensions'},
- {text: '扩展注意事项', link: '/zh/guide/extension-notes'},
- {text: '编译命令生成器', link: '/zh/guide/cli-generator'},
- {text: '环境变量列表', link: '/zh/guide/env-vars'},
- {text: '依赖关系图表', link: '/zh/guide/deps-map'},
- ]
- },
- {
- text: '扩展构建指南',
- items: [
- {text: '故障排除', link: '/zh/guide/troubleshooting'},
- {text: '在 Windows 上构建', link: '/zh/guide/build-on-windows'},
- {text: '构建 GNU libc 兼容的二进制', link: '/zh/guide/build-with-glibc'},
- ],
- }
- ],
- '/zh/develop/': [
- {
- text: '开发指南',
- items: [
- {text: '开发简介', link: '/zh/develop/'},
- {text: '项目结构简介', link: '/zh/develop/structure'},
- {text: '对 PHP 源码的修改', link: '/zh/develop/php-src-changes'},
- ],
- },
- {
- text: '模块',
- items: [
- {text: 'Doctor 环境检查工具', link: '/zh/develop/doctor-module'},
- {text: '资源模块', link: '/zh/develop/source-module'},
- ]
- },
- {
- text: '其他',
- items: [
- {text: '系统编译工具', link: '/zh/develop/system-build-tools'},
- {text: 'craft.yml 配置详解', link: '/zh/develop/craft-yml'},
- ]
- }
- ],
- '/zh/contributing/': [
- {
- text: '贡献指南',
- items: [
- {text: '贡献指南', link: '/zh/contributing/'},
- ],
- }
- ],
+ '/zh/guide/': [
+ {
+ text: '快速上手',
+ items: [
+ { text: '概览', link: '/zh/guide/' },
+ { text: '安装', link: '/zh/guide/installation' },
+ { text: '第一次构建', link: '/zh/guide/first-build' },
+ { text: 'PHP SAPI 构建参考', link: '/zh/guide/sapi-reference' },
+ { text: '命令行参考', link: '/zh/guide/cli-reference' },
+ ],
+ },
+ {
+ text: '扩展',
+ items: [
+ { text: '支持的扩展列表', link: '/zh/guide/extensions' },
+ { text: '扩展注意事项', link: '/zh/guide/extension-notes' },
+ { text: '命令生成器', link: '/zh/guide/cli-generator' },
+ ],
+ },
+ {
+ text: '参考',
+ items: [
+ { text: '环境变量', link: '/zh/guide/env-vars' },
+ { text: '依赖关系图', link: '/zh/guide/deps-map' },
+ { text: '故障排除', link: '/zh/guide/troubleshooting' },
+ ],
+ },
+ ],
+ '/zh/develop/': [
+ {
+ text: '开发者指南',
+ items: [
+ { text: '开发简介', link: '/zh/develop/' },
+ { text: '项目结构', link: '/zh/develop/structure' },
+ { text: '对 PHP 源码的修改', link: '/zh/develop/php-src-changes' },
+ ],
+ },
+ {
+ text: '核心概念',
+ items: [
+ { text: 'Package 模型', link: '/zh/develop/package-model' },
+ { text: 'Registry 与插件系统', link: '/zh/develop/registry' },
+ { text: '构建生命周期', link: '/zh/develop/build-lifecycle' },
+ ],
+ },
+ {
+ text: '模块',
+ items: [
+ { text: 'Doctor 环境检查', link: '/zh/develop/doctor-module' },
+ { text: '资源模块', link: '/zh/develop/source-module' },
+ { text: 'craft.yml 配置', link: '/zh/develop/craft-yml' },
+ { text: '编译工具', link: '/zh/develop/system-build-tools' },
+ ],
+ },
+ {
+ text: 'Vendor 模式',
+ items: [
+ { text: '简介', link: '/zh/develop/vendor-mode/' },
+ { text: '编写 Package 类', link: '/zh/develop/vendor-mode/package-classes' },
+ { text: '注解参考', link: '/zh/develop/vendor-mode/annotations' },
+ { text: '依赖注入', link: '/zh/develop/vendor-mode/dependency-injection' },
+ { text: '生命周期 Hook', link: '/zh/develop/vendor-mode/lifecycle-hooks' },
+ ],
+ },
+ ],
+ '/zh/contributing/': [
+ {
+ text: '贡献指南',
+ items: [
+ { text: '贡献指南', link: '/zh/contributing/' },
+ ],
+ },
+ ],
+ '/zh/faq/': [
+ {
+ text: 'FAQ',
+ items: [
+ { text: '常见问题', link: '/zh/faq/' },
+ ],
+ },
+ ],
};
diff --git a/docs/.vitepress/theme/index.ts b/docs/.vitepress/theme/index.ts
index 06771bcf5..d8a454234 100644
--- a/docs/.vitepress/theme/index.ts
+++ b/docs/.vitepress/theme/index.ts
@@ -3,9 +3,13 @@ import DefaultTheme from 'vitepress/theme'
import {inBrowser, useData} from "vitepress";
import {watchEffect} from "vue";
import './style.css';
+import DepsMap from '../components/DepsMap.vue';
export default {
...DefaultTheme,
+ enhanceApp({ app }) {
+ app.component('DepsMap', DepsMap)
+ },
setup() {
const { lang } = useData()
watchEffect(() => {
diff --git a/docs/deps-craft-yml.md b/docs/deps-craft-yml.md
deleted file mode 100644
index 0ee0e11d0..000000000
--- a/docs/deps-craft-yml.md
+++ /dev/null
@@ -1,70 +0,0 @@
-```yaml
-# PHP version to build (default: 8.4)
-php-version: 8.4
-# [REQUIRED] Static PHP extensions to build (list or comma-separated are both accepted)
-extensions: bcmath,fileinfo,phar,zlib,sodium,posix,pcntl
-# Extra libraries to build (list or comma-separated are both accepted)
-libs: [ ]
-# [REQUIRED] Build SAPIs (list or comma-separated are both accepted)
-sapi: cli,micro,fpm
-# Show full console output (default: false)
-debug: false
-# Build options (same as `build` command options, all options are optional)
-build-options:
- # Before build, remove all old build files and sources (default: false)
- with-clean: false
- # Build with all suggested libraries (default: false)
- with-suggested-libs: false
- # Build with all suggested extensions (default: false)
- with-suggested-exts: false
- # Build extra shared extensions (list or comma-separated are both accepted)
- build-shared: [ ]
- # Build without stripping the binary (default: false)
- no-strip: false
- # Disable Opcache JIT (default: false)
- disable-opcache-jit: false
- # PHP configuration options (same as --with-config-file-path)
- with-config-file-path: ""
- # PHP configuration options (same as --with-config-file-scan-dir)
- with-config-file-scan-dir: ""
- # Hardcoded INI options for cli and micro SAPI (e.g. "memory_limit=4G", list accepted)
- with-hardcoded-ini: [ ]
- # Pretend micro SAPI as cli SAPI to avoid some frameworks to limit the usage of micro SAPI
- with-micro-fake-cli: false
- # Additional patch point injection files (e.g. "path/to/patch.php", list accepted)
- with-added-patch: [ ]
- # Ignore micro extension tests (if you are using micro SAPI, default: false)
- without-micro-ext-test: false
- # UPX pack the binary (default: false)
- with-upx-pack: false
- # Set the micro.exe program icon (only for Windows, default: "")
- with-micro-logo: ""
- # Set micro SAPI as win32 mode, without this, micro SAPI will be compiled as a console application (only for Windows, default: false)
- enable-micro-win32: false
-
-# Build options for shared extensions (list or comma-separated are both accepted)
-shared-extensions: [ ]
-
-# Download options
-download-options:
- # Use custom url for specified sources, format: "{source-name}:{url}" (e.g. "php-src:https://example.com/php-8.4.0.tar.gz")
- custom-url: [ ]
- # Use custom git repo for specified sources, format: "{source-name}:{branch}:{url}" (e.g. "php-src:master:https://github.com/php/php-src.git")
- custom-git: [ ]
- # Retries count for downloading sources (default: 5)
- retry: 5
- # Use pre-built libraries if available (default: false)
- prefer-pre-built: true
- # Do not download from alternative sources (default: false)
- no-alt: false
-
-craft-options:
- doctor: true
- download: true
- build: true
-
-# Extra environment variables
-extra-env:
- # e.g. Use github token to avoid rate limit
- GITHUB_TOKEN: your-github-token
-```
diff --git a/docs/en/contributing/index.md b/docs/en/contributing/index.md
index 6dc5ecf55..5438cc30c 100644
--- a/docs/en/contributing/index.md
+++ b/docs/en/contributing/index.md
@@ -1,63 +1,5 @@
# Contributing
-Thank you for being here, this project welcomes your contributions!
-
-## Contribution Guide
-
-If you have code or documentation to contribute, here's what you need to know first.
-
-1. What type of code are you contributing? (new extensions, bug fixes, security issues, project framework optimizations, documentation)
-2. If you contribute new files or new snippets, is your code checked by `php-cs-fixer` and `phpstan`?
-3. Have you fully read the [Developer Guide](../develop/) before contributing code?
-
-If you can answer the above questions and have made changes to the code,
-you can initiate a Pull Request in the project GitHub repository in time.
-After the code review is completed, the code can be modified according to the suggestion, or directly merged into the main branch.
-
-## Contribution Type
-
-The main purpose of this project is to compile statically linked PHP binaries,
-and the command line processing function is written based on `symfony/console`.
-Before development, if you are not familiar with it,
-Check out the [symfony/console documentation](https://symfony.com/doc/current/components/console.html) first.
-
-### Security Update
-
-Because this project is basically a PHP project running locally, generally speaking, there will be no remote attacks.
-But if you find such a problem, please **DO NOT submit a PR or Issue in the GitHub repository,
-You need to contact the project maintainer (crazywhalecc) via [mail](mailto:admin@zhamao.me).
-
-### Fix Bugs
-
-Fixing bugs generally does not involve modification of the project structure and framework,
-so if you can locate the wrong code and fix it directly, please submit a PR directly.
-
-### New Extensions
-
-For adding a new extension,
-you need to understand some basic structure of the project and how to add a new extension according to the existing logic.
-It will be covered in detail in the next section on this page.
-In general, you will need:
-
-1. Evaluate whether the extension can be compiled inline into PHP.
-2. Evaluate whether the extension's dependent libraries (if any) can be compiled statically.
-3. Write library compile commands on different platforms.
-4. Verify that the extension and its dependencies are compatible with existing extensions and dependencies.
-5. Verify that the extension works normally in `cli`, `micro`, `fpm`, `embed` SAPIs.
-6. Write documentation and add your extension.
-
-### Project Framework Optimization
-
-If you are already familiar with the working principle of `symfony/console`,
-and at the same time want to make some modifications or optimizations to the framework of the project,
-please understand the following things first:
-
-1. Adding extensions does not belong to project framework optimization,
-but if you find that you have to optimize the framework when adding new extensions,
-you need to modify the framework itself before adding extensions.
-2. For some large-scale logical modifications (such as those involving LibraryBase, Extension objects, etc.),
-it is recommended to submit an Issue or Draft PR for discussion first.
-3. In the early stage of the project, it was a pure private development project, and there were some Chinese comments in the code.
-After internationalizing your project you can submit a PR to translate these comments into English.
-4. Please do not submit more useless code fragments in the code,
-such as a large number of unused variables, methods, classes, and code that has been rewritten many times.
+
diff --git a/docs/en/develop/build-lifecycle.md b/docs/en/develop/build-lifecycle.md
new file mode 100644
index 000000000..f80e402fd
--- /dev/null
+++ b/docs/en/develop/build-lifecycle.md
@@ -0,0 +1,6 @@
+# Build Lifecycle
+
+
diff --git a/docs/en/develop/craft-yml.md b/docs/en/develop/craft-yml.md
index e0aea228f..10f8be47d 100644
--- a/docs/en/develop/craft-yml.md
+++ b/docs/en/develop/craft-yml.md
@@ -4,4 +4,4 @@ aside: false
# craft.yml Configuration
-
+
diff --git a/docs/en/develop/doctor-module.md b/docs/en/develop/doctor-module.md
index 64aed4afc..3bd284297 100644
--- a/docs/en/develop/doctor-module.md
+++ b/docs/en/develop/doctor-module.md
@@ -1,70 +1,4 @@
-# Doctor module
+# Doctor Module
-The Doctor module is a relatively independent module used to check the system environment, which can be entered with the command `bin/spc doctor`, and the entry command class is in `DoctorCommand.php`.
-
-The Doctor module is a checklist with a series of check items and automatic repair items.
-These items are stored in the `src/SPC/doctor/item/` directory,
-And two Attributes are used as check item tags and auto-fix item tags: `#[AsCheckItem]` and `#[AsFixItem]`.
-
-Take the existing check item `if necessary tools are installed`,
-which is used to check whether the packages necessary for compilation are installed in the macOS system.
-The following is its source code:
-
-```php
-use SPC\doctor\AsCheckItem;
-use SPC\doctor\AsFixItem;
-use SPC\doctor\CheckResult;
-
-#[AsCheckItem('if necessary tools are installed', limit_os: 'Darwin', level: 997)]
-public function checkCliTools(): ?CheckResult
-{
- $missing = [];
- foreach (self::REQUIRED_COMMANDS as $cmd) {
- if ($this->findCommand($cmd) === null) {
- $missing[] = $cmd;
- }
- }
- if (!empty($missing)) {
- return CheckResult::fail('missing system commands: ' . implode(', ', $missing), 'build-tools', [$missing]);
- }
- return CheckResult::ok();
-}
-```
-
-The first parameter of the attribute is the name of the check item,
-and the following `limit_os` parameter restricts the check item to be triggered only under the specified system,
-and `level` is the priority of executing the check item, the larger the number, the higher the priority higher.
-
-The `$this->findCommand()` method used in it is the method of `SPC\builder\traits\UnixSystemUtilTrait`,
-the purpose is to find the location of the system command, and return NULL if it cannot be found.
-
-Each check item method should return a `SPC\doctor\CheckResult`:
-
-- When returning `CheckResult::fail()`, the first parameter is used to output the error prompt of the terminal,
- and the second parameter is the name of the repair item when this check item can be automatically repaired.
-- When `CheckResult::ok()` is returned, the check passed. You can also pass a parameter to return the check result, for example: `CheckResult::ok('OS supported')`.
-- When returning `CheckResult::fail()`, if the third parameter is included, the array of the third parameter will be used as the parameter of `AsFixItem`.
-
-The following is the method for automatically repairing items corresponding to this check item:
-
-```php
-#[AsFixItem('build-tools')]
-public function fixBuildTools(array $missing): bool
-{
- foreach ($missing as $cmd) {
- try {
- shell(true)->exec('brew install ' . escapeshellarg($cmd));
- } catch (RuntimeException) {
- return false;
- }
- }
- return true;
-}
-```
-
-`#[AsFixItem()]` first parameter is the name of the fix item, and this method must return True or False.
-When False is returned, the automatic repair failed and manual handling is required.
-
-In the code here, `shell()->exec()` is the method of executing commands of the project,
-which is used to replace `exec()` and `system()`, and also provides debugging, obtaining execution status,
-entering directories, etc. characteristic.
+
diff --git a/docs/en/develop/index.md b/docs/en/develop/index.md
index 33e4163f5..717f4cd4c 100644
--- a/docs/en/develop/index.md
+++ b/docs/en/develop/index.md
@@ -1,35 +1,4 @@
# Start Developing
-Developing this project requires the installation and deployment of a PHP environment,
-as well as some extensions and Composer commonly used in PHP projects.
-
-The development environment and running environment of the project are almost exactly the same.
-You can refer to the **Manual Build** section to install system PHP or use the pre-built static PHP of this project as the environment.
-I will not go into details here.
-
-Regardless of its purpose, this project itself is actually a `php-cli` program. You can edit and develop it as a normal PHP project.
-At the same time, you need to understand the Shell languages of different systems.
-
-The current purpose of this project is to compile statically compiled independent PHP,
-but the main part also includes compiling static versions of many dependent libraries,
-so you can reuse this set of compilation logic to build independent binary versions of other programs, such as Nginx, etc.
-
-## Environment preparation
-
-A PHP environment is required to develop this project. You can use the PHP that comes with the system,
-or you can use the static PHP built by this project.
-
-Regardless of which PHP you use, in your development environment you need to install these extensions:
-
-```
-curl,dom,filter,mbstring,openssl,pcntl,phar,posix,sodium,tokenizer,xml,xmlwriter
-```
-
-The static-php-cli project itself does not require so many extensions, but during the development process,
-you will use tools such as Composer and PHPUnit, which require these extensions.
-
-> For micro self-executing binaries built by static-php-cli itself, only `pcntl,posix,mbstring,tokenizer,phar` is required.
-
-## Start development
-
-Continuing down to see the project structure documentation, you can learn how `static-php-cli` works.
+
diff --git a/docs/en/develop/package-model.md b/docs/en/develop/package-model.md
new file mode 100644
index 000000000..654153659
--- /dev/null
+++ b/docs/en/develop/package-model.md
@@ -0,0 +1,6 @@
+# Package Model
+
+
diff --git a/docs/en/develop/php-src-changes.md b/docs/en/develop/php-src-changes.md
index 190702594..bb150ee87 100644
--- a/docs/en/develop/php-src-changes.md
+++ b/docs/en/develop/php-src-changes.md
@@ -1,59 +1,4 @@
-# Modifications to PHP source code
+# PHP Source Modifications
-During the static compilation process, static-php-cli made some modifications to the PHP source code
-in order to achieve good compatibility, performance, and security.
-The following is a description of the current modifications to the PHP source code.
-
-## Micro related patches
-
-Based on the patches provided by the phpmicro project,
-static-php-cli has made some modifications to the PHP source code to meet the needs of static compilation.
-The patches currently used by static-php-cli during compilation in the [patch list](https://github.com/easysoft/phpmicro/tree/master/patches) are:
-
-- static_opcache
-- static_extensions_win32
-- cli_checks
-- disable_huge_page
-- vcruntime140
-- win32
-- zend_stream
-- cli_static
-- macos_iconv
-- phar
-
-## PHP <= 8.1 libxml patch
-
-Because PHP only provides security updates for 8.1 and stops updating older versions,
-static-php-cli applies the libxml compilation patch that has been applied in newer versions of PHP to PHP 8.1 and below.
-
-## gd extension Windows patch
-
-Compiling the gd extension under Windows requires major changes to the `config.w32` file.
-static-php-cli has made some changes to the gd extension to make it easier to compile under Windows.
-
-## YAML extension Windows patch
-
-YAML extension needs to modify the `config.w32` file to compile under Windows.
-static-php-cli has made some modifications to the YAML extension to make it easier to compile under Windows.
-
-## static-php-cli version information insertion
-
-When compiling, static-php-cli will insert the static-php-cli version information into the PHP version information for easy identification.
-
-## Add option to hardcode INI
-
-When using the `-I` parameter to hardcode INI into static PHP functionality,
-static-php-cli will modify the PHP source code to insert the hardcoded content.
-
-## Linux system repair patch
-
-Some compilation environments may lack some system header files or libraries.
-static-php-cli will automatically fix these problems during compilation, such as:
-
-- HAVE_STRLCAT missing problem
-- HAVE_STRLCPY missing problem
-
-## Fiber issue fix patch for Windows
-
-When compiling PHP on Windows, there will be some issues with the Fiber extension.
-static-php-cli will automatically fix these issues during compilation (modify `config.w32` in php-src).
+
diff --git a/docs/en/develop/registry.md b/docs/en/develop/registry.md
new file mode 100644
index 000000000..e21b5aa5b
--- /dev/null
+++ b/docs/en/develop/registry.md
@@ -0,0 +1,6 @@
+# Registry & Plugin System
+
+
diff --git a/docs/en/develop/source-module.md b/docs/en/develop/source-module.md
index 51c3ba3ca..f2825f329 100644
--- a/docs/en/develop/source-module.md
+++ b/docs/en/develop/source-module.md
@@ -1,372 +1,5 @@
-# Source module
+# Source Module
-The download source module of static-php-cli is a major module.
-It includes dependent libraries, external extensions, PHP source code download methods and file decompression methods.
-The download configuration file mainly involves the `source.json` and `pkg.json` file, which records the download method of all downloadable sources.
-
-The main commands involved in the download function are `bin/spc download` and `bin/spc extract`.
-The `download` command is a downloader that downloads sources according to the configuration file,
-and the `extract` command is an extractor that extract sources from downloaded files.
-
-Generally speaking, downloading sources may be slow because these sources come from various official websites, GitHub,
-and other different locations.
-At the same time, they also occupy a large space, so you can download the sources once and reuse them.
-
-The configuration file of the downloader is `source.json`, which contains the download methods of all sources.
-You can add the source download methods you need, or modify the existing source download methods.
-
-The download configuration structure of each source is as follows.
-The following is the source download configuration corresponding to the `libevent` extension:
-
-```json
-{
- "libevent": {
- "type": "ghrel",
- "repo": "libevent/libevent",
- "match": "libevent.+\\.tar\\.gz",
- "provide-pre-built": true,
- "license": {
- "type": "file",
- "path": "LICENSE"
- }
- }
-}
-```
-
-The most important field here is `type`. Currently, the types it supports are:
-
-- `url`: Directly use URL to download, for example: `https://download.libsodium.org/libsodium/releases/libsodium-1.0.18.tar.gz`.
-- `pie`: Download PHP extensions from Packagist using the PIE (PHP Installer for Extensions) standard.
-- `ghrel`: Use the GitHub Release API to download, download the artifacts uploaded from the latest version released by maintainers.
-- `ghtar`: Use the GitHub Release API to download.
- Different from `ghrel`, `ghtar` is downloaded from the `source code (tar.gz)` in the latest Release of the project.
-- `ghtagtar`: Use GitHub Release API to download.
- Compared with `ghtar`, `ghtagtar` can find the latest one from the `tags` list and download the source code in `tar.gz` format
- (because some projects only use `tag` release version).
-- `bitbuckettag`: Download using BitBucket API, basically the same as `ghtagtar`, except this one applies to BitBucket.
-- `git`: Clone the project directly from a Git address to download sources, applicable to any public Git repository.
-- `filelist`: Use a crawler to crawl the Web download site that provides file index,
- and get the latest version of the file name and download it.
-- `custom`: If none of the above download methods are satisfactory, you can write `custom`,
- create a new class under `src/SPC/store/source/`, extends `CustomSourceBase`, and write the download script yourself.
-
-## source.json Common parameters
-
-Each source file in source.json has the following params:
-
-- `license`: the open source license of the source code, see **Open Source License** section below
-- `type`: must be one of the types mentioned above
-- `path` (optional): release the source code to the specified directory instead of `source/{name}`
-- `provide-pre-built` (optional): whether to provide precompiled binary files.
- If `true`, it will automatically try to download precompiled binary files when running `bin/spc download`
-
-::: tip
-The `path` parameter in `source.json` can specify a relative or absolute path. When specified as a relative path, the path is based on `source/`.
-:::
-
-## Download type - url
-
-URL type sources refer to downloading files directly from the URL.
-
-The parameters included are:
-
-- `url`: The download address of the file, such as `https://example.com/file.tgz`
-- `filename` (optional): The file name saved to the local area. If not specified, the file name of the url will be used.
-
-Example (download the imagick extension and extract it to the extension storage path of the php source code):
-
-```json
-{
- "ext-imagick": {
- "type": "url",
- "url": "https://pecl.php.net/get/imagick",
- "path": "php-src/ext/imagick",
- "filename": "imagick.tgz",
- "license": {
- "type": "file",
- "path": "LICENSE"
- }
- }
-}
-```
-
-## Download type - pie
-
-PIE (PHP Installer for Extensions) type sources refer to downloading PHP extensions from Packagist that follow the PIE standard.
-This method automatically fetches extension information from the Packagist repository and downloads the appropriate distribution file.
-
-The parameters included are:
-
-- `repo`: The Packagist vendor/package name, such as `vendor/package-name`
-
-Example (download a PHP extension from Packagist using PIE):
-
-```json
-{
- "ext-example": {
- "type": "pie",
- "repo": "vendor/example-extension",
- "path": "php-src/ext/example",
- "license": {
- "type": "file",
- "path": "LICENSE"
- }
- }
-}
-```
-
-::: tip
-The PIE download type will automatically detect the extension information from Packagist metadata,
-including the download URL, version, and distribution type.
-The extension must be marked as `type: php-ext` or contain `php-ext` metadata in its Packagist package definition.
-:::
-
-## Download type - ghrel
-
-ghrel will download files from Assets uploaded in GitHub Release.
-First use the GitHub Release API to get the latest version, and then download the corresponding files according to the regular matching method.
-
-The parameters included are:
-
-- `repo`: GitHub repository name
-- `match`: regular expression matching Assets files
-- `prefer-stable`: Whether to download stable versions first (default is `false`)
-
-Example (download the libsodium library, matching the libsodium-x.y.tar.gz file in Release):
-
-```json
-{
- "libsodium": {
- "type": "ghrel",
- "repo": "jedisct1/libsodium",
- "match": "libsodium-\\d+(\\.\\d+)*\\.tar\\.gz",
- "license": {
- "type": "file",
- "path": "LICENSE"
- }
- }
-}
-```
-
-## Download type - ghtar
-
-ghtar will download the file from the GitHub Release Tag.
-Unlike `ghrel`, `ghtar` will download the `source code (tar.gz)` from the latest Release of the project.
-
-The parameters included are:
-
-- `repo`: GitHub repository name
-- `prefer-stable`: Whether to download stable versions first (default is `false`)
-
-Example (brotli library):
-
-```json
-{
- "brotli": {
- "type": "ghtar",
- "repo": "google/brotli",
- "license": {
- "type": "file",
- "path": "LICENSE"
- }
- }
-}
-```
-
-## Download type - ghtagtar
-
-Use the GitHub Release API to download.
-Compared with `ghtar`, `ghtagtar` can find the latest one from the `tags` list and download the source code in `tar.gz` format
-(because some projects only use the `tag` version).
-
-The parameters included are:
-
-- `repo`: GitHub repository name
-- `prefer-stable`: Whether to download stable versions first (default is `false`)
-
-Example (gmp library):
-
-```json
-{
- "gmp": {
- "type": "ghtagtar",
- "repo": "alisw/GMP",
- "license": {
- "type": "text",
- "text": "EXAMPLE LICENSE"
- }
- }
-}
-```
-
-## Download Type - bitbuckettag
-
-Download using BitBucket API, basically the same as `ghtagtar`, except this one works with BitBucket.
-
-The parameters included are:
-
-- `repo`: BitBucket repository name
-
-## Download type - git
-
-Clone the project directly from a Git address to download sources, applicable to any public Git repository.
-
-The parameters included are:
-
-- `url`: Git link (HTTPS only)
-- `rev`: branch name
-
-```json
-{
- "imap": {
- "type": "git",
- "url": "https://github.com/static-php/imap.git",
- "rev": "master",
- "license": {
- "type": "file",
- "path": "LICENSE"
- }
- }
-}
-```
-
-## Download type - filelist
-
-Use a crawler to crawl a web download site that provides a file index and get the latest version of the file name and download it.
-
-Note that this method is only applicable to static sites with page index functions such as mirror sites and GNU official websites.
-
-The parameters included are:
-
-- `url`: The URL of the page to crawl the latest version of the file
-- `regex`: regular expression matching file names and download links
-
-Example (download the libiconv library from the GNU official website):
-
-```json
-{
- "libiconv": {
- "type": "filelist",
- "url": "https://ftp.gnu.org/gnu/libiconv/",
- "regex": "/href=\"(?
libiconv-(?[^\"]+)\\.tar\\.gz)\"/",
- "license": {
- "type": "file",
- "path": "COPYING"
- }
- }
-}
-```
-
-## Download type - custom
-
-If the above downloading methods are not satisfactory, you can write `custom`,
-create a new class under `src/SPC/store/source/`, extends `CustomSourceBase`, and write the download script yourself.
-
-I won’t go into details here, you can look at `src/SPC/store/source/PhpSource.php` or `src/SPC/store/source/PostgreSQLSource.php` as examples.
-
-## pkg.json General parameters
-
-pkg.json stores non-source-code files, such as precompiled tools musl-toolchain and UPX. It includes:
-
-- `type`: The same type as `source.json` and different kinds of parameters.
-- `extract` (optional): The path to decompress after downloading, the default is `pkgroot/{pkg_name}`.
-- `extract-files` (optional): Extract only the specified files to the specified location after downloading.
-
-It should be noted that `pkg.json` does not involve compilation, modification and distribution of source code,
-so there is no `license` open source license field.
-And you cannot use the `extract` and `extract-files` parameters at the same time.
-
-Example (download nasm locally and extract only program files to PHP SDK):
-
-```json
-{
- "nasm-x86_64-win": {
- "type": "url",
- "url": "https://www.nasm.us/pub/nasm/releasebuilds/2.16.01/win64/nasm-2.16.01-win64.zip",
- "extract-files": {
- "nasm-2.16.01/nasm.exe": "{php_sdk_path}/bin/nasm.exe",
- "nasm-2.16.01/ndisasm.exe": "{php_sdk_path}/bin/ndisasm.exe"
- }
- }
-}
-```
-
-The key name in `extract-files` is the file in the source folder, and the key value is the storage path. The storage path can use the following variables:
-
-- `{php_sdk_path}`: (Windows only) PHP SDK path
-- `{pkg_root_path}`: `pkgroot/`
-- `{working_dir}`: current working directory
-- `{download_path}`: download directory
-- `{source_path}`: source code decompression directory
-
-When `extract-files` does not use variables and is a relative path, the directory of the relative path is `{working_dir}`.
-
-## Open source license
-
-For `source.json`, each source file should contain an open source license.
-The `license` field stores the open source license information.
-
-Each `license` contains the following parameters:
-
-- `type`: `file` or `text`
-- `path`: the license file in the source code directory (required when `type` is `file`)
-- `text`: License text (required when `type` is `text`)
-
-Example (yaml extension source code with LICENSE file):
-
-```json
-{
- "yaml": {
- "type": "git",
- "path": "php-src/ext/yaml",
- "rev": "php7",
- "url": "https://github.com/php/pecl-file_formats-yaml",
- "license": {
- "type": "file",
- "path": "LICENSE"
- }
- }
-}
-```
-
-When an open source project has multiple licenses, multiple files can be specified:
-
-```json
-{
- "libuv": {
- "type": "ghtar",
- "repo": "libuv/libuv",
- "license": [
- {
- "type": "file",
- "path": "LICENSE"
- },
- {
- "type": "file",
- "path": "LICENSE-extra"
- }
- ]
- }
-}
-```
-
-When the license of an open source project uses different files between versions,
-`path` can be used as an array to list the possible license files:
-
-```json
-{
- "redis": {
- "type": "git",
- "path": "php-src/ext/redis",
- "rev": "release/6.0.2",
- "url": "https://github.com/phpredis/phpredis",
- "license": {
- "type": "file",
- "path": [
- "LICENSE",
- "COPYING"
- ]
- }
- }
-}
-```
+
diff --git a/docs/en/develop/structure.md b/docs/en/develop/structure.md
index e43b6d6d7..cadef786d 100644
--- a/docs/en/develop/structure.md
+++ b/docs/en/develop/structure.md
@@ -1,180 +1,5 @@
-# Introduction to project structure
+# Project Structure
-static-php-cli mainly contains three logical components: sources, dependent libraries, and extensions.
-These components contains 4 configuration files: `source.json`, `pkg.json`, `lib.json`, and `ext.json`.
-
-A complete process for building standalone static PHP is:
-
-1. Use the source download module `Downloader` to download specified or all source codes.
- These sources include PHP source code, dependent library source code, and extension source code.
-2. Use the source decompression module `SourceExtractor` to decompress the downloaded sources to the compilation directory.
-3. Use the dependency tool to calculate the dependent extensions and dependent libraries of the currently added extension,
- and then compile each library that needs to be compiled in the order of dependencies.
-4. After building each dependent library using `Builder` under the corresponding operating system, install it to the `buildroot` directory.
-5. If external extensions are included (the source code does not contain extensions within PHP),
- copy the external extensions to the `source/php-src/ext/` directory.
-6. Use `Builder` to build the PHP source code and build target to the `buildroot` directory.
-
-The project is mainly divided into several folders:
-
-- `bin/`: used to store program entry files, including `bin/spc`, `bin/spc-alpine-docker`, `bin/setup-runtime`.
-- `config/`: Contains all the extensions and dependent libraries supported by the project,
- as well as the download link and download methods of these sources. It is divided into files: `lib.json`, `ext.json`, `source.json`, `pkg.json`, `pre-built.json` .
-- `src/`: The core code of the project, including the entire framework and commands for compiling various extensions and libraries.
-- `vendor/`: The directory that Composer depends on, you do not need to make any modifications to it.
-
-The operating principle is to start a `ConsoleApplication` of `symfony/console`, and then parse the commands entered by the user in the terminal.
-
-## Basic command line structure
-
-`bin/spc` is an entry file, including the Unix common `#!/usr/bin/env php`,
-which is used to allow the system to automatically execute with the PHP interpreter installed on the system.
-After the project executes `new ConsoleApplication()`, the framework will automatically register them as commands.
-
-The project does not directly use the Command registration method and command execution method recommended by Symfony. Here are small changes:
-
-1. Each command uses the `#[AsCommand()]` Attribute to register the name and description.
-2. Abstract `execute()` so that all commands are based on `BaseCommand` (which is based on `Symfony\Component\Console\Command\Command`),
- and the execution code of each command itself is written in the `handle()` method .
-3. Added variable `$no_motd` to `BaseCommand`, which is used to display the Figlet greeting when the command is executed.
-4. `BaseCommand` saves `InputInterface` and `OutputInterface` as member variables. You can use `$this->input` and `$this->output` within the command class.
-
-## Basic source code structure
-
-The source code of the project is located in the `src/SPC` directory,
-supports automatic loading of the PSR-4 standard, and contains the following subdirectories and classes:
-
-- `src/SPC/builder/`: The core compilation command code used to build libraries,
- PHP and related extensions under different operating systems, and also includes some compilation system tool methods.
-- `src/SPC/command/`: All commands of the project are here.
-- `src/SPC/doctor/`: Doctor module, which is a relatively independent module used to check the system environment.
- It can be entered using the command `bin/spc doctor`.
-- `src/SPC/exception/`: exception class.
-- `src/SPC/store/`: Classes related to storage, files and sources are all here.
-- `src/SPC/util/`: Some reusable tool methods are here.
-- `src/SPC/ConsoleApplication.php`: command line program entry file.
-
-If you have read the source code, you may find that there is also a `src/globals/` directory,
-which is used to store some global variables, global methods,
-and non-PSR-4 standard PHP source code that is relied upon during the build process, such as extension sanity check code etc.
-
-## Phar application directory issue
-
-Like other php-cli projects, spc itself has additional considerations for paths.
-Because spc can run in multiple modes such as `php-cli directly`, `micro SAPI`, `php-cli with Phar`, `vendor with Phar`, etc.,
-there are ambiguities in various root directories. A complete explanation is given here.
-This problem is generally common in the base class path selection problem of accessing files in PHP projects, especially when used with `micro.sfx`.
-
-Note that this may only be useful for you when developing Phar projects or PHP frameworks.
-
-> Next, we will treat `static-php-cli` (that is, spc) as a normal `php` command line program. You can understand spc as any of your own php-cli applications for reference.
-
-There are three basic constant theoretical values below. We recommend that you introduce these three constants when writing PHP projects:
-
-- `WORKING_DIR`: the working directory when executing PHP scripts
-
-- `SOURCE_ROOT_DIR` or `ROOT_DIR`: the root directory of the project folder, generally the directory where `composer.json` is located
-
-- `FRAMEWORK_ROOT_DIR`: the root directory of the framework used, which may be used by self-developed frameworks. Generally, the framework directory is read-only
-
-You can define these constants in your framework entry or cli applications to facilitate the use of paths in your project.
-
-The following are PHP built-in constant values, which have been defined inside the PHP interpreter:
-
-- `__DIR__`: the directory where the file of the currently executed script is located
-
-- `__FILE__`: the file path of the currently executed script
-
-### Git project mode (source)
-
-Git project mode refers to a framework or program itself stored in plain text in the current folder, and running through `php path/to/entry.php`.
-
-Assume that your project is stored in the `/home/example/static-php-cli/` directory, or your project is the framework itself,
-which contains project files such as `composer.json`:
-
-```
-composer.json
-src/App/MyCommand.app
-vendor/*
-bin/entry.php
-```
-
-We assume that the above constants are obtained from `src/App/MyCommand.php`:
-
-| Constant | Value |
-|----------------------|------------------------------------------------------|
-| `WORKING_DIR` | `/home/example/static-php-cli` |
-| `SOURCE_ROOT_DIR` | `/home/example/static-php-cli` |
-| `FRAMEWORK_ROOT_DIR` | `/home/example/static-php-cli` |
-| `__DIR__` | `/home/example/static-php-cli/src/App` |
-| `__FILE__` | `/home/example/static-php-cli/src/App/MyCommand.php` |
-
-In this case, the values of `WORKING_DIR`, `SOURCE_ROOT_DIR`, and `FRAMEWORK_ROOT_DIR` are exactly the same: `/home/example/static-php-cli`.
-
-The source code of the framework and the source code of the application are both in the current path.
-
-### Vendor library mode (vendor)
-
-The vendor library mode generally means that your project is a framework or is installed into the project as a composer dependency by other applications,
-and the storage location is in the `vendor/author/XXX` directory.
-
-Suppose your project is `crazywhalecc/static-php-cli`, and you or others install this project in another project using `composer require`.
-
-We assume that static-php-cli contains all files except the `vendor` directory with the same `Git mode`, and get the constant value from `src/App/MyCommand`,
-Directory constant should be:
-
-| Constant | Value |
-|----------------------|--------------------------------------------------------------------------------------|
-| `WORKING_DIR` | `/home/example/another-app` |
-| `SOURCE_ROOT_DIR` | `/home/example/another-app` |
-| `FRAMEWORK_ROOT_DIR` | `/home/example/another-app/vendor/crazywhalecc/static-php-cli` |
-| `__DIR__` | `/home/example/another-app/vendor/crazywhalecc/static-php-cli/src/App` |
-| `__FILE__` | `/home/example/another-app/vendor/crazywhalecc/static-php-cli/src/App/MyCommand.php` |
-
-Here `SOURCE_ROOT_DIR` refers to the root directory of the project using `static-php-cli`.
-
-### Git project Phar mode (source-phar)
-
-Git project Phar mode refers to the mode of packaging the project directory of the Git project mode into a `phar` file. We assume that `/home/example/static-php-cli` will be packaged into a Phar file, and the directory has the following files:
-
-```
-composer.json
-src/App/MyCommand.app
-vendor/*
-bin/entry.php
-```
-
-When packaged into `app.phar` and stored in the `/home/example/static-php-cli` directory, `app.phar` is executed at this time. Assuming that the `src/App/MyCommand` code is executed, the constant is obtained in the file:
-
-| Constant | Value |
-|----------------------|----------------------------------------------------------------------|
-| `WORKING_DIR` | `/home/example/static-php-cli` |
-| `SOURCE_ROOT_DIR` | `phar:///home/example/static-php-cli/app.phar/` |
-| `FRAMEWORK_ROOT_DIR` | `phar:///home/example/static-php-cli/app.phar/` |
-| `__DIR__` | `phar:///home/example/static-php-cli/app.phar/src/App` |
-| `__FILE__` | `phar:///home/example/static-php-cli/app.phar/src/App/MyCommand.php` |
-
-Because the `phar://` protocol is required to read files in the phar itself, the project root directory and the framework directory will be different from `WORKING_DIR`.
-
-### Vendor Library Phar Mode (vendor-phar)
-
-Vendor Library Phar Mode means that your project is installed as a framework in other projects and stored in the `vendor` directory.
-
-We assume that your project directory structure is as follows:
-
-```
-composer.json # Composer configuration file of the current project
-box.json # Configuration file for packaging Phar
-another-app.php # Entry file of another project
-vendor/crazywhalecc/static-php-cli/* # Your project is used as a dependent library
-```
-
-When packaging these files under the directory `/home/example/another-app/` into `app.phar`, the value of the following constant for your project should be:
-
-| Constant | Value |
-|----------------------|------------------------------------------------------------------------------------------------------|
-| `WORKING_DIR` | `/home/example/another-app` |
-| `SOURCE_ROOT_DIR` | `phar:///home/example/another-app/app.phar/` |
-| `FRAMEWORK_ROOT_DIR` | `phar:///home/example/another-app/app.phar/vendor/crazywhalecc/static-php-cli` |
-| `__DIR__` | `phar:///home/example/another-app/app.phar/vendor/crazywhalecc/static-php-cli/src/App` |
-| `__FILE__` | `phar:///home/example/another-app/app.phar/vendor/crazywhalecc/static-php-cli/src/App/MyCommand.php` |
+
diff --git a/docs/en/develop/system-build-tools.md b/docs/en/develop/system-build-tools.md
index 48273f639..a5ac6edfe 100644
--- a/docs/en/develop/system-build-tools.md
+++ b/docs/en/develop/system-build-tools.md
@@ -1,242 +1,4 @@
# Compilation Tools
-static-php-cli uses many system compilation tools when building static PHP. These tools mainly include:
-
-- `autoconf`: used to generate `configure` scripts.
-- `make`: used to execute `Makefile`.
-- `cmake`: used to execute `CMakeLists.txt`.
-- `pkg-config`: Used to find the installation path of dependent libraries.
-- `gcc`: used to compile C/C++ projects under Linux.
-- `clang`: used to compile C/C++ projects under macOS.
-
-For Linux and macOS operating systems,
-these tools can usually be installed through the package manager, which is written in the doctor module.
-Theoretically we can also compile and download these tools manually,
-but this will increase the complexity of compilation, so we do not recommend this.
-
-## Linux Compilation Tools
-
-For Linux systems, different distributions have different installation methods for compilation tools.
-And for static compilation, the package management of some distributions cannot install libraries and tools for pure static compilation.
-Therefore, for the Linux platform and its different distributions,
-we currently provide a variety of compilation environment preparations.
-
-### Glibc Environment
-
-The glibc environment refers to the underlying `libc` library of the system
-(that is, the C standard library that all programs written in C language are dynamically linked to) uses `glibc`,
-which is the default environment for most distributions.
-For example: Ubuntu, Debian, CentOS, RHEL, openSUSE, Arch Linux, etc.
-
-In the glibc environment, the package management and compiler we use point to glibc by default,
-and glibc cannot be statically linked well.
-One of the reasons it cannot be statically linked is that its network library `nss` cannot be compiled statically.
-
-For the glibc environment, in static-php-cli and spc in 2.0-RC8 and later, you can choose two ways to build static PHP:
-
-1. Use Docker to build, you can use `bin/spc-alpine-docker` to build, it will build an Alpine Linux docker image.
-2. Use `bin/spc doctor --auto-fix` to install the `musl-wrapper` and `musl-cross-make` packages, and then build directly.
-([Related source code](https://github.com/crazywhalecc/static-php-cli/blob/main/src/SPC/doctor/item/LinuxMuslCheck.php))
-
-Generally speaking, the build results in these two environments are consistent, and you can choose according to actual needs.
-
-In the doctor module, static-php-cli will first detect the current Linux distribution.
-If the current distribution is a glibc environment, you will be prompted to install the musl-wrapper and musl-cross-make packages.
-
-The process of installing `musl-wrapper` in the glibc environment is as follows:
-
-1. Download the specific version of [musl-wrapper source code](https://musl.libc.org/releases/) from the musl official website.
-2. Use `gcc` installed from the package management to compile the musl-wrapper source code and generate `musl-libc` and other libraries: `./configure --disable-gcc-wrapper && make -j && sudo make install`.
-3. The musl-wrapper related libraries will be installed in the `/usr/local/musl` directory.
-
-The process of installing `musl-cross-make` in the glibc environment is as follows:
-
-1. Download the precompiled [musl-cross-make](https://dl.static-php.dev/static-php-cli/deps/musl-toolchain/) compressed package from dl.static-php.dev .
-2. Unzip to the `/usr/local/musl` directory.
-
-::: tip
-In the glibc environment, static compilation can be achieved by directly installing musl-wrapper,
-but musl-wrapper only contains `musl-gcc` and not `musl-g++`, which means that C++ code cannot be compiled.
-So we need musl-cross-make to provide `musl-g++`.
-
-The reason why the musl-cross-make package cannot be compiled directly locally is that
-its compilation environment requirements are relatively high (requires more than 36GB of memory, compiled under Alpine Linux),
-so we provide precompiled binary packages that can be used for all Linux distributions.
-
-At the same time, the package management of some distributions provides musl-wrapper,
-but musl-cross-make needs to match the corresponding musl-wrapper version,
-so we do not use package management to install musl-wrapper.
-
-Compiling musl-cross-make will be introduced in the **musl-cross-make Toolchain Compilation** section of this chapter.
-:::
-
-### Musl Environment
-
-The musl environment refers to the system's underlying `libc` library that uses `musl`,
-which is a lightweight C standard library that can be well statically linked.
-
-For the currently popular Linux distributions, Alpine Linux uses the musl environment,
-so static-php-cli can directly build static PHP under Alpine Linux.
-You only need to install basic compilation tools (such as `gcc`, `cmake`, etc.) directly from the package management.
-
-For other distributions, if your distribution uses the musl environment,
-you can also use static-php-cli to build static PHP directly after installing the necessary compilation tools.
-
-::: tip
-In the musl environment, static-php-cli will automatically skip the installation of musl-wrapper and musl-cross-make.
-:::
-
-### Docker Environment
-
-The Docker environment refers to using Docker containers to build static PHP. You can use `bin/spc-alpine-docker` to build.
-Before executing this command, you need to install Docker first, and then execute `bin/spc-alpine-docker` in the project root directory.
-
-After executing `bin/spc-alpine-docker`, static-php-cli will automatically download the Alpine Linux image and then build a `cwcc-spc-x86_64` or `cwcc-spc-aarch64` image.
-Then all build process is performed within this image, which is equivalent to compiling in Alpine Linux.
-
-## musl-cross-make Toolchain Compilation
-
-In Linux, although you do not need to manually compile the musl-cross-make tool,
-if you want to understand its compilation process, you can refer here.
-Another important reason is that this may not be compiled using automated tools such as CI and Actions,
-because the existing CI service compilation environment does not meet the compilation requirements of musl-cross-make,
-and the configuration that meets the requirements is too expensive.
-
-The compilation process of musl-cross-make is as follows:
-
-Prepare an Alpine Linux environment (either directly installed or using Docker).
-The compilation process requires more than **36GB** of memory,
-so you need to compile on a machine with larger memory.
-Without this much memory, compilation may fail.
-
-Then write the following content into the `config.mak` file:
-
-```makefile
-STAT = -static --static
-FLAG = -g0 -Os -Wno-error
-
-ifneq ($(NATIVE),)
-COMMON_CONFIG += CC="$(HOST)-gcc ${STAT}" CXX="$(HOST)-g++ ${STAT}"
-else
-COMMON_CONFIG += CC="gcc ${STAT}" CXX="g++ ${STAT}"
-endif
-
-COMMON_CONFIG += CFLAGS="${FLAG}" CXXFLAGS="${FLAG}" LDFLAGS="${STAT}"
-
-BINUTILS_CONFIG += --enable-gold=yes --enable-gprofng=no
-GCC_CONFIG += --enable-static-pie --disable-cet --enable-default-pie
-#--enable-default-pie
-
-CONFIG_SUB_REV = 888c8e3d5f7b
-GCC_VER = 13.2.0
-BINUTILS_VER = 2.40
-MUSL_VER = 1.2.4
-GMP_VER = 6.2.1
-MPC_VER = 1.2.1
-MPFR_VER = 4.2.0
-LINUX_VER = 6.1.36
-```
-
-And also you need to add `gcc-13.2.0.tar.xz.sha1` file, contents here:
-
-```
-5f95b6d042fb37d45c6cbebfc91decfbc4fb493c gcc-13.2.0.tar.xz
-```
-
-If you are using Docker to build, create a new `Dockerfile` file and write the following content:
-
-```dockerfile
-FROM alpine:edge
-
-RUN apk add --no-cache \
-gcc g++ git make curl perl \
-rsync patch wget libtool \
-texinfo autoconf automake \
-bison tar xz bzip2 zlib \
-file binutils flex \
-linux-headers libintl \
-gettext gettext-dev icu-libs pkgconf \
-pkgconfig icu-dev bash \
-ccache libarchive-tools zip
-
-WORKDIR /opt
-
-RUN git clone https://git.zv.io/toolchains/musl-cross-make.git
-WORKDIR /opt/musl-cross-make
-COPY config.mak /opt/musl-cross-make
-COPY gcc-13.2.0.tar.xz.sha1 /opt/musl-cross-make/hashes
-
-RUN make TARGET=x86_64-linux-musl -j || :
-RUN sed -i 's/poison calloc/poison/g' ./gcc-13.2.0/gcc/system.h
-RUN make TARGET=x86_64-linux-musl -j
-RUN make TARGET=x86_64-linux-musl install -j
-RUN tar cvzf x86_64-musl-toolchain.tgz output/*
-```
-
-If you are using Alpine Linux in a non-Docker environment, you can directly execute the commands in the Dockerfile, for example:
-
-```bash
-apk add --no-cache \
-gcc g++ git make curl perl \
-rsync patch wget libtool \
-texinfo autoconf automake \
-bison tar xz bzip2 zlib \
-file binutils flex \
-linux-headers libintl \
-gettext gettext-dev icu-libs pkgconf \
-pkgconfig icu-dev bash \
-ccache libarchive-tools zip
-
-git clone https://git.zv.io/toolchains/musl-cross-make.git
-# Copy config.mak to the working directory of musl-cross-make.
-# You need to replace /path/to/config.mak with your config.mak file path.
-cp /path/to/config.mak musl-cross-make/
-cp /path/to/gcc-13.2.0.tar.xz.sha1 musl-cross-make/hashes
-
-make TARGET=x86_64-linux-musl -j || :
-sed -i 's/poison calloc/poison/g' ./gcc-13.2.0/gcc/system.h
-make TARGET=x86_64-linux-musl -j
-make TARGET=x86_64-linux-musl install -j
-tar cvzf x86_64-musl-toolchain.tgz output/*
-```
-
-::: tip
-All the above scripts are suitable for x86_64 architecture Linux.
-If you need to build musl-cross-make for the ARM environment, just replace all `x86_64` above with `aarch64`.
-:::
-
-This compilation process may fail due to insufficient memory, network problems, etc.
-You can try a few more times, or use a machine with larger memory to compile.
-If you encounter problems or you have better improvement solutions, go to [Discussion](https://github.com/crazywhalecc/static-php-cli-hosted/issues/1).
-
-## macOS Environment
-
-For macOS systems, the main compilation tool we use is `clang`,
-which is the default compiler for macOS systems and is also the compiler of Xcode.
-
-Compiling under macOS mainly relies on Xcode or Xcode Command Line Tools.
-You can download Xcode from the App Store,
-or execute `xcode-select --install` in the terminal to install Xcode Command Line Tools.
-
-In addition, in the `doctor` environment check module, static-php-cli will check whether Homebrew,
-compilation tools, etc. are installed on the macOS system.
-If not, you will be prompted to install them. I will not go into details here.
-
-## FreeBSD Environment
-
-FreeBSD is also a Unix system, and its compilation tools are similar to macOS.
-You can directly use the package management `pkg` to install `clang` and other compilation tools through the `doctor` command.
-
-## pkg-config Compilation (*nix only)
-
-If you observe the compilation log when using static-php-cli to build static PHP, you will find that no matter what is compiled,
-`pkg-config` will be compiled first. This is because `pkg-config` is a library used to find dependencies.
-In earlier versions of static-php-cli, we directly used the `pkg-config` tool installed by package management,
-but this would cause some problems, such as:
-
-- Even if `PKG_CONFIG_PATH` is specified, `pkg-config` will try to find dependent packages from the system path.
-- Since `pkg-config` will look for dependent packages from the system path,
- if a dependent package with the same name exists in the system, compilation may fail.
-
-In order to avoid the above problems, we compile `pkg-config` into `buildroot/bin` in user mode and use it.
-We use parameters such as `--without-sysroot` to avoid looking for dependent packages from the system path.
+
diff --git a/docs/en/develop/vendor-mode/annotations.md b/docs/en/develop/vendor-mode/annotations.md
new file mode 100644
index 000000000..fa1790699
--- /dev/null
+++ b/docs/en/develop/vendor-mode/annotations.md
@@ -0,0 +1,6 @@
+# Annotations Reference
+
+
diff --git a/docs/en/develop/vendor-mode/dependency-injection.md b/docs/en/develop/vendor-mode/dependency-injection.md
new file mode 100644
index 000000000..2fb4be676
--- /dev/null
+++ b/docs/en/develop/vendor-mode/dependency-injection.md
@@ -0,0 +1,6 @@
+# Dependency Injection
+
+
diff --git a/docs/en/develop/vendor-mode/index.md b/docs/en/develop/vendor-mode/index.md
new file mode 100644
index 000000000..47c2e19c5
--- /dev/null
+++ b/docs/en/develop/vendor-mode/index.md
@@ -0,0 +1,6 @@
+# Vendor Mode
+
+
diff --git a/docs/en/develop/vendor-mode/lifecycle-hooks.md b/docs/en/develop/vendor-mode/lifecycle-hooks.md
new file mode 100644
index 000000000..d5502dbac
--- /dev/null
+++ b/docs/en/develop/vendor-mode/lifecycle-hooks.md
@@ -0,0 +1,6 @@
+# Lifecycle Hooks
+
+
diff --git a/docs/en/develop/vendor-mode/package-classes.md b/docs/en/develop/vendor-mode/package-classes.md
new file mode 100644
index 000000000..3c56c0a08
--- /dev/null
+++ b/docs/en/develop/vendor-mode/package-classes.md
@@ -0,0 +1,6 @@
+# Writing Package Classes
+
+
diff --git a/docs/en/faq/index.md b/docs/en/faq/index.md
index b65dca463..6359e3bf2 100644
--- a/docs/en/faq/index.md
+++ b/docs/en/faq/index.md
@@ -1,64 +1,62 @@
# FAQ
-Here will be some questions that you may encounter easily. There are currently many, but I need to take time to organize them.
+Here will be some questions that you may encounter easily.
-## What is the path of php.ini ?
+## What is the path of php.ini?
On Linux, macOS and FreeBSD, the path of `php.ini` is `/usr/local/etc/php/php.ini`.
On Windows, the path is `C:\windows\php.ini` or the current directory of `php.exe`.
-The directory where to look for `php.ini` can be changed on *nix using the manual build option `--with-config-file-path`.
+The directory where to look for `php.ini` can be changed on *nix using the build option `--with-config-file-path`.
In addition, on Linux, macOS and FreeBSD, `.ini` files present in the `/usr/local/etc/php/conf.d` directory will also be loaded.
On Windows, this path is empty by default.
-The directory can be changed using the manual build option `--with-config-file-scan-dir`.
+The directory can be changed using the build option `--with-config-file-scan-dir`.
-`php.ini` will also be searched for in [the other standard locations](https://www.php.net/manual/configuration.file.php).
+`php.ini` will also be searched for in [the other standard locations](https://www.php.net/manual/configuration.file.php).
## Can statically-compiled PHP install extensions?
-Because the principle of installing PHP extensions under the normal mode is to use `.so` type dynamic link library to install new extensions,
+Because the principle of installing PHP extensions under the normal mode is to use `.so` type dynamic link library to install new extensions,
and we use the static link PHP compiled by this project. However, static linking has different definitions in different operating systems.
-First of all, for Linux systems, statically linked binaries will not link the system's dynamic link library.
+First of all, for Linux systems, statically linked binaries will not link the system's dynamic link library.
Purely statically linked binaries (`build with -all-static`) cannot load dynamic libraries, so new extensions cannot be added.
At the same time, in pure static mode, you cannot use extensions such as `ffi` to load external `.so` modules.
You can use the command `ldd buildroot/bin/php` to check whether the binary you built under Linux is purely statically linked.
-If you [build GNU libc based PHP](../guide/build-with-glibc), you can use the `ffi` extension to load external `.so` modules and load `.so` extensions with the same ABI.
+If you build GNU libc based PHP, you can use the `ffi` extension to load external `.so` modules and load `.so` extensions with the same ABI.
-For example, you can use the following command to build a static PHP binary dynamically linked with glibc,
+For example, you can use the following command to build a static PHP binary dynamically linked with glibc,
supporting FFI extensions and loading the `xdebug.so` extension of the same PHP version and the same TS type:
```bash
-bin/spc-gnu-docker download --for-extensions=ffi,xml --with-php=8.4
-bin/spc-gnu-docker build ffi,xml --build-cli --debug
+SPC_TARGET=native-native-gnu.2.17 spc build:php "ffi,xml" --build-cli -vvv
buildroot/bin/php -d "zend_extension=/path/to/php{PHP_VER}-{ts/nts}/xdebug.so" --ri xdebug
```
+This uses the Zig toolchain to produce a partially static binary dynamically linked against glibc 2.17. No Docker and no extra cross-compilation toolchain are required.
+
For macOS platform, almost all binaries under macOS cannot be truly purely statically linked, and almost all binaries will link macOS system libraries: `/usr/lib/libresolv.9.dylib` and `/usr/lib/libSystem.B.dylib`.
So on macOS, you can **directly** use SPC to build statically compiled PHP binaries with dynamically linked extensions:
-1. Build shared extension `xxx.so` using: `--build-shared=XXX` option. e.g. `bin/spc build bcmath,zlib --build-shared=xdebug --build-cli`
+1. Build shared extension `xxx.so` using: `--build-shared=XXX` option. e.g. `spc build:php "bcmath,zlib" --build-shared=xdebug --build-cli`
2. You will get `buildroot/modules/xdebug.so` and `buildroot/bin/php`.
3. The `xdebug.so` file could be used for php that version and thread-safe are the same.
For the Windows platform, since officially built extensions (such as `php_yaml.dll`) force the use of the `php8.dll` dynamic library as a link, and statically built PHP does not include any dynamic libraries other than system libraries,
-php.exe built by static-php cannot load officially built dynamic extensions. Since static-php-cli does not yet support building dynamic extensions, there is currently no way to load dynamic extensions with static-php.
+php.exe built by static-php cannot load officially built dynamic extensions. Since StaticPHP does not yet support building dynamic extensions, there is currently no way to load dynamic extensions with static-php.
However, Windows can normally use the `FFI` extension to load other dll files and call them.
## Can it support Oracle database extension?
-Some extensions that rely on closed source libraries, such as `oci8`, `sourceguardian`, etc.,
+Some extensions that rely on closed source libraries, such as `oci8`, `sourceguardian`, etc.,
they do not provide purely statically compiled dependent library files (`.a`), only dynamic dependent library files (`.so`).
-These extensions cannot be compiled into static-php-cli using source code, so this project may never support these extensions.
+These extensions cannot be compiled into StaticPHP using source code, so this project may never support these extensions.
However, in theory you can access and use such extensions under macOS and Linux according to the above questions.
-If you have a need for such extensions, or most people have needs for these closed-source extensions,
-see the discussion on [standalone-php-cli](https://github.com/crazywhalecc/static-php-cli/discussions/58). Welcome to leave a message.
-
## Does it support Windows?
The project currently supports Windows, but the number of supported extensions is small. Windows support is not perfect. There are mainly the following problems:
@@ -68,26 +66,26 @@ The project currently supports Windows, but the number of supported extensions i
## Can I protect my source code with micro?
-You can't. micro.sfx is essentially combining php and php code into one file,
+You can't. micro.sfx is essentially combining php and php code into one file,
there is no process of compiling or encrypting the PHP code.
First of all, php-src is the official interpreter of PHP code, and there is no PHP compiler compatible with mainstream branches on the market.
-I saw on the Internet that there is a project called BPC (Binary PHP Compiler?) that can compile PHP into binary,
+I saw on the Internet that there is a project called BPC (Binary PHP Compiler?) that can compile PHP into binary,
but there are many restrictions.
-The direction of encrypting and protecting the code is not the same as compiling.
-After compiling, the code can also be obtained through reverse engineering and other methods.
+The direction of encrypting and protecting the code is not the same as compiling.
+After compiling, the code can also be obtained through reverse engineering and other methods.
The real protection is still carried out by means of packing and encrypting the code.
-Therefore, this project (static-php-cli) and related projects (lwmbs, swoole-cli) all provide a convenient compilation tool for php-src source code.
+Therefore, this project (StaticPHP) and related projects (lwmbs, swoole-cli) all provide a convenient compilation tool for php-src source code.
The phpmicro referenced by this project and related projects is only a package of PHP's sapi interface, not a compilation tool for PHP code.
-The compiler for PHP code is a completely different project, so the extra cases are not taken into account.
-If you are interested in encryption, you can consider using existing encryption technologies,
+The compiler for PHP code is a completely different project, so the extra cases are not taken into account.
+If you are interested in encryption, you can consider using existing encryption technologies,
such as Swoole Compiler, Source Guardian, etc.
## Unable to use ssl
-**Update: This issue has been fixed in the latest version of static-php-cli, which now reads the system's certificate file by default. If you still have problems, try the solution below.**
+**Update: This issue has been fixed in the latest version of StaticPHP, which now reads the system's certificate file by default. If you still have problems, try the solution below.**
When using curl, pgsql, etc. to request an HTTPS website or establish an SSL connection, there may be an `error:80000002:system library::No such file or directory` error.
This error is caused by statically compiled PHP without specifying `openssl.cafile` via `php.ini`.
@@ -101,8 +99,9 @@ For the certificate locations of different distros, please refer to [Golang docs
## Why don't we support older versions of PHP?
-Because older versions of PHP have many problems, such as security issues, performance issues, and functional issues.
-In addition, many older versions of PHP are not compatible with the latest dependency libraries,
+Because older versions of PHP have many problems, such as security issues, performance issues, and functional issues.
+In addition, many older versions of PHP are not compatible with the latest dependency libraries,
which is one of the reasons why older versions of PHP are not supported.
-You can use older versions compiled earlier by static-php-cli, such as PHP 8.0, but earlier versions will not be explicitly supported.
+You can use older versions compiled earlier by StaticPHP, such as PHP 8.0, but earlier versions will not be explicitly supported.
+
diff --git a/docs/en/guide/action-build.md b/docs/en/guide/action-build.md
deleted file mode 100644
index 7d4bba327..000000000
--- a/docs/en/guide/action-build.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# GitHub Action Build
-
-Action Build refers to compiling directly using GitHub Action.
-
-If you don't want to compile it yourself, you can download the artifact from the existing Action in this project,
-or you can download it from a self-hosted server：[Enter](https://dl.static-php.dev/static-php-cli/common/).
-
-> Self-hosted binaries are also built from Actions: [repo](https://github.com/static-php/static-php-cli-hosted).
-> The extensions included are: bcmath,bz2,calendar,ctype,curl,dom,exif,fileinfo,filter,ftp,gd,gmp,iconv,xml,mbstring,mbregex,mysqlnd,openssl,
-> pcntl,pdo,pdo_mysql,pdo_sqlite,phar,posix,redis,session,simplexml,soap,sockets,sqlite3,tokenizer,xmlwriter,xmlreader,zlib,zip
-
-## Build Guide
-
-Using GitHub Action makes it easy to build a statically compiled PHP and phpmicro,
-while also defining the extensions to compile.
-
-1. Fork project.
-2. Go to the Actions of the project and select `CI`.
-3. Select `Run workflow`, fill in the PHP version you want to compile, the target type, and the list of extensions. (extensions comma separated, e.g. `bcmath,curl,mbstring`)
-4. After waiting for about a period of time, enter the corresponding task and get `Artifacts`.
-
-If you enable `debug`, all logs will be output at build time, including compiled logs, for troubleshooting.
-
-> If you need to build in other environments, you can use [manual build](./manual-build).
-
-## Extensions
-
-You can go to [extensions](./extensions) check here to see if all the extensions you need currently support.
-and then go to [command generator](./cli-generator) select the extension you need to compile, copy the extensions string to `extensions` option.
diff --git a/docs/en/guide/build-on-windows.md b/docs/en/guide/build-on-windows.md
deleted file mode 100644
index e5c0c459b..000000000
--- a/docs/en/guide/build-on-windows.md
+++ /dev/null
@@ -1,228 +0,0 @@
-# Build on Windows
-
-Because the Windows system is an NT kernel, the compilation tools and operating system interfaces
-used by Unix-like operating systems are almost completely different,
-so the build process on Windows will be slightly different from that of Unix systems.
-
-## GitHub Actions Build
-
-Building the Windows version of static-php from Actions is now supported.
-Like Linux and macOS, you need to Fork the static-php-cli repository to your GitHub account first,
-then you can enter [Extension List](./extensions) to select the extension to be compiled,
-and then go to your own `CI on Windows` select the PHP version, fill in the extension list (comma separated), and click Run.
-
-If you're going to develop or build locally, please read on.
-
-## Requirements
-
-The tools required to build static PHP on Windows are the same as PHP's official Windows build tools.
-You can read [Official Documentation](https://wiki.php.net/internals/windows/stepbystepbuild_sdk_2).
-
-To sum up, you need the following environment and tools:
-
-- Windows 10/11 (requires build 17063 or later)
-- Visual Studio 2019/2022 (recommended 2022)
-- C++ desktop development for Visual Studio
-- Git for Windows
-- [php-sdk-binary-tools](https://github.com/php/php-sdk-binary-tools) (can be installed automatically using doctor)
-- strawberry-perl (can be installed automatically using doctor)
-- nasm (can be installed automatically using doctor)
-
-::: tip
-The construction of static-php-cli on Windows refers to using MSVC to build PHP and is not based on MinGW, Cygwin, WSL and other environments.
-
-If you prefer to use WSL, please refer to the chapter on Building on Linux.
-:::
-
-After installing Visual Studio and selecting the C++ desktop development workload,
-you may download about 8GB of compilation tools, and the download speed depends on your network conditions.
-
-### Install Git
-
-Git for Windows can be downloaded and installed from [here](https://git-scm.com/download/win) `Standalone Installer 64-bit` version,
-installed in the default location (`C:\Program Files\Git\`).
-If you don't want to download and install manually,
-you can also use Visual Studio Installer and check Git in the **Individual component** tab.
-
-### Prepare static-php-cli
-
-Downloading the static-php-cli project is very simple, just use git clone.
-It is recommended to place the project in `C:\spc-build\` or a similar directory.
-It is best **not to have spaces in the path**.
-
-```shell
-mkdir "C:\spc-build"
-cd C:\spc-build
-git clone https://github.com/crazywhalecc/static-php-cli.git
-cd static-php-cli
-```
-
-It is a bit strange that static-php-cli itself requires a PHP environment,
-but now you can quickly install the PHP environment through a script.
-Generally, your computer will not have the Windows version of PHP installed,
-so we recommend that you use `bin/setup-runtime` directly after downloading static-php-cli to install PHP and Composer in the current directory.
-
-```shell
-# Install PHP and Composer to the ./runtime/ directory
-bin/setup-runtime
-
-# After installation, if you need to use PHP and Composer in global commands,
-# use the following command to add the runtime/ directory to PATH
-bin/setup-runtime -action add-path
-
-# Delete the runtime/ directory in PATH
-bin/setup-runtime -action remove-path
-```
-
-Finally, now that you have PHP and Composer installed, you need to install static-php-cli's Composer dependencies:
-
-```shell
-composer install
-```
-
-### Install other Tools (automatic)
-
-For `php-sdk-binary-tools`, `strawberry-perl`, and `nasm`,
-we recommend that you directly use the command `bin/spc doctor` to check and install them.
-
-If doctor successfully installs automatically, please **skip** the steps below to manually install the above tools.
-
-But if the automatic installation fails, please refer to the manual installation method below.
-
-### Install php-sdk-binary-tools (manual)
-
-```shell
-cd C:\spc-build\static-php-cli
-git clone https://github.com/php/php-sdk-binary-tools.git
-```
-
-> You can also set the global variable `PHP_SDK_PATH` in Windows settings and
-> clone the project to the path corresponding to the variable.
-> Under normal circumstances, you don't need to change it.
-
-### Install strawberry-perl (manual)
-
-> If you don't need to compile the openssl extension, you don't need to install perl.
-
-1. Download the latest version of strawberry-perl from [GitHub](https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/).
-2. Install to the `C:\spc-build\static-php-cli\pkgroot\perl\` directory.
-
-> You can download the `-portable` version and extract it directly to the above directory.
-> The last `perl.exe` should be located at `C:\spc-build\static-php-cli\pkgroot\perl\perl\bin\perl.exe`.
-
-### Install nasm (manual)
-
-> If you don't need to compile openssl extension, you don't need to install nasm.
-
-1. Download the nasm tool (x64) from [official website](https://www.nasm.us/pub/nasm/releasebuilds/).
-2. Place `nasm.exe` and `ndisasm.exe` in the `C:\spc-build\static-php-cli\php-sdk-binary-tools\bin\` directory.
-
-## Download required sources
-
-Same as [Manual build - Download](./manual-build.html#command-download)
-
-## Build PHP
-
-Use the build command to start building the static php binary.
-Before executing the `bin/spc build` command, be sure to use the `download` command to download sources.
-It is recommended to use `doctor` to check the environment.
-
-### Build SAPI
-
-You need to go to [Extension List](./extensions) or [Command Generator](./cli-generator) to select the extension you want to add,
-and then use the command `bin/spc build` to compile.
-You need to specify targets, choose from the following parameters (at least one):
-
-- `--build-cli`: Build a cli sapi (command line interface, which can execute PHP code on the command line)
-- `--build-micro`: Build a micro sapi (used to build a standalone executable binary containing PHP code)
-
-```shell
-# Compile PHP with bcmath,openssl,zlib extensions, the compilation target is cli
-bin/spc build "bcmath,openssl,zlib" --build-cli
-
-# Compile PHP with phar,curl,posix,pcntl,tokenizer extensions, compile target is micro and cli
-bin/spc build "bcmath,openssl,zlib" --build-micro --build-cli
-```
-
-::: warning
-In Windows, it is best to use double quotes to wrap parameters containing commas, such as `"bcmath,openssl,mbstring"`.
-:::
-
-### Debug
-
-If you encounter problems during the compilation process, or want to view each executing shell command,
-you can use `--debug` to enable debug mode and view all terminal logs:
-
-```shell
-bin/spc build "openssl" --build-cli --debug
-```
-
-### Build Options
-
-During the compilation process, in some special cases,
-the compiler and the content of the compilation directory need to be intervened.
-You can try to use the following commands:
-
-- `--with-clean`: clean up old make files before compiling PHP
-- `--enable-zts`: Make compiled PHP thread-safe version (default is NTS version)
-- `--with-libs=XXX,YYY`: Compile the specified dependent library before compiling PHP, and activate some extension optional functions
-- `--with-config-file-scan-dir=XXX`: Set the directory to scan for `.ini` files after reading `php.ini` (Check [here](../faq/index.html#what-is-the-path-of-php-ini) for default paths)
-- `-I xxx=yyy`: Hard compile INI options into PHP before compiling (support multiple options, alias is `--with-hardcoded-ini`)
-- `--with-micro-fake-cli`: When compiling micro, let micro's `PHP_SAPI` pretend to be `cli` (for compatibility with some programs that check `PHP_SAPI`)
-- `--disable-opcache-jit`: Disable opcache jit (enabled by default)
-- `--without-micro-ext-test`: After building micro.sfx, do not test the running results of different extensions in micro.sfx
-- `--with-suggested-exts`: Add `ext-suggests` as dependencies when compiling
-- `--with-suggested-libs`: Add `lib-suggests` as dependencies when compiling
-- `--with-upx-pack`: Use UPX to reduce the size of the binary file after compilation (you need to use `bin/spc install-pkg upx` to install upx first)
-- `--with-micro-logo=XXX.ico`: Customize the icon of the `exe` executable file after customizing the micro build (in the format of `.ico`)
-
-Here is a simple example where we preset a larger `memory_limit` and disable the `system` function:
-
-```shell
-bin/spc build "bcmath,openssl" --build-cli -I "memory_limit=4G" -I "disable_functions=system"
-```
-
-Another example: Customize our hello-world.exe program logo:
-
-```shell
-bin/spc build "ffi,bcmath" --build-micro --with-micro-logo=mylogo.ico --debug
-bin/spc micro:combine hello.php
-# Then we got `my-app.exe` with custom logo!
-my-app.exe
-```
-
-## Use php.exe
-
-After php.exe is compiled, it is located in the `buildroot\bin\` directory. You can copy it to any location for use.
-
-```shell
-.\php -v
-```
-
-## Use micro.sfx
-
-> phpmicro is a SelF-extracted eXecutable SAPI module,
-> provided by [phpmicro](https://github.com/dixyes/phpmicro) project.
-> But this project is using a [fork](https://github.com/static-php/phpmicro) of phpmicro, because we need to add some features to it.
-> It can put php runtime and your source code together.
-
-The final compilation result will output a file named `./micro.sfx`,
-which needs to be used with your PHP source code like `code.php`.
-This file will be located in the path `buildroot/bin/micro.sfx`.
-
-Prepare your project source code, which can be a single PHP file or a Phar file, for use.
-
-> If you want to combine phar files, you must add `phar` extension when compiling!
-
-```shell
-# code.php " Using glibc static binaries can run on most modern Linux distributions but cannot run on musl libc distributions, such as CentOS 6, Alpine Linux, etc.
-
-## Build glibc Compatible Linux Binary
-
-The latest version of static-php-cli includes the `bin/spc-gnu-docker` script,
-which can create a CentOS 7.x (glibc-2.17) Docker container with one click and build a glibc compatible PHP static binary in the container.
-
-Then, run the following command once.
-The first run will take a long time because it needs to download the CentOS 7.x image and some build tools.
-
-```bash
-bin/spc-gnu-docker
-```
-
-After the image is built, you will see the same command help menu as `bin/spc`, which means the container is ready.
-
-After the container is ready, you can refer to the [local build](./manual-build) section to build your PHP static binary.
-Just replace `bin/spc` or `./spc` with `bin/spc-gnu-docker`.
-
-```bash
-bin/spc-gnu-docker build bcmath,ctype,openssl,pdo,phar,posix,session,tokenizer,xml,zip --build-cli --debug
-```
-
-## Notes
-
-In rare cases, glibc-based static PHP may encounter segment faults and other errors, but there are currently few examples.
-If you encounter any issues, please submit an issue.
-
-glibc build is an extended feature and is not part of the default static-php support.
-If you have related issues or requirements, please indicate that you are building based on glibc when submitting an issue.
-
-If you need to build glibc-based binaries without using Docker,
-please refer to the `bin/spc-gnu-docker` script to manually create a similar environment.
-
-Please keep in mind that we only support glibc build with `bin/spc-gnu-docker`. Compilation on RHEL 9 & 10 has been tested and is stable, but if you run into issues, we may choose not to fix them.
diff --git a/docs/en/guide/cli-generator.md b/docs/en/guide/cli-generator.md
index 87163d000..8bd71229d 100644
--- a/docs/en/guide/cli-generator.md
+++ b/docs/en/guide/cli-generator.md
@@ -2,15 +2,10 @@
aside: false
---
-
-# CLI Build Command Generator
+# Build Command Generator
-::: tip
-The extensions selected below may contain extensions that are not supported by the selected operating system,
-which may cause compilation to fail. Please check [Supported Extensions](./extensions) first.
-:::
-
-
+
diff --git a/docs/en/guide/cli-reference.md b/docs/en/guide/cli-reference.md
new file mode 100644
index 000000000..3ca5b527f
--- /dev/null
+++ b/docs/en/guide/cli-reference.md
@@ -0,0 +1,525 @@
+---
+outline: 'deep'
+---
+
+# CLI Reference
+
+::: tip
+If you installed spc as a pre-built binary, replace every `spc` in this page with `./spc` (or `.\spc.exe` on Windows).
+
+If you installed from source, use `bin/spc` instead.
+:::
+
+## download
+
+Download source archives and pre-built binaries required for building.
+
+```bash
+spc download [artifacts] [options]
+```
+
+`artifacts` (optional): Specific artifacts to download, comma-separated (e.g. `"php-src,openssl,curl"`).
+
+### Options
+
+| Option | Short | Description |
+|---------------------------------|-------|-------------------------------------------------------|
+| `--for-extensions=` | `-e` | Download artifacts needed by the given extensions |
+| `--for-libs=` | `-l` | Download artifacts needed by the given libraries |
+| `--for-packages=` | | Download artifacts needed by the given packages |
+| `--without-suggests` | | Skip suggested packages when using `--for-extensions` |
+| `--clean` | | Delete existing download cache before fetching |
+| `--with-php=` | | PHP version in `major.minor` format (default: `8.4`) |
+| `--prefer-binary` | `-p` | Prefer pre-built binaries over source archives |
+| `--prefer-source` | | Prefer source archives over pre-built binaries |
+| `--source-only` | | Only download source artifacts |
+| `--binary-only` | | Only download binary artifacts |
+| `--parallel=` | `-P` | Number of parallel downloads (default: `1`) |
+| `--retry=` | `-R` | Number of retries on failure (default: `0`) |
+| `--ignore-cache=` | | Force re-download the specified artifacts |
+| `--no-alt` | | Do not use alternative mirror URLs |
+| `--no-shallow-clone` | | Do not clone git repositories shallowly |
+| `--custom-url=` | `-U` | Override the download URL for a source |
+| `--custom-git=` | `-G` | Override with a custom git repository |
+| `--custom-local=` | `-L` | Use a local path as a source override |
+
+### Examples
+
+```bash
+# Download only what the chosen extensions need
+spc download --for-extensions="bcmath,openssl,curl" --with-php=8.4
+
+# Download specific artifacts
+spc download "php-src,openssl"
+
+# Speed up with parallelism and retries
+spc download --for-extensions="bcmath,openssl,curl" --parallel 8 --retry=3
+
+# Prefer pre-built binaries
+spc download --for-extensions="bcmath,openssl,curl" --prefer-binary
+
+# Force re-download the PHP source (e.g. when switching versions)
+spc download --for-extensions="bcmath,curl" --ignore-cache="php-src" --with-php=8.3
+
+# Override a download URL
+spc download --for-extensions="bcmath" --custom-url "php-src:https://downloads.php.net/~user/php-8.5.0alpha1.tar.xz"
+```
+
+## build:php {#build-php}
+
+Build PHP and extensions from source. Alias: `build`.
+
+```bash
+spc build:php [options]
+```
+
+`extensions` (required): Comma-separated list of extensions to compile statically (e.g. `"bcmath,openssl,curl"`).
+
+All `download` options are also available on `build:php` with the `--dl-` prefix (e.g. `--dl-with-php=8.3`, `--dl-parallel=4`). These are passed to the automatic downloader that runs before the build.
+
+### SAPI Selection {#sapi-selection}
+
+These flags apply only to the combined `build:php` target. To build a specific SAPI in isolation, use its dedicated command (e.g. `spc build:php-cli`).
+
+| Option | Description |
+|----------------------|---------------------------------------------------------------|
+| `--build-cli` | Build the `cli` SAPI (`php` / `php.exe`) |
+| `--build-fpm` | Build `php-fpm` (Linux and macOS only) |
+| `--build-cgi` | Build `php-cgi` |
+| `--build-micro` | Build `micro.sfx` |
+| `--build-embed` | Build the embed static library (`libphp.a` / `php8embed.lib`) |
+| `--build-frankenphp` | Build the FrankenPHP binary |
+
+### Common Build Options {#common-build-options}
+
+| Option | Short | Description |
+|--------------------------------------|-------|--------------------------------------------------------------------------------------------------------|
+| `--no-strip` | | Keep debug symbols; do not strip the binary |
+| `--with-upx-pack` | | Compress the output binary with UPX (install first with `spc install-pkg upx`; Linux and Windows only) |
+| `--disable-opcache-jit` | | Disable OPcache JIT |
+| `--with-config-file-path=` | | Directory where PHP looks for `php.ini` (default: `/usr/local/etc/php`) |
+| `--with-config-file-scan-dir=` | | Directory PHP scans for additional `.ini` files (default: `/usr/local/etc/php/conf.d`) |
+| `--with-hardcoded-ini=` | `-I` | Bake an INI setting into the binary at compile time (repeatable) |
+| `--enable-zts` | | Enable thread-safe (ZTS) mode |
+| `--no-smoke-test` | | Skip the post-build smoke tests |
+| `--with-suggests` | | Also resolve and install suggested packages |
+| `--with-packages=` | | Additional packages to install alongside the build |
+| `--no-download` | | Skip the download step (use existing cached files) |
+| `--build-shared=` | `-D` | Extensions to compile as shared `.so` / `.dll` instead of static |
+
+### micro Options {#micro-options}
+
+| Option | Description |
+|----------------------------|--------------------------------------------------------------------------------------|
+| `--with-micro-fake-cli` | Make `micro`'s `PHP_SAPI` report `cli` instead of `micro` |
+| `--without-micro-ext-test` | Disable the post-build extension test for `micro.sfx` |
+| `--with-micro-logo=` | Embed a custom `.ico` icon into `micro.sfx` (Windows only) |
+| `--enable-micro-win32` | Build `micro.sfx` as a Win32 GUI application instead of a console app (Windows only) |
+
+### frankenphp Options {#frankenphp-options}
+
+| Option | Description |
+|--------------------------------|---------------------------------------------------|
+| `--enable-zts` | Required for FrankenPHP; enables thread-safe mode |
+| `--with-frankenphp-app=` | Embed a directory into the FrankenPHP binary |
+
+### embed Options {#embed-options}
+
+| Option | Description |
+|-------------------------|-----------------------------------------------------------------------|
+| `--build-shared=` | Compile specific extensions as shared libraries (requires embed SAPI) |
+
+### Download Pass-through Options {#download-options}
+
+All downloader options are available with the `--dl-` prefix:
+
+| Option | Description |
+|------------------------------------|--------------------------------------------|
+| `--dl-with-php=` | PHP version to download (default: `8.4`) |
+| `--dl-prefer-binary` | Prefer pre-built binaries for dependencies |
+| `--dl-parallel=` | Number of parallel downloads |
+| `--dl-retry=` | Number of retries on failure |
+| `--dl-custom-url=` | Override a source download URL |
+| `--dl-custom-git=` | Override with a custom git repository |
+
+Downloader options passed to `build:php` are used by the automatic downloader that runs before the build.
+This allows you to control the download behavior without needing a separate `spc download` command.
+
+```bash
+spc build:php "bcmath,openssl,curl" --build-cli --dl-with-php=8.3 --dl-prefer-binary --dl-parallel=4
+```
+
+### Examples
+
+```bash
+# Build cli SAPI
+spc build:php "bcmath,openssl,curl" --build-cli
+
+# Build cli + micro together
+spc build:php "bcmath,phar,openssl,curl" --build-cli --build-micro
+
+# Build with a specific PHP version
+spc build:php "bcmath,openssl" --build-cli --dl-with-php=8.3
+
+# Bake INI into the binary
+spc build:php "bcmath,pcntl" --build-cli -I "memory_limit=4G" -I "disable_functions=system"
+
+# Keep debug symbols
+spc build:php "bcmath,openssl" --build-cli --no-strip
+
+# Build FrankenPHP (ZTS required)
+spc build:php "bcmath,openssl,curl" --build-frankenphp --enable-zts
+```
+
+## build:php-cli, build:php-fpm, build:php-micro, build:php-embed, build:php-cgi, build:frankenphp
+
+Dedicated single-target build commands. These accept the same options as `build:php` except the SAPI-selection flags (`--build-*`), which are implicit.
+
+```bash
+spc build:php-cli "bcmath,openssl,curl"
+spc build:php-micro "bcmath,phar,openssl"
+spc build:php-fpm "bcmath,openssl,curl,pdo_mysql"
+spc build:php-embed "bcmath,openssl"
+spc build:frankenphp "bcmath,openssl,curl" --enable-zts
+```
+
+## build:libs
+
+Build one or more library packages from source.
+
+```bash
+spc build:libs [options]
+```
+
+`libraries` (required): Comma-separated list of library package names to build (e.g. `"openssl,curl,zlib"`).
+
+All `download` options are available with the `--dl-` prefix.
+
+### Options
+
+| Option | Short | Description |
+|---|---|---|
+| `--with-suggests` | `-L`, `-E` | Also resolve and install suggested packages |
+| `--with-packages=` | | Additional packages to install alongside the build, comma-separated |
+| `--no-download` | | Skip downloading artifacts (use existing cached files) |
+
+### Examples
+
+```bash
+# Build a single library
+spc build:libs openssl
+
+# Build multiple libraries
+spc build:libs "openssl,curl,zlib"
+
+# Build with suggested packages included
+spc build:libs openssl --with-suggests
+
+# Skip the download step
+spc build:libs openssl --no-download
+```
+
+## craft
+
+Read a `craft.yml` and run the full build pipeline automatically.
+
+```bash
+spc craft [path/to/craft.yml]
+```
+
+If no path is given, `craft.yml` in the current working directory is used. See [craft.yml configuration](../develop/craft-yml) for the file format.
+
+## doctor
+
+Diagnose whether the current environment can compile PHP normally.
+
+```bash
+spc doctor [--auto-fix[=never]]
+```
+
+| Option | Description |
+|--------------------|--------------------------------------------------------------------|
+| `--auto-fix` | Automatically fix detected issues using the system package manager |
+| `--auto-fix=never` | Report issues but never attempt automatic fixes |
+
+## dev:shell
+
+Enter an interactive shell with StaticPHP's build environment pre-loaded (compiler wrappers, `buildroot/`, `pkgroot/` paths, etc. on `PATH`).
+
+```bash
+spc dev:shell
+```
+
+Useful for compiling small programs against `libphp.a` (embed SAPI) or inspecting the build environment manually.
+
+## check-update
+
+Check whether newer versions are available for downloaded artifacts.
+
+```bash
+spc check-update [artifact] [options]
+```
+
+`artifact` (optional): Artifact names to check, comma-separated. Defaults to all currently downloaded artifacts.
+
+### Options
+
+| Option | Short | Description |
+|---|---|---|
+| `--json` | | Output results in JSON format |
+| `--bare` | | Check without requiring the artifact to be downloaded first (old version will be `null`) |
+| `--parallel=` | `-p` | Number of parallel update checks (default: `10`) |
+| `--with-php=` | | PHP version context in `major.minor` format (default: `8.4`) |
+
+### Examples
+
+```bash
+# Check all downloaded artifacts
+spc check-update
+
+# Check specific artifacts
+spc check-update "openssl,curl"
+
+# Output as JSON
+spc check-update --json
+
+# Check without requiring a prior download
+spc check-update "openssl" --bare
+```
+
+## dump-extensions
+
+Analyse a Composer project and output the list of PHP extensions it requires.
+
+```bash
+spc dump-extensions [path] [options]
+```
+
+`path` (optional): Path to the project root (default: `.`).
+
+### Options
+
+| Option | Short | Description |
+|---|---|---|
+| `--format=` | `-F` | Output format (default: `default`) |
+| `--no-ext-output=` | `-N` | When no extensions are found, output this default comma-separated list instead of exiting with failure |
+| `--no-dev` | | Exclude dev dependencies |
+| `--no-spc-filter` | `-S` | Do not apply the SPC filter when determining required extensions |
+
+### Examples
+
+```bash
+# Analyse the current directory
+spc dump-extensions
+
+# Analyse a specific directory
+spc dump-extensions /path/to/project
+
+# Exclude dev dependencies
+spc dump-extensions --no-dev
+
+# Fall back to a default list when no extensions are found
+spc dump-extensions --no-ext-output="bcmath,openssl"
+```
+
+## dump-license
+
+Export open-source license files for artifacts.
+
+```bash
+spc dump-license [artifacts] [options]
+```
+
+`artifacts` (optional): Specific artifacts whose licenses should be dumped, comma-separated (e.g. `"php-src,openssl,curl"`).
+
+### Options
+
+| Option | Short | Description |
+|---|---|---|
+| `--for-extensions=` | `-e` | Dump by extension names (automatically includes `php-src`), e.g. `"openssl,mbstring"` |
+| `--for-libs=` | `-l` | Dump by library names, e.g. `"openssl,zlib"` |
+| `--for-packages=` | `-p` | Dump by package names, e.g. `"php,libssl"` |
+| `--dump-dir=` | `-d` | Directory to write license files (default: `buildroot/license`) |
+| `--without-suggests` | | Do not include licenses for suggested packages |
+
+### Examples
+
+```bash
+# Dump licenses for the extensions you compiled
+spc dump-license --for-extensions="bcmath,openssl,curl"
+
+# Dump licenses for specific artifacts
+spc dump-license "php-src,openssl"
+
+# Write licenses to a custom directory
+spc dump-license --for-extensions="bcmath,openssl" --dump-dir=/tmp/licenses
+```
+
+## extract
+
+Extract downloaded artifacts to their target locations in the source tree.
+
+```bash
+spc extract [artifacts] [options]
+```
+
+`artifacts` (optional): Specific artifacts to extract, comma-separated (e.g. `"php-src,openssl,curl"`).
+
+### Options
+
+| Option | Short | Description |
+|---|---|---|
+| `--for-extensions=` | `-e` | Extract artifacts needed by the given extensions, e.g. `"openssl,mbstring"` |
+| `--for-libs=` | `-l` | Extract artifacts needed by the given libraries, e.g. `"libcares,openssl"` |
+| `--for-packages=` | | Extract artifacts needed by the given packages, e.g. `"php,libssl,libcurl"` |
+| `--without-suggests` | | Skip suggested packages when using `--for-extensions` |
+| `--source-only` | | Force extraction from source even if a pre-built binary is available |
+
+### Examples
+
+```bash
+# Extract artifacts for a set of extensions
+spc extract --for-extensions="bcmath,openssl,curl"
+
+# Extract specific artifacts
+spc extract "php-src,openssl"
+
+# Force source extraction
+spc extract --for-extensions="bcmath,openssl" --source-only
+```
+
+## install-pkg
+
+Install additional helper packages (e.g. UPX, toolchains). Aliases: `i`, `install-package`.
+
+```bash
+spc install-pkg [options]
+```
+
+`package` (required): The name of the package to install.
+
+All `download` options are available with the `--dl-` prefix.
+
+### Examples
+
+```bash
+# Install the UPX compressor
+spc install-pkg upx
+```
+
+## micro:combine
+
+Merge `micro.sfx` with a PHP or PHAR file to produce a standalone executable.
+
+```bash
+spc micro:combine [options]
+```
+
+`file` (required): Path to the PHP or PHAR file to combine.
+
+### Options
+
+| Option | Short | Description |
+|---|---|---|
+| `--with-micro=` | `-M` | Path to a custom `micro.sfx` (default: `buildroot/bin/micro.sfx`) |
+| `--with-ini-set=` | `-I` | Inject an INI setting into the binary (repeatable) |
+| `--with-ini-file=` | `-N` | Inject INI settings from a file |
+| `--output=` | `-O` | Output file name (default: `my-app`) |
+
+### Examples
+
+```bash
+# Combine a PHP script
+spc micro:combine app.php
+
+# Combine a PHAR with a custom output name
+spc micro:combine app.phar --output my-app
+
+# Inject INI settings
+spc micro:combine app.php -I "memory_limit=512M" -I "disable_functions=system"
+
+# Inject from an INI file
+spc micro:combine app.php --with-ini-file=custom.ini
+
+# Use a custom micro.sfx
+spc micro:combine app.php --with-micro=/path/to/micro.sfx
+```
+
+## reset
+
+Clean build directories and reset the build environment.
+
+```bash
+spc reset [options]
+```
+
+By default, removes `buildroot/` and `source/`.
+
+### Options
+
+| Option | Short | Description |
+|---|---|---|
+| `--with-pkgroot` | | Also remove the `pkgroot/` directory |
+| `--with-download` | | Also remove the `downloads/` directory |
+| `--yes` | `-y` | Skip the confirmation prompt |
+
+### Examples
+
+```bash
+# Clean build directories (will prompt for confirmation)
+spc reset
+
+# Also clear the download cache
+spc reset --with-download
+
+# Full clean without prompting
+spc reset --with-pkgroot --with-download --yes
+```
+
+## spc-config
+
+Output compiler and linker flags needed to link your own program against the PHP embed static library.
+
+```bash
+spc spc-config [extensions] [options]
+```
+
+`extensions` (optional): Comma-separated list of extensions to include.
+
+### Options
+
+| Option | Short | Description |
+|---|---|---|
+| `--with-libs=` | | Additional libraries to include, comma-separated |
+| `--with-packages=` | `-p` | Additional packages to include, comma-separated |
+| `--with-suggested-libs` | `-L` | Include suggested libraries |
+| `--with-suggests` | | Include all suggested packages |
+| `--with-suggested-exts` | `-E` | Include suggested extensions |
+| `--includes` | | Output only `-I` include paths (`CFLAGS`) |
+| `--libs` | | Output only `-L` and `-l` linker flags (`LDFLAGS` + `LIBS`) |
+| `--libs-only-deps` | | Output only `-l` dependency flags |
+| `--absolute-libs` | | Use absolute paths for library files |
+| `--no-php` | | Do not link against the PHP library |
+
+### Examples
+
+```bash
+# Output full compiler + linker flags
+spc spc-config "bcmath,openssl,curl"
+
+# Output include paths only
+spc spc-config "bcmath,openssl" --includes
+
+# Output linker flags only
+spc spc-config "bcmath,openssl" --libs
+
+# Use absolute library paths
+spc spc-config "bcmath,openssl" --libs --absolute-libs
+```
+Enter an interactive shell with StaticPHP's build environment pre-loaded (compiler wrappers, `buildroot/`, `pkgroot/` paths, etc. on `PATH`).
+
+```bash
+spc dev:shell
+```
+
+Useful for compiling small programs against `libphp.a` (embed SAPI) or inspecting the build environment manually.
diff --git a/docs/en/guide/deps-map.md b/docs/en/guide/deps-map.md
index 79100041c..1a66c91dd 100644
--- a/docs/en/guide/deps-map.md
+++ b/docs/en/guide/deps-map.md
@@ -1,26 +1,19 @@
---
-outline: 'deep'
+aside: false
---
-# Dependency Table
+# Dependency Map
-When compiling PHP, each extension and library has dependencies, which may be required or optional.
-You can choose whether to include these optional dependencies.
+This page lists all supported packages (extensions and libraries) together with their dependency relationships.
-For example, when compiling the `gd` extension under Linux,
-the `zlib,libpng` libraries and the `zlib` extension are forced to be compiled,
-while the `libavif,libwebp,libjpeg,freetype` libraries are optional libraries and will not be compiled by default
-unless specified by the `--with-libs=avif,webp,jpeg,freetype` option.
+- **Required Dependencies**: packages that are always built alongside the selected package.
+- **Suggested Dependencies**: packages that are not built by default; enable them with `--with-suggests` or by specifying them manually.
+- **Required By / Suggested By**: which other packages need or suggest this package.
-- For optional extensions (optional features of extensions), you need to specify them manually at compile time, for example, to enable igbinary support for Redis: `bin/spc build redis,igbinary`.
-- For optional libraries, you need to compile and specify them through the `--with-libs=XXX` option.
-- If you want to enable all optional extensions, you can use `bin/spc build redis --with-suggested-exts`.
-- If you want to enable all optional libraries, you can use `--with-suggested-libs`.
+Run the following command to generate the dependency data (source mode required):
-## Extension Dependency Table
+```bash
+bin/spc dev:gen-deps-data
+```
-
-
-## Library Dependency Table
-
-
\ No newline at end of file
+
diff --git a/docs/en/guide/env-vars.md b/docs/en/guide/env-vars.md
index 11cf93399..2fc50a656 100644
--- a/docs/en/guide/env-vars.md
+++ b/docs/en/guide/env-vars.md
@@ -1,25 +1,25 @@
-# Environment variables
+# Environment Variables
-All environment variables mentioned in the list on this page have default values unless otherwise noted.
+All environment variables mentioned in the list on this page have default values unless otherwise noted.
You can override the default values by setting these environment variables.
## Environment variables list
-Starting from version 2.3.5, we have centralized the environment variables in the `config/env.ini` file.
+StaticPHP centralizes environment variables in the `config/env.ini` file.
You can set environment variables by modifying this file.
-We divide the environment variables supported by static-php-cli into three types:
+We divide the environment variables supported by StaticPHP into three types:
-- Global internal environment variables: declared after static-php-cli starts, you can use `getenv()` to get them internally in static-php-cli, and you can override them before starting static-php-cli.
-- Fixed environment variables: declared after static-php-cli starts, you can only use `getenv()` to get them, but you cannot override them through shell scripts.
-- Config file environment variables: declared before static-php-cli build, you can set these environment variables by modifying the `config/env.ini` file or through shell scripts.
+- **Global internal environment variables**: declared after StaticPHP starts, you can use `getenv()` to get them internally in StaticPHP, and you can override them before starting StaticPHP.
+- **Fixed environment variables**: declared after StaticPHP starts, you can only use `getenv()` to get them, but you cannot override them through shell scripts.
+- **Config file environment variables**: declared before StaticPHP builds, you can set these environment variables by modifying the `config/env.ini` file or through shell scripts.
-You can read the comments for each parameter in [config/env.ini](https://github.com/crazywhalecc/static-php-cli/blob/main/config/env.ini) to understand its purpose.
+You can read the comments for each parameter in [config/env.ini](https://github.com/crazywhalecc/static-php-cli/blob/v3/config/env.ini) to understand its purpose.
## Custom environment variables
Generally, you don't need to modify any of the following environment variables as they are already set to optimal values.
-However, if you have special needs, you can set these environment variables to meet your needs
+However, if you have special needs, you can set these environment variables to meet your needs
(for example, you need to debug PHP performance under different compilation parameters).
If you want to use custom environment variables, you can use the `export` command in the terminal or set the environment variables directly before the command, for example:
@@ -27,25 +27,25 @@ If you want to use custom environment variables, you can use the `export` comman
```shell
# export first
export SPC_CONCURRENCY=4
-bin/spc build mbstring,pcntl --build-cli
+spc build:php "mbstring,pcntl" --build-cli
# or direct use
-SPC_CONCURRENCY=4 bin/spc build mbstring,pcntl --build-cli
+SPC_CONCURRENCY=4 spc build:php "mbstring,pcntl" --build-cli
```
Or, if you need to modify an environment variable for a long time, you can modify the `config/env.ini` file.
-`config/env.ini` is divided into three sections, `[global]` is globally effective, `[windows]`, `[macos]`, `[linux]` are only effective for the corresponding operating system.
+`config/env.ini` is divided into three sections: `[global]` is globally effective, `[windows]`, `[macos]`, `[linux]` are only effective for the corresponding operating system.
For example, if you need to modify the `./configure` command for compiling PHP, you can find the `SPC_CMD_PREFIX_PHP_CONFIGURE` environment variable in the `config/env.ini` file, and then modify its value.
-If your build conditions are more complex and require multiple `env.ini` files to switch,
+If your build conditions are more complex and require multiple `env.ini` files to switch,
we recommend that you use the `config/env.custom.ini` file.
-In this way, you can specify your environment variables by writing additional override items
+In this way, you can specify your environment variables by writing additional override items
without modifying the default `config/env.ini` file.
```ini
-; This is an example of `config/env.custom.ini` file,
+; This is an example of `config/env.custom.ini` file,
; we modify the `SPC_CONCURRENCY` and linux default CFLAGS passing to libs and PHP
[global]
SPC_CONCURRENCY=4
@@ -54,68 +54,3 @@ SPC_CONCURRENCY=4
SPC_DEFAULT_C_FLAGS="-O3"
```
-## Library environment variables (Unix only)
-
-Starting from 2.2.0, static-php-cli supports custom environment variables for all compilation dependent library commands of macOS, Linux, FreeBSD and other Unix systems.
-
-In this way, you can adjust the behavior of compiling dependent libraries through environment variables at any time.
-For example, you can set the optimization parameters for compiling the xxx library through `xxx_CFLAGS=-O0`.
-
-Of course, not every library supports the injection of environment variables.
-We currently provide three wildcard environment variables with the suffixes:
-
-- `_CFLAGS`: CFLAGS for the compiler
-- `_LDFLAGS`: LDFLAGS for the linker
-- `_LIBS`: LIBS for the linker
-
-The prefix is the name of the dependent library, and the specific name of the library is subject to `lib.json`.
-Among them, the library name with `-` needs to replace `-` with `_`.
-
-Here is an example of an optimization option that replaces the openssl library compilation:
-
-```shell
-openssl_CFLAGS="-O0"
-```
-
-The library name uses the same name listed in `lib.json` and is case-sensitive.
-
-::: tip
-When no relevant environment variables are specified, except for the following variables, the remaining values are empty by default:
-
-| var name | var default value |
-|-----------------------|-------------------------------------------------------------------------------------------------|
-| `pkg_config_CFLAGS` | macOS: `$SPC_DEFAULT_C_FLAGS -Wimplicit-function-declaration -Wno-int-conversion`, Other: empty |
-| `pkg_config_LDFLAGS` | Linux: `--static`, Other: empty |
-| `imagemagick_LDFLAGS` | Linux: `-static`, Other: empty |
-| `imagemagick_LIBS` | macOS: `-liconv`, Other: empty |
-| `ldap_LDFLAGS` | `-L$BUILD_LIB_PATH` |
-| `openssl_CFLAGS` | Linux: `$SPC_DEFAULT_C_FLAGS`, Other: empty |
-| others... | empty |
-:::
-
-The following table is a list of library names that support customizing the above three variables:
-
-| lib name |
-|-------------|
-| brotli |
-| bzip |
-| curl |
-| freetype |
-| gettext |
-| gmp |
-| imagemagick |
-| ldap |
-| libargon2 |
-| libavif |
-| libcares |
-| libevent |
-| openssl |
-
-::: tip
-Because adapting custom environment variables to each library is a particularly tedious task,
-and in most cases you do not need custom environment variables for these libraries,
-so we currently only support custom environment variables for some libraries.
-
-If the library you need to customize environment variables is not listed above,
-you can submit your request through [GitHub Issue](https://github.com/crazywhalecc/static-php-cli/issues).
-:::
diff --git a/docs/en/guide/extension-notes.md b/docs/en/guide/extension-notes.md
index 7096c0ee6..8df2ca937 100644
--- a/docs/en/guide/extension-notes.md
+++ b/docs/en/guide/extension-notes.md
@@ -1,7 +1,7 @@
# Extension Notes
-Because it is a static compilation, extensions will not compile 100% perfectly,
-and different extensions have different requirements for PHP and the environment,
+Because it is a static compilation, extensions will not compile 100% perfectly,
+and different extensions have different requirements for PHP and the environment,
which will be listed one by one here.
## curl
@@ -9,7 +9,7 @@ which will be listed one by one here.
HTTP3 support is not enabled by default, compile with `--with-libs="nghttp2,nghttp3,ngtcp2"` to enable HTTP3 support for PHP >= 8.4.
When using curl to request HTTPS, there may be an `error:80000002:system library::No such file or directory` error.
-For details on the solution, see [FAQ - Unable to use ssl](../faq/#unable-to-use-ssl).
+For details on the solution, see [FAQ](../faq/).
## phpmicro
@@ -19,7 +19,7 @@ For details on the solution, see [FAQ - Unable to use ssl](../faq/#unable-to-use
1. swoole >= 5.0 Only PHP >= 8.0 is supported.
2. swoole Currently, curl hooks are not supported for PHP 8.0.x (which may be fixed in the future).
-3. When compiling, if only `swoole` extension is included, the supported Swoole database coroutine hook will not be fully enabled.
+3. When compiling, if only `swoole` extension is included, the supported Swoole database coroutine hook will not be fully enabled.
If you need to use it, please add the corresponding `swoole-hook-xxx` extension.
4. The `zend_mm_heap corrupted` problem may occur in swoole under some extension combinations. The cause has not yet been found.
@@ -70,9 +70,9 @@ This extension contains an implementation of the coroutine environment for `pdo_
## gd
-1. gd Extension relies on more additional Graphics library. By default,
+1. gd Extension relies on more additional Graphics library. By default,
using `bin/spc build gd` directly will not support some Graphics library, such as `libjpeg`, `libavif`, etc.
-Currently, it supports four libraries: `freetype,libjpeg,libavif,libwebp`.
+Currently, it supports four libraries: `freetype,libjpeg,libavif,libwebp`.
Therefore, the following command can be used to introduce them into the gd library:
```bash
@@ -85,19 +85,19 @@ bin/spc build gd --with-libs=freetype,libjpeg,libavif,libwebp --build-cli
## oci8
-1. oci8 is an extension of the Oracle database, because the library on which the extension provided by Oracle does not provide a statically compiled version (`.a`) or source code,
+1. oci8 is an extension of the Oracle database, because the library on which the extension provided by Oracle does not provide a statically compiled version (`.a`) or source code,
and this extension cannot be compiled into php by static linking, so it cannot be supported.
## xdebug
-1. Xdebug is only buildable as a shared extension. On Linux, you'll need to use a SPC_TARGET like `native-native -dynamic` or `native-native-gnu`.
-2. When using Linux/glibc or macOS, you can compile Xdebug as a shared extension using --build-shared="xdebug".
- The compiled `./php` binary can be configured and run by specifying the INI, eg `./php -d 'zend_extension=/path/to/xdebug.so' your-code.php`.
+1. Xdebug is only buildable as a shared extension. On Linux, you'll need to use a `SPC_TARGET` with a glibc variant (e.g. `native-native-gnu.2.17`) instead of the default musl static target.
+2. When using Linux/glibc or macOS, you can compile Xdebug as a shared extension using `--build-shared="xdebug"`.
+ The compiled `./php` binary can be configured and run by specifying the INI, e.g. `./php -d 'zend_extension=/path/to/xdebug.so' your-code.php`.
## xml
-1. xml includes xml, xmlreader, xmlwriter, xsl, dom, simplexml, etc.
- When adding xml extensions, it is best to enable these extensions at the same time.
+1. xml includes xml, xmlreader, xmlwriter, xsl, dom, simplexml, etc.
+ When adding xml extensions, it is best to enable these extensions at the same time.
2. libxml is included in xml extension. Enabling xml is equivalent to enabling libxml.
## glfw
@@ -119,14 +119,14 @@ and this extension cannot be compiled into php by static linking, so it cannot b
pgsql 16.2 has fixed this bug, now it's working.
-When pgsql uses SSL connection, there may be `error:80000002:system library::No such file or directory` error,
-For details on the solution, see [FAQ - Unable to use ssl](../faq/#unable-to-use-ssl).
+When pgsql uses SSL connection, there may be `error:80000002:system library::No such file or directory` error.
+For details on the solution, see [FAQ](../faq/).
## openssl
When using openssl-based extensions (such as curl, pgsql and other network libraries),
there may be an `error:80000002:system library::No such file or directory` error.
-For details on the solution, see [FAQ - Unable to use ssl](../faq/#unable-to-use-ssl).
+For details on the solution, see [FAQ](../faq/).
## password-argon2
@@ -135,14 +135,14 @@ For details on the solution, see [FAQ - Unable to use ssl](../faq/#unable-to-use
## ffi
-1. Due to the limitation of musl libc's static linkage, you cannot use ffi because dynamic libraries cannot be loaded.
- If you need to use the ffi extension, see [Compile PHP with GNU libc](./build-with-glibc).
+1. Due to the limitation of musl libc's static linkage, you cannot use ffi because dynamic libraries cannot be loaded.
+ If you need to use the ffi extension, use a glibc-based `SPC_TARGET` (e.g. `native-native-gnu.2.17`). See [SAPI Reference](./sapi-reference) for details.
2. macOS supports the ffi extension, but errors will occur when some kernels do not contain debugging symbols.
3. Windows x64 supports the ffi extension.
## xhprof
-The xhprof extension consists of three parts: `xhprof_extension`, `xhprof_html`, `xhprof_libs`.
+The xhprof extension consists of three parts: `xhprof_extension`, `xhprof_html`, `xhprof_libs`.
Only `xhprof_extension` is included in the compiled binary.
If you need to use xhprof,
please download the source code from [pecl.php.net/package/xhprof](http://pecl.php.net/package/xhprof) and specify the `xhprof_libs` and `xhprof_html` paths for use.
@@ -166,3 +166,4 @@ Parallel is only supported on PHP 8.0 ZTS and above.
1. This is not technically an extension, but a library.
2. Building with `--with-libs="mimalloc"` on Linux or macOS will override the default allocator.
3. This is experimental for now, but is recommended in threaded environments.
+
diff --git a/docs/en/guide/extensions.md b/docs/en/guide/extensions.md
index 9ce53f63d..187543f7c 100644
--- a/docs/en/guide/extensions.md
+++ b/docs/en/guide/extensions.md
@@ -2,22 +2,16 @@
import SearchTable from "../../.vitepress/components/SearchTable.vue";
-# Extensions
+# Supported Extensions
-> - `yes`: supported
-> - _blank_: not supported yet, or WIP
-> - `no` with issue link: confirmed to be unavailable due to issue
-> - `partial` with issue link: supported but not perfect due to issue
+> - ✅: Supported
+> - blank: Not supported or not yet ported
::: tip
-If an extension you need is missing, you can create a [Feature Request](https://github.com/crazywhalecc/static-php-cli/issues).
+If an extension you need is missing, you can file a [feature request](https://github.com/crazywhalecc/static-php-cli/issues).
-Some extensions or libraries that the extension depends on will have some optional features.
-For example, the gd library optionally supports libwebp, freetype, etc.
-If you only use `bin/spc build gd --build-cli` they will not be included (static-php-cli defaults to the minimum dependency principle).
-
-For more information about optional libraries, see [Extensions, Library Dependency Map](./deps-map).
-For optional libraries, you can also select an extension from the [Command Generator](./cli-generator) and then select optional libraries.
+Some extensions or their library dependencies have optional features (e.g. gd can optionally use libwebp, freetype, etc.).
+Running `bin/spc build gd --build-cli` alone will not include them — StaticPHP follows a minimal-dependency principle by default.
:::
diff --git a/docs/en/guide/first-build.md b/docs/en/guide/first-build.md
new file mode 100644
index 000000000..b9e6a75a2
--- /dev/null
+++ b/docs/en/guide/first-build.md
@@ -0,0 +1,181 @@
+# Your First Build
+
+This page walks you through building a static PHP binary from scratch, end to end.
+
+::: tip
+If you installed spc as a pre-built binary, replace every `spc` in this page with `./spc` (or `.\spc.exe` on Windows).
+
+If you installed from source, use `bin/spc` instead.
+:::
+
+## Two Approaches
+
+StaticPHP supports two build workflows — pick the one that fits your situation:
+
+| Approach | When to use |
+|---|---|
+| `craft` (one-shot) | Everyday use, getting started quickly |
+| Step-by-step | Fine-grained control over the build pipeline |
+
+## Option 1: One-Shot Build with `craft` (Recommended)
+
+The `craft` command reads a `craft.yml` file and handles everything automatically — downloading dependencies, compiling libraries, and building PHP — in a single run.
+
+### Write craft.yml
+
+Create a `craft.yml` in your working directory and declare the PHP version, extensions, and target SAPIs:
+
+```yaml
+php-version: 8.4
+extensions: bcmath,posix,phar,zlib,openssl,curl,fileinfo,tokenizer
+sapi:
+ - cli
+ - micro
+```
+
+Not sure which extensions you need? Use the [command generator](./cli-generator) to produce a `craft.yml` automatically.
+
+### Run the Build
+
+```bash
+spc craft
+```
+
+The build pipeline runs in order: download dependencies → compile libraries → compile PHP. No interaction required.
+
+To see more detail, pass `-v`, `-vv`, or `-vvv`:
+
+```bash
+spc craft -v
+```
+
+### Inspect the Output
+
+On success, binaries land in `buildroot/bin/`:
+
+| SAPI | Output path |
+|---|---|
+| cli | `buildroot/bin/php` (Windows: `buildroot/bin/php.exe`) |
+| fpm | `buildroot/bin/php-fpm` |
+| micro | `buildroot/bin/micro.sfx` |
+| embed | `buildroot/lib/libphp.a` |
+| frankenphp | `buildroot/bin/frankenphp` |
+
+Give the CLI binary a quick smoke-test:
+
+```bash
+./buildroot/bin/php -v
+./buildroot/bin/php -m
+```
+
+## Option 2: Step-by-Step Build
+
+This approach lets you run download and compile as separate steps — useful when you want to cache downloads in CI and reuse them across builds.
+
+### Step 1: Download Dependencies
+
+```bash
+# Download only what the chosen extensions need (recommended)
+spc download --for-extensions="bcmath,posix,phar,zlib,openssl,curl,fileinfo,tokenizer" --with-php=8.4
+
+# Download by specific package names
+spc download "curl,openssl" --with-php=8.4
+```
+
+Downloads are cached in `downloads/` and reused across builds automatically.
+
+```bash
+# Slow connection? Increase parallelism and retries
+spc download --for-extensions="bcmath,openssl,curl" --parallel 10 --retry=3
+
+# Use pre-built binaries where available — skips compiling those dependencies
+spc download --for-extensions="bcmath,openssl,curl" --prefer-binary
+```
+
+### Step 2: Build PHP
+
+```bash
+# Build the cli SAPI
+spc build:php "bcmath,phar,zlib,openssl,curl,fileinfo,tokenizer" --build-cli
+
+# Build multiple SAPIs in one go
+spc build:php "bcmath,phar,zlib,openssl,curl" --build-cli --build-micro
+```
+
+#### Common Build Options
+
+| Option | Description |
+|---|---|
+| `--build-cli` | Build the cli SAPI |
+| `--build-fpm` | Build php-fpm (not available on Windows) |
+| `--build-micro` | Build micro.sfx |
+| `--build-embed` | Build the embed SAPI |
+| `--build-frankenphp` | Build FrankenPHP |
+| `--enable-zts` | Enable thread-safe (ZTS) mode |
+| `--no-strip` | Keep debug symbols; do not strip the binary |
+| `-I key=value` | Hard-compile an INI option into PHP |
+| `--with-upx-pack` | Compress output with UPX (run `spc install-pkg upx` first) |
+
+Example — baking in a larger memory limit and disabling the `system` function:
+
+```bash
+spc build:php "bcmath,pcntl,posix" --build-cli -I "memory_limit=4G" -I "disable_functions=system"
+```
+
+## Packaging a micro App
+
+Once you have `micro.sfx`, use `micro:combine` to bundle your PHP code into a single self-contained executable:
+
+```bash
+echo " hello.php
+spc micro:combine hello.php --output=hello
+./hello
+```
+
+Works with `.phar` files too, and you can inject INI settings at packaging time:
+
+```bash
+# Bundle a phar
+spc micro:combine your-app.phar --output=your-app
+
+# Inject INI via command-line options
+spc micro:combine your-app.phar --output=your-app -I "memory_limit=512M"
+
+# Inject INI from a file
+spc micro:combine your-app.phar --output=your-app -N /path/to/custom.ini
+```
+
+## Debugging and Rebuilding
+
+If a build fails or you want to trace what's happening, use `-v` / `-vv` / `-vvv`:
+
+```bash
+spc build:php "bcmath,openssl" --build-cli -vv
+```
+
+- `-v` shows `INFO`-level logs: which modules are running and what build commands are being executed.
+- `-vv` shows `DEBUG`-level logs: all internal debug output from StaticPHP.
+- `-vvv` shows `DEBUG`-level logs and also pipes the stdout of every shell command directly to your terminal.
+
+To wipe compiled artifacts and start fresh without re-downloading, run `reset`:
+
+```bash
+spc reset
+# Then rebuild
+spc build:php "bcmath,openssl" --build-cli
+```
+
+::: tip
+`reset` only removes `buildroot/` and `source/`. Your `downloads/` cache is preserved.
+Add `--with-download` if you also want to clear the download cache.
+:::
+
+If you're stuck, open an [Issue](https://github.com/static-php/static-php-cli/issues) and include your `craft.yml` (if any) and a zip of the `log/` directory.
+
+## What's Next
+
+- [PHP SAPI Reference](./sapi-reference) — Build options and usage guide for each PHP SAPI
+- [CLI Reference](./cli-reference) — Full documentation for every command and option
+- [Extensions](./extensions) — Browse supported extensions and their dependencies
+- [Troubleshooting](./troubleshooting) — Diagnose common build failures
+
diff --git a/docs/en/guide/index.md b/docs/en/guide/index.md
index 54e7840c5..1facd732b 100644
--- a/docs/en/guide/index.md
+++ b/docs/en/guide/index.md
@@ -1,50 +1,52 @@
# Guide
-Static php cli is a tool used to build statically compiled PHP binaries,
-currently supporting Linux and macOS systems.
-
-In the guide section, you will learn how to use static php cli to build standalone PHP programs.
-
-- [Build (local)](./manual-build)
-- [Build (GitHub Actions)](./action-build)
-- [Supported Extensions](./extensions)
-
-## Compilation Environment
-
-The following is the architecture support situation, where :gear: represents support for GitHub Action build,
-:computer: represents support for local manual build, and empty represents temporarily not supported.
-
-| | x86_64 | aarch64 |
-|---------|-------------------|-------------------|
-| macOS | :gear: :computer: | :gear: :computer: |
-| Linux | :gear: :computer: | :gear: :computer: |
-| Windows | :gear: :computer: | |
-| FreeBSD | :computer: | :computer: |
-
-Current supported PHP versions for compilation:
-
-> :warning: Partial support, there may be issues with new beta versions and old versions.
->
-> :heavy_check_mark: Supported
->
-> :x: Not supported
-
-| PHP Version | Status | Comment |
-|-------------|--------------------|-------------------------------------------------------------------------------------------------------------------------|
-| 7.2 | :x: | |
-| 7.3 | :x: | phpmicro and many extensions do not support 7.3, 7.4 versions |
-| 7.4 | :x: | phpmicro and many extensions do not support 7.3, 7.4 versions |
-| 8.0 | :warning: | PHP official has stopped maintaining 8.0, we no longer handle 8.0 related backport support |
-| 8.1 | :warning: | PHP official only provides security updates for 8.1, we no longer handle 8.1 related backport support after 8.5 release |
-| 8.2 | :heavy_check_mark: | |
-| 8.3 | :heavy_check_mark: | |
-| 8.4 | :heavy_check_mark: | |
-| 8.5 (beta) | :warning: | PHP 8.5 is currently in beta stage |
-
-> This table shows the support status of static-php-cli for building corresponding versions, not the PHP official support status for that version.
-
-## PHP Support Versions
-
-Currently, static-php-cli supports PHP versions 8.2 ~ 8.5, and theoretically supports PHP 8.1 and earlier versions, just select the earlier version when downloading.
-However, due to some extensions and special components that have stopped supporting earlier versions of PHP, static-php-cli will not explicitly support earlier versions.
-We recommend that you compile the latest PHP version possible for a better experience.
+::: warning
+You are reading the documentation for StaticPHP v3. The v2 version will be deprecated after the stable release of v3.
+The 3.0 version is currently in the alpha stage, and you can view the v2 documentation [here](https://static-php.github.io/v2-docs/).
+:::
+
+## What is StaticPHP?
+
+StaticPHP is a build tool that compiles the PHP interpreter together with any extensions you need into a single self-contained binary. The target system doesn't need PHP or any runtime libraries installed — just copy the binary and run it. Builds target Linux, macOS, and Windows.
+
+StaticPHP isn't limited to PHP. Built on the same infrastructure, it can also compile standalone static binaries for common tools like `curl`, `pkg-config`, and `htop` — no dependencies required on the target machine. Support for more tools (including `openssl` and other frequently-used CLI utilities) is planned.
+
+## Why bother with a static PHP binary?
+
+A typical PHP installation is tightly coupled to the system: you install PHP, then extensions, then spend time dealing with version mismatches across distros. A static binary sidesteps all of that — what you get is a single executable that runs on any machine of the same architecture, no setup required.
+
+Common use cases:
+
+- **Distributing CLI tools** — Ship tools like Composer, PHPStan, or your own CLI as a single file. Users don't need PHP installed.
+- **Leaner containers** — Replace a bloated `php:8.x` base image with a minimal image (or even `FROM scratch`) carrying just a static binary.
+- **Server applications** — Build a static binary with FPM or FrankenPHP baked in. Deployment becomes a file copy, with no dependency on the host environment.
+
+## phpmicro: ship PHP and your code as one file
+
+[phpmicro](https://micro.static-php.dev) is a third-party PHP SAPI that StaticPHP supports out of the box. It merges the PHP interpreter with your `.php` source or `.phar` archive into a single self-extracting executable (`.sfx`).
+
+```
+micro.sfx + your-app.phar = your-app # one file, zero dependencies
+```
+
+This is ideal for distributing PHP-based CLI tools: the end user just gets an ordinary executable with no idea PHP is involved.
+
+## Improving how you ship and deploy PHP projects
+
+**Drop the heavy Docker base image**
+
+The official `php:8.x` image can be hundreds of megabytes, most of which is just the PHP runtime. Swap it for a static PHP binary with a minimal base image — or `FROM scratch` — and you can get container sizes down to single-digit megabytes with noticeably faster startup times.
+
+**Ship PHP CLI tools like native binaries**
+
+Build your CLI with [symfony/console](https://symfony.com/doc/current/components/console.html) or [Laravel Zero](https://laravel-zero.com), bundle it into a `.phar` with [Box](https://github.com/box-project/box), then merge it with phpmicro. The result is a single distributable executable — the same experience users expect from Go or Rust tools, with no PHP runtime required on their end.
+
+**Single-file web apps with FrankenPHP**
+
+[FrankenPHP](https://frankenphp.dev) is a modern PHP app server with built-in HTTP/2, HTTP/3, and automatic HTTPS. StaticPHP can compile FrankenPHP together with your chosen extensions into one binary. The result is a complete web server in a single file — no Nginx, no PHP-FPM, just deploy and run.
+
+## Next steps
+
+- [Installation](./installation) — Get the StaticPHP build tool
+- [First Build](./first-build) — Full walkthrough: from downloading sources to a working executable
+- [CLI Reference](./cli-reference) — Every command and option, in one place
diff --git a/docs/en/guide/installation.md b/docs/en/guide/installation.md
new file mode 100644
index 000000000..f2df13e78
--- /dev/null
+++ b/docs/en/guide/installation.md
@@ -0,0 +1,121 @@
+# Installation
+
+## Requirements
+
+| Platform | Architecture | Notes |
+|---|---|---|
+| Linux | x86_64, aarch64 | Major distros supported (Alpine, Debian/Ubuntu, RHEL/CentOS, etc.) |
+| macOS | x86_64 (Intel), arm64 (Apple Silicon) | macOS 12 or later |
+| Windows | x86_64 | Windows 10 Build 17063 or later |
+
+::: tip
+Both glibc-based distros (Debian, Ubuntu, Arch, etc.) and musl-based ones (Alpine) are supported on Linux.
+The `doctor` command will detect your environment and guide you through installing the right toolchain if needed.
+:::
+
+Pick the installation method that fits your use case:
+
+| Method | Best for |
+|---|---|
+| Pre-built binary | Most users — download and run, no dependencies |
+| From source | Contributors, or anyone who needs to modify core build logic |
+| Vendor mode | Integrating StaticPHP into an existing PHP project |
+
+## Pre-built binary
+
+`spc` has no runtime dependencies — download the binary for your platform and it's ready to go.
+
+> Fun fact: `spc` itself is a static PHP binary built with StaticPHP. We use StaticPHP to build StaticPHP's own build tool.
+
+```shell
+# Linux x86_64
+curl -#fSL https://dl.static-php.dev/v3/spc-bin/latest/spc-linux-x86_64 -o spc
+# Linux arm64
+curl -#fSL https://dl.static-php.dev/v3/spc-bin/latest/spc-linux-aarch64 -o spc
+# macOS x86_64 (Intel)
+curl -#fSL https://dl.static-php.dev/v3/spc-bin/latest/spc-macos-x86_64 -o spc
+# macOS arm64 (Apple Silicon)
+curl -#fSL https://dl.static-php.dev/v3/spc-bin/latest/spc-macos-aarch64 -o spc
+# Windows x86_64 (PowerShell)
+curl.exe -#fSL https://dl.static-php.dev/v3/spc-bin/latest/spc-windows-x86_64.exe -o spc.exe
+```
+
+On Linux and macOS, mark the binary as executable before running it:
+
+```bash
+chmod +x spc && ./spc --version
+```
+
+## From source
+
+This is the right path if you want to contribute to StaticPHP, or need to modify the core registry and build scripts. You'll need PHP >= 8.4, Composer, and the `mbstring,posix,pcntl,iconv,phar,zlib` extensions.
+
+```bash
+git clone https://github.com/crazywhalecc/static-php-cli.git --branch v3
+cd static-php-cli
+composer install
+```
+
+If you don't have PHP or Composer installed, use the bundled setup script to install a self-contained runtime:
+
+::: code-group
+```bash [Linux / macOS]
+bin/setup-runtime
+```
+```powershell [Windows]
+.\bin\setup-runtime.ps1
+.\bin\setup-runtime.ps1 add-path # add runtime/ to PATH
+```
+:::
+
+The script downloads `php` and `composer` into a `runtime/` subdirectory. You then have two options:
+
+1. **Call them directly** (no PATH changes needed):
+ ```bash
+ runtime/php bin/spc --help
+ runtime/php runtime/composer install
+ ```
+
+2. **Add `runtime/` to your PATH** so you can use `php`, `composer`, and `bin/spc` without prefixes:
+ ```bash
+ export PATH="/path/to/static-php-cli/runtime:$PATH"
+ # Add this to ~/.bashrc or ~/.zshrc to make it permanent
+ ```
+
+::: tip
+In regions with restricted access to GitHub or getcomposer.org, pass `--mirror china` to use a mirror:
+```bash
+bin/setup-runtime --mirror china
+```
+:::
+
+## Vendor mode
+
+If you already have a PHP project and want to call StaticPHP's build APIs directly, or use a custom registry to support private libraries and extensions, pull it in as a Composer dependency:
+
+```bash
+composer require crazywhalecc/static-php-cli
+```
+
+See the [Vendor Mode guide](../develop/vendor-mode/) for details.
+
+## Verify your build environment
+
+> **Vendor mode users can skip this step.**
+
+Once installed, run `doctor` to check that your system has the required build tools (cmake, make, a C compiler, etc.):
+
+```bash
+# Using the spc binary
+./spc doctor
+# From source
+bin/spc doctor
+```
+
+If anything is missing, `--auto-fix` will attempt to install it for you:
+
+```bash
+./spc doctor --auto-fix
+```
+
+Once `doctor` reports everything is good, head over to [First Build](./first-build).
diff --git a/docs/en/guide/manual-build.md b/docs/en/guide/manual-build.md
deleted file mode 100644
index 28f0ec87e..000000000
--- a/docs/en/guide/manual-build.md
+++ /dev/null
@@ -1,703 +0,0 @@
----
-outline: 'deep'
----
-
-# Build (Linux, macOS, FreeBSD)
-
-This section covers the build process for Linux, macOS, and FreeBSD. If you want to build on Windows,
-also need to read [Build on Windows](./build-on-windows).
-
-### Build locally (using SPC binary) (recommended)
-
-This project provides a binary file of static-php-cli.
-You can directly download the binary file of the corresponding platform and then use it to build static PHP.
-Currently, the platforms supported by `spc` binary are Linux and macOS.
-
-Here's how to download from self-hosted server:
-
-```bash
-# Download from self-hosted nightly builds (sync with main branch)
-# For Linux x86_64
-curl -fsSL -o spc https://dl.static-php.dev/static-php-cli/spc-bin/nightly/spc-linux-x86_64
-# For Linux aarch64
-curl -fsSL -o spc https://dl.static-php.dev/static-php-cli/spc-bin/nightly/spc-linux-aarch64
-# macOS x86_64 (Intel)
-curl -fsSL -o spc https://dl.static-php.dev/static-php-cli/spc-bin/nightly/spc-macos-x86_64
-# macOS aarch64 (Apple)
-curl -fsSL -o spc https://dl.static-php.dev/static-php-cli/spc-bin/nightly/spc-macos-aarch64
-# Windows (x86_64, win10 build 17063 or later)
-curl.exe -fsSL -o spc.exe https://dl.static-php.dev/static-php-cli/spc-bin/nightly/spc-windows-x64.exe
-
-# Add execute perm (Linux and macOS only)
-chmod +x ./spc
-
-# Run (Linux and macOS)
-./spc --version
-# Run (Windows powershell)
-.\spc.exe --version
-```
-
-> If you are using the packaged `spc` binary, you will need to replace the leading `bin/spc` with `./spc` in all the commands below.
-
-### Build locally (using source code)
-
-If you have problems using the spc binary, or if you need to modify the static-php-cli source code, download static-php-cli from the source code.
-
-Currently, it supports building on macOS and Linux.
-macOS supports the latest version of the operating system and two architectures,
-while Linux supports Debian and derivative distributions, as well as Alpine Linux.
-
-Because this project itself is developed using PHP,
-it is also necessary to install PHP on the system during compilation.
-This project also provides static binary PHP suitable for this project,
-which can be selected and used according to actual situations.
-
-```bash
-# clone repo
-git clone https://github.com/crazywhalecc/static-php-cli.git --depth=1
-cd static-php-cli
-
-# You need to install the PHP environment first before running Composer and this project. The installation method can be referred to below.
-composer update
-```
-
-### Use Precompiled Static PHP Binaries
-
-If you don't want to use Docker and install PHP in the system,
-you can directly download the php binary cli program compiled by this project itself. The usage process is as follows:
-
-Deploy the environment using the command, the command will download a static php-cli binary from [self-hosted server](https://dl.static-php.dev/static-php-cli/).
-Next, it will automatically download Composer from [getcomposer](https://getcomposer.org/download/latest-stable/composer.phar) or [Aliyun mirror](https://mirrors.aliyun.com/composer/composer.phar).
-
-::: tip
-Using precompiled static PHP binaries is currently only supported on Linux and macOS.
-The FreeBSD environment is currently not supported due to the lack of an automated build environment.
-:::
-
-```bash
-bin/setup-runtime
-
-# For users with special network environments such as mainland China, you can use mirror sites (aliyun) to speed up the download speed
-bin/setup-runtime --mirror china
-```
-
-This script will download two files in total: `bin/php` and `bin/composer`. After the download is complete, there are two ways to use it:
-
-1. Add the `bin/` directory to the PATH: `export PATH="/path/to/your/static-php-cli/bin:$PATH"`, after adding the path,
-it is equivalent to installing PHP in the system, you can directly Use commands such as `composer`, `php -v`, or directly use `bin/spc`.
-2. Direct call, such as executing static-php-cli command: `bin/php bin/spc --help`, executing Composer: `bin/php bin/composer update`.
-
-### Use Docker
-
-If you don't want to install PHP and Composer runtime environment on your system, you can use the built-in Docker environment build script.
-
-```bash
-# To use directly, replace `bin/spc` with `bin/spc-alpine-docker` in all used commands
-bin/spc-alpine-docker
-```
-
-The first time the command is executed, `docker build` will be used to build a Docker image.
-The default built Docker image is the `x86_64` architecture, and the image name is `cwcc-spc-x86_64`.
-
-If you want to build `aarch64` static-php-cli in `x86_64` environment,
-you can use qemu to emulate the arm image to run Docker, but the speed will be very slow.
-Use command: `SPC_USE_ARCH=aarch64 bin/spc-alpine-docker`.
-
-If it prompts that sudo is required to run after running,
-execute the following command once to grant static-php-cli permission to execute sudo:
-
-```bash
-export SPC_USE_SUDO=yes
-```
-
-### Use System PHP
-
-Below are some example commands for installing PHP and Composer in the system.
-It is recommended to search for the specific installation method yourself or ask the AI search engine to obtain the answer,
-which will not be elaborated here.
-
-```bash
-# [macOS], need install Homebrew first. See https://brew.sh/
-# Remember change your composer executable path. For M1/M2 Chip mac, "/opt/homebrew/bin/", for Intel mac, "/usr/local/bin/". Or add it to your own path.
-brew install php wget
-wget https://getcomposer.org/download/latest-stable/composer.phar -O /path/to/your/bin/composer && chmod +x /path/to/your/bin/composer
-
-# [Debian], you need to make sure your php version >= 8.1 and composer >= 2.0
-sudo apt install php-cli composer php-tokenizer
-
-# [Alpine]
-apk add bash file wget xz php81 php81-common php81-pcntl php81-tokenizer php81-phar php81-posix php81-xml composer
-```
-
-::: tip
-Currently, some versions of Ubuntu install older PHP versions,
-so no installation commands are provided. If necessary, it is recommended to add software sources such as ppa first,
-and then install the latest version of PHP and tokenizer, XML, and phar extensions.
-
-Older versions of Debian may have an older (<= 7.4) version of PHP installed by default, it is recommended to upgrade Debian first.
-:::
-
-## Build with craft (recommended)
-
-Using `bin/spc craft`, you can use a configuration file and a command to automatically check the environment, download source code, build dependency libraries, build PHP and extensions, etc.
-
-You need to write a `craft.yml` file and save it in the current working directory. `craft.yml` can be generated by [command generator](./cli-generator) or written manually.
-
-For manual writing, please refer to the comments in [craft.yml configuration](../develop/craft-yml.md) to write it.
-Let's assume that you compile an extension combination and choose PHP 8.4, outputting `cli` and `fpm`:
-
-```yaml
-# path/to/craft.yml
-php-version: 8.4
-extensions: bcmath,posix,phar,zlib,openssl,curl,fileinfo,tokenizer
-sapi:
- - cli
- - fpm
-```
-
-Then use the `bin/spc craft` command to compile:
-
-```bash
-bin/spc craft --debug
-```
-
-If the build is successful, you will see the `buildroot/bin` directory in the current directory, which contains the compiled PHP binary file, or the corresponding SAPI.
-
-- cli: The build result is `buildroot/bin/php.exe` on Windows and `buildroot/bin/php` on other platforms.
-- fpm: The build result is `buildroot/bin/php-fpm`.
-- micro: The build result is `buildroot/bin/micro.sfx`. If you need to further package it with PHP code, please refer to [Packaging micro binary](./manual-build#command-micro-combine).
-- embed: See [Using embed](./manual-build#embed-usage).
-- frankenphp: The build result is `buildroot/bin/frankenphp`.
-
-If the build fails, you can use the `--debug` parameter to view detailed error information,
-or use the `--with-clean` to clear the old compilation results and recompile.
-
-If the build still fails to use the above method, please submit an issue and attach your `craft.yml` and `./log` archive.
-
-## Step-by-step build command
-
-If you have customized requirements, or the need to download and compile PHP and dependent libraries separately, you can use the `bin/spc` command to execute step by step.
-
-### Command download - Download dependency packages
-
-Use the command `bin/spc download` to download the source code required for compilation,
-including php-src and the source code of various dependent libraries.
-
-```bash
-# Download all dependencies, defaults to php 8.4
-bin/spc download --all
-
-# Download all dependent packages, and specify the main version of PHP to download, optional: 8.1, 8.2, 8.3, 8.4
-# Also supports specific version of php release: 8.3.10, 8.2.22, etc.
-bin/spc download --all --with-php=8.3
-
-# Show download progress bar while downloading (curl)
-bin/spc download --all --debug
-
-# Delete old download data
-bin/spc download --clean
-
-# Download specified dependencies
-bin/spc download php-src,micro,zstd,ext-zstd
-
-# Download only extensions and libraries to be compiled (use extensions, including suggested libraries)
-bin/spc download --for-extensions=openssl,swoole,zip,pcntl,zstd
-
-# Download resources, prefer to download dependencies with pre-built packages (reduce the time to compile dependencies)
-bin/spc download --for-extensions="curl,pcntl,xml,mbstring" --prefer-pre-built
-
-# Download only the extensions and dependent libraries to be compiled (use extensions, excluding suggested libraries)
-bin/spc download --for-extensions=openssl,swoole,zip,pcntl --without-suggestions
-
-# Download only libraries to be compiled (use libraries, including suggested libraries and required libraries, can use --for-extensions together)
-bin/spc download --for-libs=liblz4,libevent --for-extensions=pcntl,rar,xml
-
-# Download only libraries to be compiled (use libraries, excluding suggested libraries)
-bin/spc download --for-libs=liblz4,libevent --without-suggestions
-
-# When downloading sources, ignore some source caches (always force download, e.g. switching PHP version)
-bin/spc download --for-extensions=curl,pcntl,xml --ignore-cache-sources=php-src --with-php=8.3.10
-
-# Set retry times (default is 0)
-bin/spc download --all --retry=2
-```
-
-If the network in your area is not good, or the speed of downloading the dependency package is too slow,
-you can download `download.zip` which is packaged regularly every week from GitHub Action,
-and use the command to directly use the zip archive as a dependency.
-
-Dependent packages can be downloaded locally from [Action](https://github.com/static-php/static-php-cli-hosted/actions/workflows/download-cache.yml).
-Enter Action and select the latest Workflow that has been successfully run, and download `download-files-x.y`.
-
-```bash
-bin/spc download --from-zip=/path/to/your/download.zip
-```
-
-If a source cannot be downloaded all the time, or you need to download some specific version of the package,
-such as downloading the beta version of PHP, the old version of the library, etc.,
-you can use the parameter `-U` or `--custom-url` to rewrite the download link,
-Make the downloader force the link you specify to download packages from this source.
-The method of use is `{source-name}:{url}`, which can rewrite the download URLs of multiple libraries at the same time.
-Also, it is available when downloading with the `--for-extensions` option.
-
-
-```bash
-# Specifying to download a alpha version of PHP 8.5
-bin/spc download --all -U "php-src:https://downloads.php.net/~edorian/php-8.5.0alpha2.tar.xz"
-
-# Specifying to download an older version of the curl library
-bin/spc download --all -U "curl:https://curl.se/download/curl-7.88.1.tar.gz"
-```
-
-If the source you download is not a link, but a git repository, you can use `-G` or `--custom-git` to rewrite the download link,
-so that the downloader can force the use of the specified git repository to download packages from this source.
-The usage method is `{source-name}:{branch}:{url}`, which can rewrite the download link of multiple libraries at the same time.
-It is also available when downloading with the `--for-extensions` option.
-
-```bash
-# Specifying to download the source code of the PHP extension from the specified branch of the git repository
-bin/spc download --for-extensions=redis -G "php-src:master:https://github.com/php/php-src.git"
-
-# Download the latest code from the master branch of the swoole-src repository instead of PECL release version
-bin/spc download --for-extensions=swoole -G "swoole:master:https://github.com/swoole/swoole-src.git"
-```
-
-### Command - doctor
-
-If you can run `bin/spc` normally but cannot compile static PHP or dependent libraries normally,
-you can run `bin/spc doctor` first to check whether the system itself lacks dependencies.
-
-```bash
-# Quick check
-bin/spc doctor
-
-# Quickly check and fix when it can be automatically repaired (use package management to install dependent packages, only support the above-mentioned operating systems and distributions)
-bin/spc doctor --auto-fix
-```
-
-### Command - build
-
-Use the build command to start building the static php binary.
-Before executing the `bin/spc build` command, be sure to use the `download` command to download sources.
-It is recommended to use `doctor` to check the environment.
-
-#### Basic build
-
-You need to go to [Extension List](./extensions) or [Command Generator](./cli-generator) to select the extension you want to add,
-and then use the command `bin/spc build` to compile.
-You need to specify a compilation target, choose from the following parameters:
-
-- `--build-cli`: Build a cli sapi (command line interface, which can execute PHP code on the command line)
-- `--build-fpm`: Build a fpm sapi (php-fpm, used in conjunction with other traditional fpm architecture software such as nginx)
-- `--build-cgi`: Build a cgi sapi (cgi, rarely used)
-- `--build-micro`: Build a micro sapi (used to build a standalone executable binary containing PHP code)
-- `--build-embed`: Build an embed sapi (used to embed into other C language programs)
-- `--build-frankenphp`: Build a [FrankenPHP](https://github.com/php/frankenphp) executable
-- `--build-all`: build all above sapi
-
-```bash
-# Compile PHP with bcmath,curl,openssl,ftp,posix,pcntl extensions, the compilation target is cli
-bin/spc build bcmath,curl,openssl,ftp,posix,pcntl --build-cli
-
-# Compile PHP with phar,curl,posix,pcntl,tokenizer extensions, compile target is micro
-bin/spc build phar,curl,posix,pcntl,tokenizer --build-micro
-```
-
-::: tip
-If you need to repeatedly build and debug, you can delete the `buildroot/` and `source/` directories so that you can re-extract and build all you need from the downloaded source code package:
-
-```shell
-# remove
-rm -rf buildroot source
-# build again
-bin/spc build bcmath,curl,openssl,ftp,posix,pcntl --build-cli
-```
-:::
-
-::: tip
-If you want to build multiple versions of PHP and don't want to build other dependent libraries repeatedly each time,
-you can use `switch-php-version` to quickly switch to another version and compile after compiling one version:
-
-```shell
-# switch to 8.4
-bin/spc switch-php-version 8.4
-# build
-bin/spc build bcmath,curl,openssl,ftp,posix,pcntl --build-cli
-# switch to 8.1
-bin/spc switch-php-version 8.1
-# build
-bin/spc build bcmath,curl,openssl,ftp,posix,pcntl --build-cli
-```
-:::
-
-#### Build Options
-
-During the compilation process, in some special cases,
-the compiler and the content of the compilation directory need to be intervened.
-You can try to use the following commands:
-
-- `--cc=XXX`: Specifies the execution command of the C language compiler (Linux default `musl-gcc` or `gcc`, macOS default `clang`)
-- `--cxx=XXX`: Specifies the execution command of the C++ language compiler (Linux defaults to `g++`, macOS defaults to `clang++`)
-- `--with-clean`: clean up old make files before compiling PHP
-- `--enable-zts`: Make compiled PHP thread-safe version (default is NTS version)
-- `--no-strip`: Do not run `strip` after compiling the PHP library to trim the binary file to reduce its size
-- `--with-libs=XXX,YYY`: Compile the specified dependent library before compiling PHP, and activate some extended optional functions (such as libavif of the gd library, etc.)
-- `--with-config-file-path=XXX`: Set the path in which to look for `php.ini` (Check [here](../faq/index.html#what-is-the-path-of-php-ini) for default paths)
-- `--with-config-file-scan-dir=XXX`: Set the directory to scan for `.ini` files after reading `php.ini` (Check [here](../faq/index.html#what-is-the-path-of-php-ini) for default paths)
-- `-I xxx=yyy`: Hard compile INI options into PHP before compiling (support multiple options, alias is `--with-hardcoded-ini`)
-- `--with-micro-fake-cli`: When compiling micro, let micro's `PHP_SAPI` pretend to be `cli` (for compatibility with some programs that check `PHP_SAPI`)
-- `--disable-opcache-jit`: Disable opcache jit (enabled by default)
-- `-P xxx.php`: Inject external scripts during static-php-cli compilation (see **Inject external scripts** below for details)
-- `--without-micro-ext-test`: After building micro.sfx, do not test the running results of different extensions in micro.sfx
-- `--with-suggested-exts`: Add `ext-suggests` as dependencies when compiling
-- `--with-suggested-libs`: Add `lib-suggests` as dependencies when compiling
-- `--with-upx-pack`: Use UPX to reduce the size of the binary file after compilation (you need to use `bin/spc install-pkg upx` to install upx first)
-- `--build-shared=XXX,YYY`: compile the specified extension into a shared library (the default is to compile into a static library)
-
-For hardcoding INI options, it works for cli, micro, embed sapi. Here is a simple example where we preset a larger `memory_limit` and disable the `system` function:
-
-```bash
-bin/spc build bcmath,pcntl,posix --build-all -I "memory_limit=4G" -I "disable_functions=system"
-```
-
-## Debug
-
-If you encounter problems during the compilation process, or want to view each executing shell command,
-you can use `--debug` to enable debug mode and view all terminal logs:
-
-```bash
-bin/spc build mysqlnd,pdo_mysql --build-all --debug
-```
-
-## Command - micro:combine
-
-Use the `micro:combine` command to build the compiled `micro.sfx` and your code (`.php` or `.phar` file) into an executable binary.
-You can also use this command to directly build a micro binary injected with ini configuration.
-
-::: tip
-Injecting ini configuration refers to adding a special structure after micro.sfx to save ini configuration items before combining micro.sfx with PHP source code.
-
-micro.sfx can identify the INI file header through a special byte, and the micro can be started with INI through the INI file header.
-
-The original wiki of this feature is in [phpmicro - Wiki](https://github.com/easysoft/phpmicro/wiki/INI-settings), and this feature may change in the future.
-:::
-
-The following is the general usage, directly packaging the php source code into a file:
-
-```bash
-# Before doing the packaging process, you should use `build --build-micro` to compile micro.sfx
-echo " a.php
-bin/spc micro:combine a.php
-
-# Just use it
-./my-app
-```
-
-You can use the following options to specify the file name to be output, and you can also specify micro.sfx in other paths for packaging.
-
-```bash
-# specify the output filename
-bin/spc micro:combine a.php --output=custom-bin
-# Use absolute path
-bin/spc micro:combine a.php -O /tmp/my-custom-app
-
-# Specify micro.sfx in other locations for packaging
-bin/spc micro:combine a.app --with-micro=/path/to/your/micro.sfx
-```
-
-If you want to inject ini configuration items, you can use the following parameters to add ini to the executable file from a file or command line option.
-
-```bash
-# Specified using command-line options (-I is shorthand for --with-ini-set)
-bin/spc micro:combine a.php -I "a=b" -I "foo=bar"
-
-# Use ini file specification (-N is shorthand for --with-ini-file)
-bin/spc micro:combine a.php -N /path/to/your/custom.ini
-```
-
-::: warning
-Note, please do not directly use the PHP source code or the `php.ini` file in the system-installed PHP,
-it is best to manually write an ini configuration file that you need, for example:
-
-```ini
-; custom.ini
-curl.cainfo=/path/to/your/cafile.pem
-memory_limit=1G
-```
-
-The ini injection of this command is achieved by appending a special structure after micro.sfx,
-which is different from the function of inserting hard-coded INI during compilation.
-:::
-
-If you want to package phar, just replace `a.php` with the packaged phar file.
-But please note that micro.sfx under phar needs extra attention to the path problem, see [Developing - Phar directory issue](../develop/structure#phar-application-directory-issue).
-
-## Command - extract
-
-Use the command `bin/spc extract` to unpack and copy the source code required for compilation,
-including php-src and the source code of various dependent libraries (you need to specify the name of the library to be unpacked).
-
-For example, after we have downloaded sources, we want to distribute and execute the build process,
-manually unpack and copy the package to a specified location, and we can use commands.
-
-```bash
-# Unzip the downloaded compressed package of php-src and libxml2, and store the decompressed source code in the source directory
-bin/spc extract php-src,libxml2
-```
-
-## Command - dump-extensions
-
-Use the command `bin/spc dump-extensions` to export required extensions of the current project.
-
-```bash
-# Print the extension list of the project, pass in the root directory of the project containing composer.json
-bin/spc dump-extensions /path/to/your/project/
-
-# Print the extension list of the project, excluding development dependencies
-bin/spc dump-extensions /path-to/tour/project/ --no-dev
-
-# Output in the extension list format acceptable to the spc command (comma separated)
-bin/spc dump-extensions /path-to/tour/project/ --format=text
-
-# Output as a JSON list
-bin/spc dump-extensions /path-to/tour/project/ --format=json
-
-# When the project does not have any extensions, output the specified extension combination instead of returning failure
-bin/spc dump-extensions /path-to/your/project/ --no-ext-output=mbstring,posix,pcntl,phar
-
-# Do not exclude extensions not supported by spc when outputting
-bin/spc dump-extensions /path/to/your/project/ --no-spc-filter
-```
-It should be noted that the project directory must contain the `vendor/installed.json` and `composer.lock` files, otherwise they cannot be found normally.
-
-## Dev Command - dev
-
-Debug commands refer to a collection of commands that can assist in outputting some information
-when you use static-php-cli to build PHP or modify and enhance the static-php-cli project itself.
-
-- `dev:extensions`: output all currently supported extension names, or output the specified extension information
-- `dev:php-version`: output the currently compiled PHP version (by reading `php_version.h`)
-- `dev:sort-config`: Sort the list of configuration files in the `config/` directory in alphabetical order
-- `dev:lib-ver `: Read the version from the source code of the dependency library (only available for specific dependency libraries)
-- `dev:ext-ver `: Read the corresponding version from the source code of the extension (only available for specific extensions)
-- `dev:pack-lib `: Package the specified library into a tar.gz file (maintainer only)
-- `dev:gen-ext-docs`: Generate extension documentation (maintainer only)
-
-```bash
-# output all extensions information
-bin/spc dev:extensions
-
-# Output the meta information of the specified extension
-bin/spc dev:extensions mongodb,curl,openssl
-
-# Output the specified columns
-# Available column name: lib-depends, lib-suggests, ext-depends, ext-suggests, unix-only, type
-bin/spc dev:extensions --columns=lib-depends,type,ext-depends
-
-# Output the currently compiled PHP version
-# You need to decompress the downloaded PHP source code to the source directory first
-# You can use `bin/spc extract php-src` to decompress the source code separately
-bin/spc dev:php-version
-
-# Sort the configuration files in the config/ directory in alphabetical order (e.g. ext.json)
-bin/spc dev:sort-config ext
-```
-
-## Command - install-pkg
-
-Use the command `bin/spc install-pkg` to download some precompiled or closed source tools and install them into the `pkgroot` directory.
-
-When `bin/spc doctor` automatically repairs the Windows environment, tools such as nasm and perl will be downloaded, and the installation process of `install-pkg` will also be used.
-
-Here is an example of installing the tool:
-
-- Download and install UPX (Linux and Windows only): `bin/spc install-pkg upx`
-- Download and install nasm (Windows only): `bin/spc install-pkg nasm`
-- Download and install go-xcaddy: `bin/spc install-pkg go-xcaddy`
-
-## Command - del-download
-
-In some cases, you need to delete single or multiple specified download source files and re-download them, such as switching PHP versions.
-The `bin/spc del-download` command is provided after the `2.1.0-beta.4` version. Specified source files can be deleted.
-
-Deletes downloaded source files containing precompiled packages and source code named as keys in `source.json` or `pkg.json`. Here are some examples:
-
-- Delete the old PHP source code and switch to download the 8.3 version: `bin/spc del-download php-src && bin/spc download php-src --with-php=8.3`
-- Delete the download file of redis extension: `bin/spc del-download redis`
-- Delete the downloaded musl-toolchain x86_64: `bin/spc del-download musl-toolchain-x86_64-linux`
-
-## Inject External Script
-
-Injecting external scripts refers to inserting one or more scripts during the static-php-cli compilation process
-to more flexibly support parameter modifications and source code patches in different environments.
-
-Under normal circumstances, this function mainly solves the problem that the patch cannot be modified
-by modifying the static-php-cli code when compiling with `spc` binary.
-
-There is another situation: your project directly depends on the `crazywhalecc/static-php-cli` repository and is synchronized with main branch,
-but some proprietary modifications are required, and these feature are not suitable for merging into the main branch.
-
-In view of the above situation, in the official version 2.0.0, static-php-cli has added multiple event trigger points.
-You can write an external `xx.php` script and pass it in through the command line parameter `-P` and execute.
-
-When writing to inject external scripts, the methods you will use are `builder()` and `patch_point()`.
-Among them, `patch_point()` obtains the name of the current event, and `builder()` obtains the BuilderBase object.
-
-Because the incoming patch point does not distinguish between events,
-you must write the code you want to execute in `if(patch_point() === 'your_event_name')`,
-otherwise it will be executed repeatedly in other events.
-
-The following are the supported `patch_point` event names and corresponding locations:
-
-| Event name | Event description |
-|------------------------------|----------------------------------------------------------------------------------------------------|
-| before-libs-extract | Triggered before the dependent libraries extracted |
-| after-libs-extract | Triggered after the compiled dependent libraries extracted |
-| before-php-extract | Triggered before PHP source code extracted |
-| after-php-extract | Triggered after PHP source code extracted |
-| before-micro-extract | Triggered before phpmicro extract |
-| after-micro-extract | Triggered after phpmicro extracted |
-| before-exts-extract | Triggered before the extension (to be compiled) extracted to the PHP source directory |
-| after-exts-extract | Triggered after the extension extracted to the PHP source directory |
-| before-library[*name*]-build | Triggered before the library named `name` is compiled (such as `before-library[postgresql]-build`) |
-| after-library[*name*]-build | Triggered after the library named `name` is compiled |
-| before-php-buildconf | Triggered before compiling PHP command `./buildconf` |
-| before-php-configure | Triggered before compiling PHP command `./configure` |
-| before-php-make | Triggered before compiling PHP command `make` |
-| before-sanity-check | Triggered after compiling PHP but before running extended checks |
-
-The following is a simple example of temporarily modifying the PHP source code.
-Enable the CLI function to search for the `php.ini` configuration in the current working directory:
-
-```php
-// a.php
-php_ini_ignore_cwd = 1;',
- 'sapi_module->php_ini_ignore_cwd = 0;'
- );
-}
-```
-
-```bash
-bin/spc build mbstring --build-cli -P a.php
-# Write in ./
-echo 'memory_limit=8G' > ./php.ini
-```
-
-```
-$ buildroot/bin/php -i | grep Loaded
-Loaded Configuration File => /Users/jerry/project/git-project/static-php-cli/php.ini
-
-$ buildroot/bin/php -i | grep memory
-memory_limit => 8G => 8G
-```
-
-For the objects, methods and interfaces supported by static-php-cli, you can read the source code. Most methods and objects have corresponding comments.
-
-Commonly used objects and functions using the `-P` function are:
-
-- `SPC\store\FileSystem`: file management class
- - `::replaceFileStr(string $filename, string $search, $replace)`: Replace file string content
- - `::replaceFileStr(string $filename, string $pattern, $replace)`: Regularly replace file content
- - `::replaceFileUser(string $filename, $callback)`: User-defined function replaces file content
- - `::copyDir(string $from, string $to)`: Recursively copy a directory to another location
- - `::convertPath(string $path)`: Convert the path delimiter to the current system delimiter
- - `::scanDirFiles(string $dir, bool $recursive = true, bool|string $relative = false, bool $include_dir = false)`: Traverse directory files
-- `SPC\builder\BuilderBase`: Build object
- - `->getPatchPoint()`: Get the current injection point name
- - `->getOption(string $key, $default = null)`: Get command line and compile-time options
- - `->getPHPVersionID()`: Get the currently compiled PHP version ID
- - `->getPHPVersion()`: Get the currently compiled PHP version number
- - `->setOption(string $key, $value)`: Set options
- - `->setOptionIfNotExists(string $key, $value)`: Set option if option does not exist
-
-::: tip
-static-php-cli has many open methods, which cannot be listed in the docs,
-but as long as it is a `public function` and is not marked as `@internal`, it theoretically can be called.
-:::
-
-## Multiple builds
-
-If you need to build multiple times locally, the following method can save you time downloading resources and compiling.
-
-- If you only switch the PHP version without changing the dependent libraries, you can use `bin/spc switch-php-version` to quickly switch the PHP version, and then re-run the same `build` command.
-- If you want to rebuild once, but do not re-download the source code, you can first `rm -rf buildroot source` to delete the compilation directory and source code directory, and then rebuild.
-- If you want to update a version of a dependency, you can use `bin/spc del-download ` to delete the specified source code, and then use `download ` to download it again.
-- If you want to update all dependent versions, you can use `bin/spc download --clean` to delete all downloaded sources, and then download them again.
-
-## embed usage
-
-If you want to embed static-php into other C language programs, you can use `--build-embed` to build an embed version of PHP.
-
-```bash
-bin/spc build {your extensions} --build-embed --debug
-```
-
-Under normal circumstances, PHP embed will generate `php-config` after compilation.
-For static-php, we provide `spc-config` to obtain the parameters during compilation.
-In addition, when using embed SAPI (libphp.a), you need to use the same compiler as libphp, otherwise there will be a link error.
-
-Here is the basic usage of spc-config:
-
-```bash
-# output all flags and options
-bin/spc spc-config curl,zlib,phar,openssl
-
-# output libs
-bin/spc spc-config curl,zlib,phar,openssl --libs
-
-# output includes
-bin/spc spc-config curl,zlib,phar,openssl --includes
-```
-
-By default, static-php uses the following compilers on different systems:
-
-- macOS: `clang`
-- Linux (Alpine Linux): `gcc`
-- Linux (glibc based distros, x86_64): `/usr/local/musl/bin/x86_64-linux-musl-gcc`
-- Linux (glibc based distros, aarch64): `/usr/local/musl/bin/aarch64-linux-musl-gcc`
-- FreeBSD: `clang`
-
-Here is an example of using embed SAPI:
-
-```c
-// embed.c
-#include
-
-int main(int argc,char **argv){
-
- PHP_EMBED_START_BLOCK(argc,argv)
-
- zend_file_handle file_handle;
-
- zend_stream_init_filename(&file_handle,"embed.php");
-
- if(php_execute_script(&file_handle) == FAILURE){
- php_printf("Failed to execute PHP script.\n");
- }
-
- PHP_EMBED_END_BLOCK()
- return 0;
-}
-```
-
-
-```php
- hello.php
+spc micro:combine hello.php --output=hello
+./hello
+
+# Bundle a phar
+spc micro:combine your-app.phar --output=your-app
+./your-app
+```
+
+### Injecting INI settings
+
+INI configuration can be injected at packaging time via command-line options or an ini file:
+
+```bash
+# Inject via command-line options (-I is shorthand for --with-ini-set)
+spc micro:combine your-app.phar --output=your-app -I "memory_limit=512M" -I "curl.cainfo=/etc/ssl/certs/ca-certificates.crt"
+
+# Inject from an ini file (-N is shorthand for --with-ini-file)
+spc micro:combine your-app.phar --output=your-app -N /path/to/custom.ini
+```
+
+::: tip
+The INI injected with `-I` here is runtime configuration appended to the `micro.sfx` file as a special structure. This is distinct from INI hard-coded at compile time using `-I` during `build:php`. Both can coexist.
+:::
+
+### Pretending to be the cli SAPI
+
+Some frameworks check the `PHP_SAPI` value and refuse to run outside `cli`. Since `micro`'s `PHP_SAPI` is `micro` by default, you can make it report `cli` instead:
+
+```bash
+spc build:php "bcmath,phar" --build-micro --with-micro-fake-cli
+```
+
+### Specifying a custom micro.sfx path
+
+```bash
+spc micro:combine your-app.phar --output=your-app --with-micro=/path/to/your/micro.sfx
+```
+
+### phar path considerations
+
+When packaging a phar, internal relative paths may behave differently than expected. See the [Developer Guide — Phar directory issue](../develop/structure) for details.
+
+## embed
+
+The `embed` SAPI compiles PHP into a static library (`libphp.a` on Linux/macOS, `php8embed.lib` on Windows) that can be linked into C/C++ programs to run PHP code directly.
+
+### Build
+
+```bash
+spc build:php "bcmath,openssl" --build-embed
+```
+
+Output:
+- Linux/macOS: `buildroot/lib/libphp.a`, headers in `buildroot/include/`
+- Windows: `buildroot/lib/php8embed.lib`, headers in `buildroot/include/`
+
+See [build:php — SAPI Selection](./cli-reference#sapi-selection), [build:php — Common Build Options](./cli-reference#common-build-options), and [build:php — embed Options](./cli-reference#embed-options) for the full option reference.
+
+::: tip
+Detailed instructions for linking and using `libphp.a` / `php8embed.lib` in your own projects — including compiler selection, `dev:shell` usage, and a complete C example — will be covered in the Developer Guide.
+:::
+
+## frankenphp
+
+The `frankenphp` SAPI builds a [FrankenPHP](https://github.com/php/frankenphp) binary — a modern PHP application server with Caddy built in, supporting HTTP/2, HTTP/3, automatic HTTPS, and more.
+
+::: tip
+The `frankenphp` binary produced by StaticPHP is a fully self-contained single-file executable. This is different from the official FrankenPHP release, which ships as a dynamically linked binary and requires a separate PHP installation.
+:::
+
+::: warning
+FrankenPHP requires thread-safe mode. Always pass `--enable-zts` when building.
+:::
+
+### Build
+
+```bash
+spc build:php "bcmath,openssl,curl,pdo_mysql" --build-frankenphp --enable-zts
+```
+
+The output is `buildroot/bin/frankenphp` on Linux/macOS, and `buildroot/bin/frankenphp.exe` on Windows.
+
+See [build:php — SAPI Selection](./cli-reference#sapi-selection), [build:php — Common Build Options](./cli-reference#common-build-options), and [build:php — frankenphp Options](./cli-reference#frankenphp-options) for the full option reference.
+
+### Usage
+
+```bash
+# Check version
+./buildroot/bin/frankenphp version
+
+# Run in PHP development server mode
+./buildroot/bin/frankenphp php-server
+
+# Run with a Caddyfile
+./buildroot/bin/frankenphp run --config /path/to/Caddyfile
+```
+
+For full usage, refer to the [FrankenPHP documentation](https://frankenphp.dev/docs/).
+
+## Dynamic Extension Loading
+
+Whether a static PHP binary can load extensions at runtime via `dl()` depends on how the binary was linked.
+
+**macOS** — The build always links dynamically against system libraries. Extensions built as `.so` files can be loaded at runtime via `dl()` or `php.ini` as usual.
+
+**Linux** — StaticPHP's default build target is `native-native-musl`: a fully static binary linked against musl libc. Because there is no dynamic linker available at runtime, `dl()` is disabled, the FFI extension cannot be used, and no external `.so` extensions can be loaded.
+
+To support dynamic extension loading on Linux, set the `SPC_TARGET` environment variable before building:
+
+```bash
+SPC_TARGET=native-native-gnu.2.17 spc build:php "bcmath,openssl" --build-cli
+```
+
+If you installed from source, you can also set `SPC_TARGET=native-native-gnu.2.17` in `config/env.ini` to make it the default for all builds.
+
+This uses the Zig toolchain to produce a partially static binary dynamically linked against glibc 2.17, compatible with most modern GNU/Linux distributions. No Docker and no extra cross-compilation toolchain are required. The resulting binary supports `dl()`, FFI, and loading `.so` extensions at runtime, but cannot run on musl-based systems such as Alpine Linux.
+
+**Windows** — PHP extensions on Windows are distributed as `.dll` files that depend on the DLLs bundled with the official dynamically-built PHP. StaticPHP produces a standalone static executable that does not include those DLLs, so dynamic extension loading is not possible on Windows. All extensions must be compiled in statically at build time.
+
diff --git a/docs/en/guide/troubleshooting.md b/docs/en/guide/troubleshooting.md
index 7fc79e35d..f74e7b00e 100644
--- a/docs/en/guide/troubleshooting.md
+++ b/docs/en/guide/troubleshooting.md
@@ -1,42 +1,43 @@
# Troubleshooting
-Various failures may be encountered in the process of using static-php-cli,
-here will describe how to check the errors by yourself and report Issue.
+Various failures may be encountered in the process of using StaticPHP,
+here will describe how to check the errors by yourself and report an Issue.
## Download Failure
-Problems with downloading resources are one of the most common problems with spc.
+Problems with downloading resources are one of the most common problems with spc.
The main reason is that the addresses used for SPC download resources are generally the official website of the corresponding project or GitHub, etc.,
and these websites may occasionally go down and block IP addresses.
-After encountering a download failure,
-you can try to call the download command multiple times.
+After encountering a download failure,
+you can try to call the download command multiple times.
-When downloading extensions, you may eventually see errors like `curl: (56) The requested URL returned error: 403` which are often caused by github rate limiting.
-You can verify this by adding `--debug` to the command and will see something like `[DEBU] Running command (no output) : curl -sfSL "https://api.github.com/repos/openssl/openssl/releases"`.
+When downloading extensions, you may eventually see errors like `curl: (56) The requested URL returned error: 403` which are often caused by GitHub rate limiting.
+You can verify this by adding `-vvv` to the command and will see something like `[DEBU] Running command (no output) : curl -sfSL "https://api.github.com/repos/openssl/openssl/releases"`.
To fix this, [create](https://github.com/settings/tokens) a personal access token on GitHub and set it as an environment variable `GITHUB_TOKEN=`.
-If you confirm that the address is indeed inaccessible,
+If you confirm that the address is indeed inaccessible,
you can submit an Issue or PR to update the url or download type.
## Doctor Can't Fix Something
-In most cases, the doctor module can automatically repair and install missing system environments,
+In most cases, the doctor module can automatically repair and install missing system environments,
but there are also special circumstances where the automatic repair function cannot be used normally.
Due to system limitations (for example, software such as Visual Studio cannot be automatically installed under Windows),
the automatic repair function cannot be used for some projects.
-When encountering a function that cannot be automatically repaired,
+When encountering a function that cannot be automatically repaired,
if you encounter the words `Some check items can not be fixed`,
it means that it cannot be automatically repaired.
Please submit an issue according to the method displayed on the terminal or repair the environment yourself.
## Compile Error
-When you encounter a compilation error, if the `--debug` log is not enabled, please enable the debug log first,
+When you encounter a compilation error, if the `-vvv` log is not enabled, please enable the debug log first,
and then determine the command that reported the error.
The error terminal output is very important for fixing compilation errors.
When submitting an issue, please upload the last error fragment of the terminal log (or the entire terminal log output),
and include the `spc` command and parameters used.
-If you are rebuilding, please refer to the [Local Build - Multiple Builds](./manual-build#multiple-builds) section.
+If you are rebuilding, please refer to the [First Build - Debugging and Rebuilding](./first-build#debugging-and-rebuilding) section.
+
diff --git a/docs/en/index.md b/docs/en/index.md
index 7d80bf2f7..fb4937ce0 100644
--- a/docs/en/index.md
+++ b/docs/en/index.md
@@ -3,23 +3,26 @@
layout: home
hero:
- name: "Static PHP"
- tagline: "Build standalone PHP binary on Linux, macOS, FreeBSD, Windows, with PHP project together, with popular extensions included."
+ name: "StaticPHP"
+ tagline: "StaticPHP is a powerful tool designed for building portable executables including PHP, extensions, and more."
image:
src: /images/static-php_nobg.png
- alt: Static PHP CLI Logo
+ alt: StaticPHP Logo
actions:
- theme: brand
text: Get Started
- link: ./guide/
+ link: /en/guide/
+ - theme: alt
+ text: 中文文档
+ link: /zh/
features:
- - title: Static CLI Binary
- details: You can easily compile a standalone php binary for general use. Including CLI, FPM sapi.
+ - title: Static PHP Binary
+ details: You can easily compile a standalone php binary for general use. Including cli, fpm, cgi, frankenphp SAPI.
- title: Micro Self-Extracted Executable
- details: You can compile a self-extracted executable and build with your php source code.
+ details: You can compile a self-extracted executable and build with your php source code using micro SAPI.
- title: Dependency Management
- details: static-php-cli comes with dependency management and supports installation of different types of PHP extensions.
+ details: StaticPHP comes with dependency management and supports installation of different types of PHP extensions, packages and libraries.
---
-# CLI 编译命令生成器
+# 编译命令生成器
-::: tip
-下面选择扩展可能包含所选操作系统不支持的扩展，这可能导致编译失败。请先查阅 [支持的扩展](./extensions)。
-:::
-
-
+
diff --git a/docs/zh/guide/cli-reference.md b/docs/zh/guide/cli-reference.md
new file mode 100644
index 000000000..e4a37f9ae
--- /dev/null
+++ b/docs/zh/guide/cli-reference.md
@@ -0,0 +1,522 @@
+---
+outline: 'deep'
+---
+
+# 命令行参考
+
+::: tip
+如果你采用的是 spc 二进制方式安装，请将本章节中的所有 `spc` 替换为 `./spc` 或 `.\spc.exe`。
+
+如果你采用的是源码安装，请将 `spc` 替换为 `bin/spc`。
+:::
+
+## download
+
+下载构建所需的源码包和预编译二进制。
+
+```bash
+spc download [artifacts] [options]
+```
+
+`artifacts`（可选）：指定要下载的制品名称，逗号分隔（如 `"php-src,openssl,curl"`）。
+
+### 选项
+
+| 选项 | 缩写 | 说明 |
+|---|---|---|
+| `--for-extensions=` | `-e` | 按扩展名下载其所需的制品 |
+| `--for-libs=` | `-l` | 按库名下载其所需的制品 |
+| `--for-packages=` | | 按包名下载其所需的制品 |
+| `--without-suggests` | | 使用 `--for-extensions` 时跳过建议包 |
+| `--clean` | | 下载前删除旧的下载缓存 |
+| `--with-php=` | | PHP 版本，格式为 `major.minor`（默认 `8.4`）|
+| `--prefer-binary` | `-p` | 优先使用预编译二进制 |
+| `--prefer-source` | | 优先使用源码包 |
+| `--source-only` | | 仅下载源码制品 |
+| `--binary-only` | | 仅下载二进制制品 |
+| `--parallel=` | `-P` | 并行下载数（默认 `1`）|
+| `--retry=` | `-R` | 失败重试次数（默认 `0`）|
+| `--ignore-cache=` | | 强制重新下载指定制品 |
+| `--no-alt` | | 不使用镜像站 |
+| `--no-shallow-clone` | | 不使用浅层克隆 |
+| `--custom-url=` | `-U` | 覆盖指定源的下载地址 |
+| `--custom-git=` | `-G` | 覆盖为自定义 git 仓库 |
+| `--custom-local=` | `-L` | 使用本地路径作为制品来源 |
+
+### 示例
+
+```bash
+# 按扩展名下载（推荐）
+spc download --for-extensions="bcmath,openssl,curl" --with-php=8.4
+
+# 下载指定制品
+spc download "php-src,openssl"
+
+# 增加并行数和重试次数
+spc download --for-extensions="bcmath,openssl,curl" --parallel 8 --retry=3
+
+# 优先使用预编译二进制
+spc download --for-extensions="bcmath,openssl,curl" --prefer-binary
+
+# 强制重新下载 PHP 源码（如切换版本）
+spc download --for-extensions="bcmath,curl" --ignore-cache="php-src" --with-php=8.3
+
+# 覆盖下载地址
+spc download --for-extensions="bcmath" --custom-url "php-src:https://downloads.php.net/~user/php-8.5.0alpha1.tar.xz"
+```
+
+## build:php {#build-php}
+
+从源码编译 PHP 及扩展。别名：`build`。
+
+```bash
+spc build:php [options]
+```
+
+`extensions`（必填）：要静态编译的扩展名列表，逗号分隔（如 `"bcmath,openssl,curl"`）。
+
+`build:php` 上也可使用所有 `download` 选项，只需加上 `--dl-` 前缀（如 `--dl-with-php=8.3`、`--dl-parallel=4`），这些参数将传递给构建前自动运行的下载器。
+
+### SAPI 选择 {#sapi-selection}
+
+以下选项仅适用于 `build:php` 组合目标。如需单独构建某个 SAPI，请使用对应的专用命令（如 `spc build:php-cli`）。
+
+| 选项 | 说明 |
+|---|---|
+| `--build-cli` | 构建 `cli` SAPI（`php` / `php.exe`）|
+| `--build-fpm` | 构建 `php-fpm`（仅 Linux 和 macOS）|
+| `--build-cgi` | 构建 `php-cgi` |
+| `--build-micro` | 构建 `micro.sfx` |
+| `--build-embed` | 构建 embed 静态库（`libphp.a` / `php8embed.lib`）|
+| `--build-frankenphp` | 构建 FrankenPHP 二进制 |
+
+### 通用构建选项 {#common-build-options}
+
+| 选项 | 缩写 | 说明 |
+|--------------------------------------|------|--------------------------------------------------------|
+| `--no-strip` | | 保留调试符号，不精简二进制 |
+| `--with-upx-pack` | | 用 UPX 压缩产物（需先 `spc install-pkg upx`；仅 Linux 和 Windows） |
+| `--disable-opcache-jit` | | 禁用 OPcache JIT |
+| `--with-config-file-path=` | | PHP 查找 `php.ini` 的目录（默认：`/usr/local/etc/php`） |
+| `--with-config-file-scan-dir=` | | PHP 扫描追加 `.ini` 文件的目录（默认：`/usr/local/etc/php/conf.d`） |
+| `--with-hardcoded-ini=` | `-I` | 编译时将 INI 配置硬编码进二进制（可重复使用） |
+| `--enable-zts` | | 启用线程安全（ZTS）模式 |
+| `--no-smoke-test` | | 跳过构建后的冒烟测试 |
+| `--with-suggests` | | 同时解析并安装建议包 |
+| `--with-packages=` | | 额外安装的包 |
+| `--no-download` | | 跳过下载步骤（使用已有缓存） |
+| `--build-shared=` | `-D` | 指定编译为共享 `.so` / `.dll` 的扩展 |
+
+### micro 专用选项 {#micro-options}
+
+| 选项 | 说明 |
+|----------------------------|--------------------------------------------------|
+| `--with-micro-fake-cli` | 让 `micro` 的 `PHP_SAPI` 报告为 `cli` 而非 `micro` |
+| `--without-micro-ext-test` | 跳过构建后的 `micro.sfx` 扩展测试 |
+| `--with-micro-logo=` | 为 `micro.sfx` 嵌入自定义 `.ico` 图标（仅 Windows） |
+| `--enable-micro-win32` | 将 `micro.sfx` 构建为 Win32 GUI 程序而非控制台程序（仅 Windows） |
+
+### frankenphp 专用选项 {#frankenphp-options}
+
+| 选项 | 说明 |
+|---|---|
+| `--enable-zts` | FrankenPHP 必须开启线程安全 |
+| `--with-frankenphp-app=` | 将指定目录嵌入到 FrankenPHP 二进制中 |
+
+### embed 专用选项 {#embed-options}
+
+| 选项 | 说明 |
+|---|---|
+| `--build-shared=` | 将指定扩展编译为共享库（需要 embed SAPI）|
+
+### 下载透传选项 {#download-options}
+
+所有下载器选项均可加 `--dl-` 前缀使用：
+
+| 选项 | 说明 |
+|---|---|
+| `--dl-with-php=` | 指定下载的 PHP 版本（默认 `8.4`）|
+| `--dl-prefer-binary` | 优先使用预编译二进制依赖 |
+| `--dl-parallel=` | 并行下载数 |
+| `--dl-retry=` | 失败重试次数 |
+| `--dl-custom-url=` | 覆盖指定源的下载地址 |
+| `--dl-custom-git=` | 覆盖为自定义 git 仓库 |
+
+Downloader 选项传递给 `build:php` 命令时，会被自动下载器在构建前使用。
+这样你就可以直接通过构建命令控制下载行为，无需单独执行 `spc download` 命令。
+
+```bash
+spc build:php "bcmath,openssl,curl" --build-cli --dl-with-php=8.3 --dl-prefer-binary --dl-parallel=4
+```
+
+### 示例
+
+```bash
+# 构建 cli SAPI
+spc build:php "bcmath,openssl,curl" --build-cli
+
+# 同时构建 cli + micro
+spc build:php "bcmath,phar,openssl,curl" --build-cli --build-micro
+
+# 指定 PHP 版本
+spc build:php "bcmath,openssl" --build-cli --dl-with-php=8.3
+
+# 硬编码 INI 到二进制
+spc build:php "bcmath,pcntl" --build-cli -I "memory_limit=4G" -I "disable_functions=system"
+
+# 保留调试符号
+spc build:php "bcmath,openssl" --build-cli --no-strip
+
+# 构建 FrankenPHP（需开启 ZTS）
+spc build:php "bcmath,openssl,curl" --build-frankenphp --enable-zts
+```
+
+## build:php-cli, build:php-fpm, build:php-micro, build:php-embed, build:php-cgi, build:frankenphp
+
+专用单目标构建命令，接受与 `build:php` 相同的选项，但不需要 SAPI 选择标志（`--build-*`），目标已隐式确定。
+
+```bash
+spc build:php-cli "bcmath,openssl,curl"
+spc build:php-micro "bcmath,phar,openssl"
+spc build:php-fpm "bcmath,openssl,curl,pdo_mysql"
+spc build:php-embed "bcmath,openssl"
+spc build:frankenphp "bcmath,openssl,curl" --enable-zts
+```
+
+## build:libs
+
+从源码构建一个或多个库包。
+
+```bash
+spc build:libs [options]
+```
+
+`libraries`（必填）：要构建的库包名称列表，逗号分隔（如 `"openssl,curl,zlib"`）。
+
+支持所有 `download` 命令的选项，加 `--dl-` 前缀传递。
+
+### 选项
+
+| 选项 | 缩写 | 说明 |
+|---|---|---|
+| `--with-suggests` | `-L`、`-E` | 同时解析并安装建议包 |
+| `--with-packages=` | | 额外安装的包，逗号分隔 |
+| `--no-download` | | 跳过下载步骤（使用已有缓存） |
+
+### 示例
+
+```bash
+# 构建单个库
+spc build:libs openssl
+
+# 构建多个库
+spc build:libs "openssl,curl,zlib"
+
+# 构建时包含建议包
+spc build:libs openssl --with-suggests
+
+# 跳过下载步骤
+spc build:libs openssl --no-download
+```
+
+## craft
+
+读取 `craft.yml` 并自动完成全流程构建。
+
+```bash
+spc craft [path/to/craft.yml]
+```
+
+未指定路径时，使用当前工作目录下的 `craft.yml`。配置格式参见 [craft.yml 配置](../develop/craft-yml)。
+
+## doctor
+
+检查当前环境是否满足编译要求。
+
+```bash
+spc doctor [--auto-fix[=never]]
+```
+
+| 选项 | 说明 |
+|--------------------|----------------------|
+| `--auto-fix` | 自动修复检测到的问题（使用系统包管理器） |
+| `--auto-fix=never` | 仅报告问题，不尝试自动修复 |
+
+## dev:shell
+
+进入加载了 StaticPHP 构建环境的交互式 Shell（编译器 wrapper、`buildroot/`、`pkgroot/` 等均已添加到 `PATH`）。
+
+```bash
+spc dev:shell
+```
+
+可用于在 embed SAPI 的 `libphp.a` 上编译小型 C 程序，或手动检查构建环境。
+
+## check-update
+
+检查指定制品是否有可用更新。
+
+```bash
+spc check-update [artifact] [options]
+```
+
+`artifact`（可选）：要检查更新的制品名称，逗号分隔。默认检查所有已下载的制品。
+
+### 选项
+
+| 选项 | 缩写 | 说明 |
+|---|---|---|
+| `--json` | | 以 JSON 格式输出结果 |
+| `--bare` | | 检查时不要求制品已下载（旧版本显示为 null）|
+| `--parallel=` | `-p` | 并行检查数（默认 `10`）|
+| `--with-php=` | | PHP 版本上下文，格式为 `major.minor`（默认 `8.4`）|
+
+### 示例
+
+```bash
+# 检查所有已下载制品
+spc check-update
+
+# 检查指定制品
+spc check-update "openssl,curl"
+
+# 以 JSON 格式输出
+spc check-update --json
+
+# 无需先下载即可检查
+spc check-update "openssl" --bare
+```
+
+## dump-extensions
+
+从 Composer 项目中分析所需的 PHP 扩展列表。
+
+```bash
+spc dump-extensions [path] [options]
+```
+
+`path`（可选）：项目根目录路径，默认为当前目录（`.`）。
+
+### 选项
+
+| 选项 | 缩写 | 说明 |
+|---|---|---|
+| `--format=` | `-F` | 输出格式（默认 `default`）|
+| `--no-ext-output=` | `-N` | 未找到扩展时输出的默认组合（逗号分隔），而不是以失败退出 |
+| `--no-dev` | | 不包含 dev 依赖 |
+| `--no-spc-filter` | `-S` | 不使用 SPC 过滤器筛选扩展 |
+
+### 示例
+
+```bash
+# 分析当前目录的 Composer 项目
+spc dump-extensions
+
+# 分析指定目录
+spc dump-extensions /path/to/project
+
+# 不包含 dev 依赖
+spc dump-extensions --no-dev
+
+# 未找到扩展时输出默认组合
+spc dump-extensions --no-ext-output="bcmath,openssl"
+```
+
+## dump-license
+
+导出制品的开源许可证文件。
+
+```bash
+spc dump-license [artifacts] [options]
+```
+
+`artifacts`（可选）：要导出许可证的制品名称，逗号分隔（如 `"php-src,openssl,curl"`）。
+
+### 选项
+
+| 选项 | 缩写 | 说明 |
+|---|---|---|
+| `--for-extensions=` | `-e` | 按扩展名导出（自动包含 php-src），如 `"openssl,mbstring"` |
+| `--for-libs=` | `-l` | 按库名导出，如 `"openssl,zlib"` |
+| `--for-packages=` | `-p` | 按包名导出，如 `"php,libssl"` |
+| `--dump-dir=` | `-d` | 许可证输出目录（默认 `buildroot/license`）|
+| `--without-suggests` | | 不包含建议包的许可证 |
+
+### 示例
+
+```bash
+# 按扩展名导出许可证
+spc dump-license --for-extensions="bcmath,openssl,curl"
+
+# 导出指定制品的许可证
+spc dump-license "php-src,openssl"
+
+# 指定输出目录
+spc dump-license --for-extensions="bcmath,openssl" --dump-dir=/tmp/licenses
+```
+
+## extract
+
+将已下载的制品解压到对应的目标位置。
+
+```bash
+spc extract [artifacts] [options]
+```
+
+`artifacts`（可选）：要解压的制品名称，逗号分隔（如 `"php-src,openssl,curl"`）。
+
+### 选项
+
+| 选项 | 缩写 | 说明 |
+|---|---|---|
+| `--for-extensions=` | `-e` | 按扩展名解压所需制品，如 `"openssl,mbstring"` |
+| `--for-libs=` | `-l` | 按库名解压所需制品，如 `"libcares,openssl"` |
+| `--for-packages=` | | 按包名解压所需制品，如 `"php,libssl,libcurl"` |
+| `--without-suggests` | | 使用 `--for-extensions` 时跳过建议包 |
+| `--source-only` | | 强制解压源码，即使已有预编译二进制 |
+
+### 示例
+
+```bash
+# 按扩展名解压
+spc extract --for-extensions="bcmath,openssl,curl"
+
+# 解压指定制品
+spc extract "php-src,openssl"
+
+# 强制解压源码
+spc extract --for-extensions="bcmath,openssl" --source-only
+```
+
+## install-pkg
+
+安装额外的辅助包（如 UPX、工具链等）。别名：`i`、`install-package`。
+
+```bash
+spc install-pkg [options]
+```
+
+`package`（必填）：要安装的包名称。
+
+支持所有 `download` 命令的选项，加 `--dl-` 前缀传递。
+
+### 示例
+
+```bash
+# 安装 UPX 压缩工具
+spc install-pkg upx
+
+# 安装时优先使用预编译二进制（默认行为）
+spc install-pkg upx
+```
+
+## micro:combine
+
+将 `micro.sfx` 与 PHP/PHAR 文件合并为独立可执行文件。
+
+```bash
+spc micro:combine [options]
+```
+
+`file`（必填）：要合并的 PHP 或 PHAR 文件路径。
+
+### 选项
+
+| 选项 | 缩写 | 说明 |
+|---|---|---|
+| `--with-micro=` | `-M` | 指定自定义 `micro.sfx` 文件路径（默认使用 `buildroot/bin/micro.sfx`）|
+| `--with-ini-set=` | `-I` | 合并时注入 INI 配置（可重复使用）|
+| `--with-ini-file=` | `-N` | 合并时注入 INI 文件 |
+| `--output=` | `-O` | 自定义输出文件名（默认 `my-app`）|
+
+### 示例
+
+```bash
+# 合并 PHP 文件
+spc micro:combine app.php
+
+# 合并 PHAR 文件并指定输出名
+spc micro:combine app.phar --output my-app
+
+# 注入 INI 配置
+spc micro:combine app.php -I "memory_limit=512M" -I "disable_functions=system"
+
+# 注入 INI 文件
+spc micro:combine app.php --with-ini-file=custom.ini
+
+# 使用自定义 micro.sfx
+spc micro:combine app.php --with-micro=/path/to/micro.sfx
+```
+
+## reset
+
+清理构建目录，重置构建环境。
+
+```bash
+spc reset [options]
+```
+
+默认清理 `buildroot/` 和 `source/` 目录。
+
+### 选项
+
+| 选项 | 缩写 | 说明 |
+|---|---|---|
+| `--with-pkgroot` | | 同时删除 `pkgroot/` 目录 |
+| `--with-download` | | 同时删除 `downloads/` 目录 |
+| `--yes` | `-y` | 跳过确认提示 |
+
+### 示例
+
+```bash
+# 清理构建目录（会提示确认）
+spc reset
+
+# 同时清理下载缓存
+spc reset --with-download
+
+# 完全清理（不提示）
+spc reset --with-pkgroot --with-download --yes
+```
+
+## spc-config
+
+输出静态编译所需的编译器和链接器标志，适用于将 PHP embed 库链接到自定义程序。
+
+```bash
+spc spc-config [extensions] [options]
+```
+
+`extensions`（可选）：要包含的扩展名列表，逗号分隔。
+
+### 选项
+
+| 选项 | 缩写 | 说明 |
+|---|---|---|
+| `--with-libs=` | | 额外包含的库，逗号分隔 |
+| `--with-packages=` | `-p` | 额外包含的包，逗号分隔 |
+| `--with-suggested-libs` | `-L` | 包含建议库 |
+| `--with-suggests` | | 包含所有建议包 |
+| `--with-suggested-exts` | `-E` | 包含建议扩展 |
+| `--includes` | | 仅输出 `-I` 头文件路径（`CFLAGS`）|
+| `--libs` | | 仅输出 `-L` 和 `-l` 链接标志（`LDFLAGS + LIBS`）|
+| `--libs-only-deps` | | 仅输出依赖库的 `-l` 标志 |
+| `--absolute-libs` | | 使用库文件的绝对路径输出 |
+| `--no-php` | | 不链接 PHP 库 |
+
+### 示例
+
+```bash
+# 输出完整编译标志
+spc spc-config "bcmath,openssl,curl"
+
+# 仅输出头文件路径
+spc spc-config "bcmath,openssl" --includes
+
+# 仅输出链接标志
+spc spc-config "bcmath,openssl" --libs
+
+# 使用绝对路径
+spc spc-config "bcmath,openssl" --libs --absolute-libs
+```
+
diff --git a/docs/zh/guide/deps-map.md b/docs/zh/guide/deps-map.md
index 91ff57fd8..04615a29d 100644
--- a/docs/zh/guide/deps-map.md
+++ b/docs/zh/guide/deps-map.md
@@ -1,22 +1,19 @@
---
-outline: 'deep'
+aside: false
---
-# 依赖关系图表
+# 依赖关系图
-在编译 PHP 时，每个扩展、库都有依赖关系，这些依赖关系可能是必需的，也可能是可选的。在编译 PHP 时，可以选择是否包含这些可选的依赖关系。
+这里列出了所有支持的包（扩展、库）及其依赖关系。
-例如，在 Linux 下编译 `gd` 扩展时，会强制编译 `zlib,libpng` 库和 `zlib` 扩展，而 `libavif,libwebp,libjpeg,freetype` 库都是可选的库，默认不会编译，除非通过 `--with-libs=avif,webp,jpeg,freetype` 选项指定。
+- **必需依赖**：构建该包时会强制一同构建的包。
+- **可选依赖**：默认不构建，使用 `--with-suggests` 参数可启用，或在构建命令中手动指定。
+- **被依赖**：其他哪些包需要当前包。
-- 对于可选扩展（扩展的可选特性），需手动在编译时指定，例如启用 Redis 的 igbinary 支持：`bin/spc build redis,igbinary`。
-- 对于可选库，需通过 `--with-libs=XXX` 选项编译指定。
-- 如果想启用所有的可选扩展，可以使用 `bin/spc build redis --with-suggested-exts` 参数。
-- 如果想启用所有的可选库，可以使用 `--with-suggested-libs` 参数。
+运行以下命令生成依赖数据（需要在源码模式下）：
-## 扩展的依赖图
+```bash
+bin/spc dev:gen-deps-data
+```
-
-
-## 库的依赖表
-
-
\ No newline at end of file
+
diff --git a/docs/zh/guide/env-vars.md b/docs/zh/guide/env-vars.md
index 9a2f9deb9..cd0d4a1d8 100644
--- a/docs/zh/guide/env-vars.md
+++ b/docs/zh/guide/env-vars.md
@@ -4,15 +4,15 @@
## 环境变量列表
-在 2.3.5 版本之后，我们将环境变量集中到了 `config/env.ini` 文件中，你可以通过修改这个文件来设置环境变量。
+StaticPHP 将环境变量集中到了 `config/env.ini` 文件中，你可以通过修改这个文件来设置环境变量。
-我们将 static-php-cli 支持的环境变量分为三种：
+我们将 StaticPHP 支持的环境变量分为三种：
-- 全局内部环境变量：在 static-php-cli 启动后即声明，你可以在 static-php-cli 的内部使用 `getenv()` 来获取他们，也可以在启动 static-php-cli 前覆盖。
-- 固定环境变量：在 static-php-cli 启动后声明，你仅可使用 `getenv()` 获取，但无法通过 shell 脚本对其覆盖。
-- 配置文件环境变量：在 static-php-cli 构建前声明，你可以通过修改 `config/env.ini` 文件或通过 shell 脚本来设置这些环境变量。
+- **全局内部环境变量**：在 StaticPHP 启动后即声明，你可以在 StaticPHP 的内部使用 `getenv()` 来获取他们，也可以在启动 StaticPHP 前覆盖。
+- **固定环境变量**：在 StaticPHP 启动后声明，你仅可使用 `getenv()` 获取，但无法通过 shell 脚本对其覆盖。
+- **配置文件环境变量**：在 StaticPHP 构建前声明，你可以通过修改 `config/env.ini` 文件或通过 shell 脚本来设置这些环境变量。
-你可以阅读 [config/env.ini](https://github.com/crazywhalecc/static-php-cli/blob/main/config/env.ini) 中每项参数的注释来了解其作用（仅限英文版）。
+你可以阅读 [config/env.ini](https://github.com/crazywhalecc/static-php-cli/blob/v3/config/env.ini) 中每项参数的注释来了解其作用（仅限英文版）。
## 自定义环境变量
@@ -24,10 +24,10 @@
```shell
# export 方式
export SPC_CONCURRENCY=4
-bin/spc build mbstring,pcntl --build-cli
+spc build:php "mbstring,pcntl" --build-cli
# 直接设置方式
-SPC_CONCURRENCY=4 bin/spc build mbstring,pcntl --build-cli
+SPC_CONCURRENCY=4 spc build:php "mbstring,pcntl" --build-cli
```
或者，如果你需要长期修改某个环境变量，你可以通过修改 `config/env.ini` 文件来实现。
@@ -40,7 +40,7 @@ SPC_CONCURRENCY=4 bin/spc build mbstring,pcntl --build-cli
通过写入额外的重载项目指定你的环境变量。
```ini
-; This is an example of `config/env.custom.ini` file,
+; This is an example of `config/env.custom.ini` file,
; we modify the `SPC_CONCURRENCY` and linux default CFLAGS passing to libs and PHP
[global]
SPC_CONCURRENCY=4
@@ -49,64 +49,3 @@ SPC_CONCURRENCY=4
SPC_DEFAULT_C_FLAGS="-O3"
```
-## 编译依赖库的环境变量（仅限 Unix 系统）
-
-从 2.2.0 开始，static-php-cli 对所有 macOS、Linux、FreeBSD 等 Unix 系统的编译依赖库的命令均支持自定义环境变量。
-
-这样你就可以随时通过环境变量来调整编译依赖库的行为。例如你可以通过 `xxx_CFLAGS=-O0` 来设置编译 xxx 库的优化参数。
-
-当然，不是每个依赖库都支持注入环境变量，我们目前提供了三个通配的环境变量，后缀分别为：
-
-- `_CFLAGS`: C 编译器的参数
-- `_LDFLAGS`: 链接器的参数
-- `_LIBS`: 额外的链接库
-
-前缀为依赖库的名称，具体依赖库的名称以 `lib.json` 为准。其中，带有 `-` 的依赖库名称需要将 `-` 替换为 `_`。
-
-下面是一个替换 openssl 库编译的优化选项示例：
-
-```shell
-openssl_CFLAGS="-O0"
-```
-
-库名称使用同 `lib.json` 中列举的名称，区分大小写。
-
-::: tip
-当未指定相关环境变量时，除以下变量外，其余值均默认为空：
-
-| var name | var default value |
-|-----------------------|-------------------------------------------------------------------------------------------------|
-| `pkg_config_CFLAGS` | macOS: `$SPC_DEFAULT_C_FLAGS -Wimplicit-function-declaration -Wno-int-conversion`, Other: empty |
-| `pkg_config_LDFLAGS` | Linux: `--static`, Other: empty |
-| `imagemagick_LDFLAGS` | Linux: `-static`, Other: empty |
-| `imagemagick_LIBS` | macOS: `-liconv`, Other: empty |
-| `ldap_LDFLAGS` | `-L$BUILD_LIB_PATH` |
-| `openssl_CFLAGS` | Linux: `$SPC_DEFAULT_C_FLAGS`, Other: empty |
-| others... | empty |
-
-:::
-
-下表是支持自定义以上三种变量的依赖库名称列表：
-
-| lib name |
-|-------------|
-| brotli |
-| bzip |
-| curl |
-| freetype |
-| gettext |
-| gmp |
-| imagemagick |
-| ldap |
-| libargon2 |
-| libavif |
-| libcares |
-| libevent |
-| openssl |
-
-::: tip
-因为给每个库适配自定义环境变量是一项特别繁琐的工作，且大部分情况下你都不需要这些库的自定义环境变量，所以我们目前只支持了部分库的自定义环境变量。
-
-如果你需要自定义环境变量的库不在上方列表，可以通过 [GitHub Issue](https://github.com/crazywhalecc/static-php-cli/issues)
-来提出需求。
-:::
diff --git a/docs/zh/guide/extension-notes.md b/docs/zh/guide/extension-notes.md
index 70d60d1c9..99a956216 100644
--- a/docs/zh/guide/extension-notes.md
+++ b/docs/zh/guide/extension-notes.md
@@ -7,7 +7,7 @@
HTTP3 支持默认未启用，需在编译时添加 `--with-libs="nghttp2,nghttp3,ngtcp2"` 以启用 PHP 8.4 及以上版本的 HTTP3 支持。
使用 curl 请求 HTTPS 时，可能存在 `error:80000002:system library::No such file or directory` 错误，
-解决办法详见 [FAQ - 无法使用 ssl](../faq/#无法使用-ssl)。
+解决办法详见 [FAQ](../faq/)。
## phpmicro
@@ -62,7 +62,7 @@ swoole-hook-odbc 与 `pdo_odbc` 扩展冲突。如需使用 Swoole 和 `pdo_odbc
## imap
1. 该扩展目前不支持 Kerberos。
-2. 由于底层的 c-client、ext-imap 不是线程安全的。 无法在 `--enable-zts` 构建中使用它。
+2. 由于底层的 c-client、ext-imap 不是线程安全的。无法在 `--enable-zts` 构建中使用它。
3. 该扩展已在 PHP 8.4 中被移除，因此我们建议您寻找替代实现，例如 [Webklex/php-imap](https://github.com/Webklex/php-imap)。
## gd
@@ -84,18 +84,18 @@ bin/spc build gd --with-libs=freetype,libjpeg,libavif,libwebp --build-cli
## xdebug
-1. Xdebug 只能作为共享扩展进行构建。您需要使用除了 `musl-static` 外的其他 `SPC_TARGET` 构建目标。
+1. Xdebug 只能作为共享扩展进行构建。在 Linux 上，您需要使用 glibc 变体的 `SPC_TARGET`（例如 `native-native-gnu.2.17`），而不是默认的 musl 静态目标。
2. 使用 Linux/glibc 或 macOS 时，您可以使用 `--build-shared=xdebug` 将 Xdebug 编译为共享扩展。
编译后的 `./php` 二进制文件可以通过指定 INI 文件进行配置和运行，例如 `./php -d 'zend_extension=/path/to/xdebug.so' your-code.php`。
## xml
-1. xml包括 xmlreader、xmlwriter、dom、simplexml 等，添加 xml 扩展时最好同时启用这些扩展。
-2. libxml 包含在 xml 扩展中。 启用 xml 相当于启用 libxml。
+1. xml 包括 xmlreader、xmlwriter、dom、simplexml 等，添加 xml 扩展时最好同时启用这些扩展。
+2. libxml 包含在 xml 扩展中。启用 xml 相当于启用 libxml。
## glfw
-1. glfw 扩展依赖 OpenGL，在 Linux 平台还依赖 X11 等环境，这些库都无法被轻易地动态链接。
+1. glfw 扩展依赖 OpenGL，在 Linux 平台还依赖 X11 等环境，这些库都无法被轻易地静态链接。
2. 在 macOS 系统下，我们可以动态链接系统的 OpenGL 和一些相关的库。
## rar
@@ -113,22 +113,22 @@ bin/spc build gd --with-libs=freetype,libjpeg,libavif,libwebp --build-cli
pgsql 16.2 修复了这个 Bug，现在正常工作了。
在 pgsql 使用 SSL 连接时，可能存在 `error:80000002:system library::No such file or directory` 错误，
-解决办法详见 [FAQ - 无法使用 ssl](../faq/#无法使用-ssl)。
+解决办法详见 [FAQ](../faq/)。
## openssl
使用基于 openssl 的扩展（如 curl、pgsql 等网络库）时，可能存在 `error:80000002:system library::No such file or directory` 错误，
-解决办法详见 [FAQ - 无法使用 ssl](../faq/#无法使用-ssl)。
+解决办法详见 [FAQ](../faq/)。
## password-argon2
-1. password-argon2不是一个标准的扩展。`password_hash` 函数的 `PASSWORD_ARGON2ID` 算法需要 libsodium 或 libargon2 才能工作。
+1. password-argon2 不是一个标准的扩展。`password_hash` 函数的 `PASSWORD_ARGON2ID` 算法需要 libsodium 或 libargon2 才能工作。
2. 使用 password-argon2 可以为此启用多线程支持。
## ffi
1. 由于 musl libc 静态链接的限制，无法加载动态库，因此无法使用 ffi。
- 如果您需要使用 ffi 扩展，请参阅 [使用 GNU libc 编译 PHP](./build-with-glibc)。
+ 如果您需要使用 ffi 扩展，请使用基于 glibc 的 `SPC_TARGET`（例如 `native-native-gnu.2.17`），详见 [SAPI 参考](./sapi-reference)。
2. macOS 支持 ffi 扩展，但某些内核不包含调试符号时会出现错误。
3. Windows x64 支持 ffi 扩展。
@@ -156,3 +156,4 @@ parallel 扩展只支持 PHP 8.0 及以上版本，并只支持 ZTS 构建（`--
1. 从技术上讲，这不是扩展，而是一个库。
2. 在 Linux 或 macOS 上使用 `--with-libs="mimalloc"` 进行构建将覆盖默认分配器。
3. 目前，这还处于实验阶段，但建议在线程环境中使用。
+
diff --git a/docs/zh/guide/extensions.md b/docs/zh/guide/extensions.md
index 43095a077..9cf819366 100644
--- a/docs/zh/guide/extensions.md
+++ b/docs/zh/guide/extensions.md
@@ -2,21 +2,16 @@
import SearchTable from "../../.vitepress/components/SearchTable.vue";
-# 扩展列表
+# 支持的扩展列表
-> - `yes`: 已支持
+> - ✅: 已支持
> - 空白: 目前还不支持，或正在支持中
-> - `no` with issue link: 确定不支持或无法支持
-> - `partial` with issue link: 已支持，但是无法完美工作
-
::: tip
如果缺少您需要的扩展，您可以创建 [功能请求](https://github.com/crazywhalecc/static-php-cli/issues)。
-有些扩展或扩展依赖的库会有一些可选的特性，例如 gd 库可选支持 libwebp、freetype 等。
-如果你只使用 `bin/spc build gd --build-cli` 是不会包含它们（static-php-cli 默认为最小依赖原则）。
-
-有关编译可选库，请参考 [扩展、库的依赖关系图表](./deps-map)。对于可选的库，你也可以从 [编译命令生成器](./cli-generator) 中选择扩展后展开选择可选库。
+某些扩展或其依赖的库会有可选特性（例如 gd 可选支持 libwebp、freetype 等）。
+仅使用 `bin/spc build gd --build-cli` 不会包含这些可选依赖——StaticPHP 默认遵循最小依赖原则。
:::
diff --git a/docs/zh/guide/first-build.md b/docs/zh/guide/first-build.md
new file mode 100644
index 000000000..5c7283d4f
--- /dev/null
+++ b/docs/zh/guide/first-build.md
@@ -0,0 +1,188 @@
+# 第一次构建
+
+本页通过完整的示例演示如何从零开始构建一个静态 PHP 二进制。
+
+::: tip
+如果你采用的是 spc 二进制方式安装，请将本章节中的所有 `spc` 替换为 `./spc` 或 `.\spc.exe`。
+
+如果你采用的是源码安装，请将 `spc` 替换为 `bin/spc`。
+:::
+
+## 两种构建方式
+
+StaticPHP 提供两种构建方式，根据使用场景选择：
+
+| 方式 | 适合场景 |
+|--------------|--------------------------|
+| `craft` 一键构建 | 日常使用、快速上手 |
+| 分步构建 | 细化构建流程 |
+
+## 方式一：`craft` 一键构建（推荐）
+
+`craft` 命令读取一个 `craft.yml` 配置文件，自动完成依赖下载、库编译、PHP 构建的全流程。
+
+### 编写 craft.yml
+
+在当前目录创建 `craft.yml`，声明要编译的 PHP 版本、扩展和目标 SAPI：
+
+```yaml
+php-version: 8.4
+extensions: bcmath,posix,phar,zlib,openssl,curl,fileinfo,tokenizer
+sapi:
+ - cli
+ - micro
+```
+
+不想手动编写？试试[命令行生成器](./cli-generator)自动生成配置。
+
+### 开始构建
+
+```bash
+spc craft
+```
+
+构建过程依次执行：下载依赖 → 编译依赖库 → 编译 PHP。全程无需人工干预。
+
+如需查看详细日志，加上 `-v`、`-vv` 或 `-vvv` 参数：
+
+```bash
+spc craft -v
+```
+
+### 查看产物
+
+构建成功后，产物均位于 `buildroot/bin/`：
+
+| SAPI | 产物路径 |
+|------------|------------------------------------------------------|
+| cli | `buildroot/bin/php`（Windows：`buildroot/bin/php.exe`） |
+| fpm | `buildroot/bin/php-fpm` |
+| micro | `buildroot/bin/micro.sfx` |
+| embed | `buildroot/lib/libphp.a` |
+| frankenphp | `buildroot/bin/frankenphp` |
+
+验证一下 cli 是否可用：
+
+```bash
+./buildroot/bin/php -v
+./buildroot/bin/php -m
+```
+
+## 方式二：分步构建
+
+分步方式适合需要将下载与编译拆分为独立阶段的场景，例如在 CI 中缓存下载内容以加速后续构建。
+
+### 第一步：下载依赖
+
+v3 版本中，你可以省略这一步骤，直接构建想要的内容，StaticPHP 会自动下载所需的依赖库和扩展源码。
+
+但如果你想提前下载，或在网络环境较差的情况下分阶段构建，可以使用 `download` 命令：
+
+```bash
+# 按扩展列表下载（推荐，只下载实际需要的内容）
+spc download --for-extensions="bcmath,posix,phar,zlib,openssl,curl,fileinfo,tokenizer" --with-php=8.4
+
+# 按依赖包列表下载
+spc download "curl,openssl" --with-php=8.4
+```
+
+下载内容缓存在 `downloads/` 目录，重复构建时会直接复用。
+
+```bash
+# 网络较慢时，可增大并发数和重试次数
+spc download --for-extensions="bcmath,openssl,curl" --parallel 10 --retry=3
+
+# 优先使用预编译的二进制依赖，跳过源码编译（大幅加速构建）
+spc download --for-extensions="bcmath,openssl,curl" --prefer-binary
+```
+
+### 第二步：构建 PHP
+
+```bash
+# 构建 cli SAPI
+spc build:php "bcmath,phar,zlib,openssl,curl,fileinfo,tokenizer" --build-cli
+
+# 同时构建多个 SAPI
+spc build:php "bcmath,phar,zlib,openssl,curl" --build-cli --build-micro
+```
+
+
+
+#### 常用构建选项
+
+| 选项 | 说明 |
+|----------------------|--------------------------------------|
+| `--build-cli` | 构建 cli SAPI |
+| `--build-fpm` | 构建 php-fpm（不支持 Windows） |
+| `--build-micro` | 构建 micro.sfx |
+| `--build-embed` | 构建嵌入式 SAPI |
+| `--build-frankenphp` | 构建 FrankenPHP |
+| `--enable-zts` | 启用线程安全（ZTS）版本 |
+| `--no-strip` | 保留调试符号，不精简二进制 |
+| `-I key=value` | 硬编译 INI 选项到 PHP 中 |
+| `--with-upx-pack` | 用 UPX 压缩产物（需先 `spc install-pkg upx`） |
+
+硬编译 INI 的例子——预设更大的内存限制，并禁用 `system` 函数：
+
+```bash
+spc build:php "bcmath,pcntl,posix" --build-cli -I "memory_limit=4G" -I "disable_functions=system"
+```
+
+## 打包 micro 应用
+
+构建 `micro.sfx` 后，用 `micro:combine` 将你的 PHP 代码打包进去，生成一个完全独立的可执行文件：
+
+```bash
+echo " hello.php
+spc micro:combine hello.php --output=hello
+./hello
+```
+
+也支持打包 `.phar` 文件，以及注入 INI 配置：
+
+```bash
+# 打包 phar
+spc micro:combine your-app.phar --output=your-app
+
+# 打包时注入 INI
+spc micro:combine your-app.phar --output=your-app -I "memory_limit=512M"
+
+# 从 ini 文件注入配置
+spc micro:combine your-app.phar --output=your-app -N /path/to/custom.ini
+```
+
+## 调试与重新构建
+
+构建失败，或想查看详细过程，使用 `-v` / `-vv` / `-vvv`：
+
+- `-v` 将显示 `INFO` 级别的日志，包含执行到的模块和执行的编译命令等。
+- `-vv` 将显示 `DEBUG` 级别的日志，包含所有 StaticPHP 中调试级别的日志。
+- `-vvv` 将显示 `DEBUG` 级别的日志，并将其他 shell 命令执行的 STDOUT 输出到终端。
+
+```bash
+spc build:php "bcmath,openssl" --build-cli -vv
+```
+
+或者，你也可以查看 `log/spc.shell.log` 和 `log/spc.output.log` 获取终端输出和 StaticPHP 日志。
+
+如需清理编译中间产物、从头重新构建（不重新下载），使用 `reset`：
+
+```bash
+spc reset
+# 然后重新构建
+spc build:php "bcmath,openssl" --build-cli
+```
+
+::: tip
+`reset` 只清理 `buildroot/` 和 `source/` 目录，不会删除 `downloads/` 缓存。
+如需同时清理下载缓存，加上 `--with-download` 参数。
+:::
+
+如果问题持续无法解决，欢迎提交 [Issue](https://github.com/crazywhalecc/static-php-cli/issues)，并附上 `craft.yml`（如有）和 `log/` 目录的压缩包。
+
+## 接下来
+
+- [PHP SAPI 构建参考](./sapi-reference) - 各个 PHP 的 SAPI 构建及使用指南
+- [命令行参考](./cli-reference) — 所有命令与选项的完整说明
+- [扩展列表](./extensions) — 查看支持的扩展及其依赖关系
+- [常见问题](./troubleshooting) — 构建失败时的排查指南
diff --git a/docs/zh/guide/index.md b/docs/zh/guide/index.md
index 8e5727c2a..5bc0292f9 100644
--- a/docs/zh/guide/index.md
+++ b/docs/zh/guide/index.md
@@ -1,48 +1,60 @@
-# 指南
+# 构建指南
-static-php-cli 是一个用于构建静态编译的 PHP 二进制的工具，目前支持 Linux 和 macOS 系统。
+::: warning
+你正在阅读 StaticPHP v3 版本的文档，v2 版本将在 v3 稳定发布后废弃。v3 版本目前仍处于 alpha 阶段，
+你可以在 [这里](https://static-php.github.io/v2-docs/) 查看 v2 文档。
+:::
-在指南章节中，你将了解到如何使用 static-php-cli 构建独立的 php 程序。
+## StaticPHP 是什么
-- [本地构建](./manual-build)
-- [Action 构建](./action-build)
-- [扩展列表](./extensions)
+StaticPHP 是一个构建工具，能够将 PHP 解释器与你所需的扩展一起编译成一个独立的二进制文件，无需在目标系统上预先安装 PHP 或任何依赖库。
+构建产物可以直接分发和运行，适用于 Linux、macOS 和 Windows 平台。
-## 编译环境
+StaticPHP 的能力不止于 PHP。依托同一套构建基础设施，它还可以将 `curl`、`pkg-config`、`htop` 等常用命令行工具编译为独立的静态二进制，无需在目标机器上安装任何依赖即可直接运行。后续还会持续扩充内置支持的工具集。
-下面是架构支持情况，:gear: 代表支持 GitHub Action 构建，:computer: 代表支持本地构建，空 代表暂不支持。
+## 为什么要构建静态 PHP
-| | x86_64 | aarch64 |
-|---------|-------------------|-------------------|
-| macOS | :gear: :computer: | :gear: :computer: |
-| Linux | :gear: :computer: | :gear: :computer: |
-| Windows | :gear: :computer: | |
-| FreeBSD | :computer: | :computer: |
+普通 PHP 安装依赖系统环境：你需要先安装 PHP、再装扩展、再处理各个发行版之间的差异。
+将 PHP 构建为静态二进制之后，这些问题都不再存在——你得到的是一个单文件可执行程序，在任何相同架构的系统上开箱即用。
-当前支持编译的 PHP 版本：
+典型使用场景：
-> :warning: 部分支持，对于新的测试版和旧版本可能存在问题。
->
-> :heavy_check_mark: 支持
->
-> :x: 不支持
+- **部署命令行工具**：把 PHP 工具（如 Composer、PHPStan、自研 CLI）打包后直接分发，用户无需安装 PHP。
+- **容器和嵌入式环境**：用最小体积的静态 PHP 替代臃肿的基础镜像。
+- **服务端应用**：构建包含 FPM 或 FrankenPHP SAPI 的静态二进制，部署更简单，不依赖宿主机环境。
-| PHP Version | Status | Comment |
-|-------------|--------------------|---------------------------------------------------------|
-| 7.2 | :x: | |
-| 7.3 | :x: | phpmicro 和许多扩展不支持 7.3、7.4 版本 |
-| 7.4 | :x: | phpmicro 和许多扩展不支持 7.3、7.4 版本 |
-| 8.0 | :warning: | PHP 官方已停止 8.0 的维护，我们不再处理 8.0 相关的 backport 支持 |
-| 8.1 | :warning: | PHP 官方仅对 8.1 提供安全更新，在 8.5 发布后我们不再处理 8.1 相关的 backport 支持 |
-| 8.2 | :heavy_check_mark: | |
-| 8.3 | :heavy_check_mark: | |
-| 8.4 | :heavy_check_mark: | |
-| 8.5 (beta) | :warning: | PHP 8.5 目前处于 beta 阶段 |
+## phpmicro：把 PHP 和你的代码打包成一个文件
-> 这个表格的支持状态是 static-php-cli 对构建对应版本的支持情况，不是 PHP 官方对该版本的支持情况。
+[phpmicro](https://micro.static-php.dev) 是一个第三方 PHP SAPI，StaticPHP 对其提供原生支持。
+它能将 PHP 解释器本身和你的 `.php` 源文件（或 `.phar` 打包文件）合并成单个自解压可执行文件（`sfx`）。
-## PHP 支持版本
+```
+micro.sfx + your-app.phar = your-app （可直接运行，无任何依赖）
+```
-目前，static-php-cli 对 PHP 8.2 ~ 8.5 版本是支持的，对于 PHP 8.1 及更早版本理论上支持，只需下载时选择早期版本即可。
-但由于部分扩展和特殊组件已对早期版本的 PHP 停止了支持，所以 static-php-cli 不会明确支持早期版本。
-我们推荐你编译尽可能新的 PHP 版本，以获得更好的体验。
+这特别适合分发 PHP 编写的命令行工具：用户拿到的只是一个普通的可执行文件，完全感知不到背后是 PHP。
+
+## 改善你的项目分发与部署
+
+**取代臃肿的 Docker 基础镜像**
+
+官方 `php:8.x` 镜像动辄数百 MB，大多数情况下只是为了提供一个 PHP 运行环境。
+改用静态 PHP 二进制配合极简基础镜像（甚至 `FROM scratch`），镜像体积可以压缩到个位数 MB，启动速度也更快。
+
+**构建可分发的 PHP CLI 工具**
+
+用 [symfony/console](https://symfony.com/doc/current/components/console.html) 或 [Laravel Zero](https://laravel-zero.com) 写好你的 CLI 程序，
+再用 [Box](https://github.com/box-project/box) 打包成 `.phar`，最后通过 phpmicro 合并为单文件可执行程序。
+最终产物可以直接分发，用户无需安装任何 PHP 环境，和 Go、Rust 工具的体验完全一致。
+
+**基于 FrankenPHP 构建单文件 Web 应用**
+
+[FrankenPHP](https://frankenphp.dev) 是一个现代 PHP 应用服务器，内置 HTTP/2、HTTP/3 和 HTTPS 自动管理。
+StaticPHP 支持将 FrankenPHP 连同所需扩展一起静态编译，
+最终产物是一个包含完整 Web 服务器的单一可执行文件，无需 Nginx、PHP-FPM，直接部署即可运行。
+
+## 接下来
+
+- [安装 StaticPHP](./installation) — 安装 StaticPHP 构建工具
+- [第一次构建](./first-build) — 完整流程演示：从下载源码到得到可执行文件
+- [命令行参考](./cli-reference) — 所有命令与选项速查
diff --git a/docs/zh/guide/installation.md b/docs/zh/guide/installation.md
new file mode 100644
index 000000000..1bfce62f9
--- /dev/null
+++ b/docs/zh/guide/installation.md
@@ -0,0 +1,108 @@
+# 安装 StaticPHP
+
+## 系统要求
+
+| 平台 | 架构 | 说明 |
+|---|---|---|
+| Linux | x86_64、aarch64 | 支持主流发行版（Alpine、Debian/Ubuntu、RHEL/CentOS 等） |
+| macOS | x86_64 (Intel)、arm64 (Apple Silicon) | 需要 macOS 12 或更高版本 |
+| Windows | x86_64 | 需要 Windows 10 Build 17063 或更高版本 |
+
+::: tip
+Linux 下，glibc 环境（Debian、Ubuntu、Arch 等）和 musl 环境（Alpine）均受支持。
+`doctor` 命令会自动检测当前环境并在必要时引导安装合适的工具链。
+:::
+
+StaticPHP 有多种安装方式，选择适合你的场景：
+
+| 方式 | 适合谁 |
+|---|---|
+| 预编译二进制 | 大多数用户，直接下载开箱即用 |
+| 从源码安装 | 参与开发、或需要修改核心构建逻辑的开发者 |
+| Vendor 模式 | 在已有 PHP 项目中集成 StaticPHP 能力 |
+
+## 预编译二进制
+
+spc 无须任何依赖，下载即可运行，支持 Linux、macOS 和 Windows。
+
+> spc 本身是由 StaticPHP 构建的静态 PHP 二进制，幽默地说：我们用 StaticPHP 构建了 StaticPHP 的构建工具。
+
+```shell
+# Linux x86_64
+curl -#fSL https://dl.static-php.dev/v3/spc-bin/latest/spc-linux-x86_64 -o spc
+# Linux arm64
+curl -#fSL https://dl.static-php.dev/v3/spc-bin/latest/spc-linux-aarch64 -o spc
+# macOS x86_64 (Intel)
+curl -#fSL https://dl.static-php.dev/v3/spc-bin/latest/spc-macos-x86_64 -o spc
+# macOS arm64 (Apple Silicon)
+curl -#fSL https://dl.static-php.dev/v3/spc-bin/latest/spc-macos-aarch64 -o spc
+# Windows x86_64 (PowerShell)
+curl.exe -#fSL https://dl.static-php.dev/v3/spc-bin/latest/spc-windows-x86_64.exe -o spc.exe
+```
+
+*nix 系统下载完成后需要赋予可执行权限：
+
+```bash
+chmod +x spc && ./spc --version
+```
+
+## 从源码安装
+
+适合想参与开发、或需要修改核心注册表和构建脚本的开发者。需要系统已安装 PHP >= 8.4、Composer，以及 `mbstring,posix,pcntl,iconv,phar,zlib` 扩展。
+
+```bash
+git clone https://github.com/static-php/static-php.git --branch v3
+cd static-php-cli
+composer install
+```
+
+如果系统还没有 PHP 和 Composer，可以用内置脚本一键安装运行环境：
+
+::: code-group
+```bash [Linux / macOS]
+bin/setup-runtime
+```
+```powershell [Windows]
+.\bin\setup-runtime.ps1
+.\bin\setup-runtime.ps1 add-path # 将 runtime/ 加入 PATH
+```
+:::
+
+脚本执行完成后，会在项目目录下生成 `runtime/` 子目录，其中包含 `php` 和 `composer` 两个可执行文件。安装完成后有两种使用方式：
+
+1. **直接通过路径调用**（无需修改环境变量）：
+ ```bash
+ runtime/php bin/spc --help
+ runtime/php runtime/composer install
+ ```
+
+2. **将 `runtime/` 加入 PATH**（之后可直接使用 `php`、`composer`、`bin/spc`）：
+ ```bash
+ export PATH="/path/to/static-php/runtime:$PATH"
+ # 建议写入 ~/.bashrc 或 ~/.zshrc 使其永久生效
+ ```
+
+## Vendor 模式
+
+适合在已有 PHP 项目中直接集成 StaticPHP 能力，或通过自定义 registry 支持私有库和扩展的构建。
+
+```bash
+composer require crazywhalecc/static-php-cli
+```
+
+Vendor 模式的详细用法见 [Vendor 模式指南](../develop/vendor-mode/)。
+
+## 验证构建环境
+
+> **Vendor 模式用户可跳过此步骤。**
+
+安装完成后，运行 `doctor` 检查系统构建工具链是否就绪（cmake、make、编译器等）：
+
+```bash
+# 使用 spc 二进制
+./spc doctor --auto-fix
+# 使用源码安装
+bin/spc doctor --auto-fix
+```
+
+检查通过后，继续阅读[第一次构建](./first-build)。
diff --git a/docs/zh/guide/manual-build.md b/docs/zh/guide/manual-build.md
deleted file mode 100644
index 4c24cab8f..000000000
--- a/docs/zh/guide/manual-build.md
+++ /dev/null
@@ -1,638 +0,0 @@
----
-outline: 'deep'
----
-
-# 本地构建（Linux、macOS、FreeBSD）
-
-本章节为 Linux、macOS、FreeBSD 的构建过程，如果你要在 Windows 上构建，请到 [在 Windows 上构建](./build-on-windows)。
-
-## 手动构建（使用 SPC 二进制）（推荐）
-
-本项目提供了一个 static-php-cli 的二进制文件，你可以直接下载对应平台的二进制文件，然后使用它来构建静态的 PHP。目前 `spc` 二进制支持的平台有 Linux 和 macOS。
-
-使用以下命令从自托管服务器下载：
-
-```bash
-# Download from self-hosted nightly builds (sync with main branch)
-# For Linux x86_64
-curl -fsSL -o spc https://dl.static-php.dev/static-php-cli/spc-bin/nightly/spc-linux-x86_64
-# For Linux aarch64
-curl -fsSL -o spc https://dl.static-php.dev/static-php-cli/spc-bin/nightly/spc-linux-aarch64
-# macOS x86_64 (Intel)
-curl -fsSL -o spc https://dl.static-php.dev/static-php-cli/spc-bin/nightly/spc-macos-x86_64
-# macOS aarch64 (Apple)
-curl -fsSL -o spc https://dl.static-php.dev/static-php-cli/spc-bin/nightly/spc-macos-aarch64
-# Windows (x86_64, win10 build 17063 or later)
-curl.exe -fsSL -o spc.exe https://dl.static-php.dev/static-php-cli/spc-bin/nightly/spc-windows-x64.exe
-
-# Add execute perm (Linux and macOS only)
-chmod +x ./spc
-
-# Run (Linux and macOS)
-./spc --version
-# Run (Windows powershell)
-.\spc.exe --version
-```
-
-> 如果你使用的是打包好的 `spc` 二进制，你需要将下面所有命令中 `bin/spc` 开头替换为 `./spc`。
-
-## 手动构建（使用源码）
-
-如果使用 spc 二进制出现问题，或你有修改 static-php-cli 源码需求，请从源码下载 static-php-cli。
-
-目前支持在 macOS、Linux 上构建，macOS 支持最新版操作系统和两种架构，Linux 支持 Debian、RHEL 及衍生发行版、Alpine Linux 等。
-
-因为本项目本身采用 PHP 开发，所以在编译时也需要系统安装 PHP。本项目本身也提供了适用于本项目的静态二进制 php，可以根据实际情况自行选择使用。
-
-### 下载本项目
-
-```bash
-git clone https://github.com/crazywhalecc/static-php-cli.git --depth=1
-cd static-php-cli
-
-# 你需要先安装 PHP 环境后再运行 Composer 和本项目，安装方式可参考下面。
-composer update
-```
-
-### 使用预编译静态 PHP 二进制运行 static-php-cli
-
-如果你不想使用 Docker、在系统内安装 PHP，可以直接下载本项目自身编译好的 php 二进制 cli 程序。使用流程如下：
-
-使用命令部署环境，此脚本会从 [自托管的服务器](https://dl.static-php.dev/static-php-cli/) 下载一个当前操作系统的 php-cli 包，
-并从 [getcomposer](https://getcomposer.org/download/latest-stable/composer.phar) 或 [Aliyun（镜像）](https://mirrors.aliyun.com/composer/composer.phar) 下载 Composer。
-
-::: tip
-使用预编译静态 PHP 二进制目前仅支持 Linux 和 macOS。FreeBSD 环境因为缺少自动化构建环境，所以暂不支持。
-:::
-
-```bash
-bin/setup-runtime
-
-# 对于中国大陆地区等网络环境特殊的用户，可使用镜像站加快下载速度
-bin/setup-runtime --mirror china
-```
-
-此脚本总共会下载两个文件：`bin/php` 和 `bin/composer`，下载完成后，有两种使用方式：
-
-1. 将 `bin/` 目录添加到 PATH 路径中：`export PATH="/path/to/your/static-php-cli/bin:$PATH"`，添加路径后，相当于系统安装了 PHP，可直接使用 `composer`、`php -v` 等命令，也可以直接使用 `bin/spc`。
-2. 直接调用，比如执行 static-php-cli 命令：`bin/php bin/spc --help`，执行 Composer：`bin/php bin/composer update`。
-
-### 使用 Docker 环境
-
-如果你不愿意在系统安装 PHP 和 Composer 运行环境，可以使用内置的 Docker 环境构建脚本。
-
-```bash
-# 直接使用，将所有使用的命令中 `bin/spc` 替换为 `bin/spc-alpine-docker` 即可
-bin/spc-alpine-docker
-```
-
-首次执行命令会使用 `docker build` 构建一个 Docker 镜像，默认构建的 Docker 镜像为 `x86_64` 架构，镜像名称为 `cwcc-spc-x86_64`。
-
-如果你想在 `x86_64` 环境下构建 `aarch64` 的 static-php-cli，可以使用 qemu 模拟 arm 镜像运行 Docker，但速度会非常慢。使用参数：`SPC_USE_ARCH=aarch64 bin/spc-alpine-docker`。
-
-如果运行后提示需要 sudo 才能运行，执行一次以下命令可授予 static-php-cli 执行 sudo 的权限：
-
-```bash
-export SPC_USE_SUDO=yes
-```
-
-### 使用系统 PHP 环境
-
-下面是系统安装 PHP、Composer 的一些示例命令。具体安装方式建议自行搜索或询问 AI 搜索引擎获取答案，这里不多赘述。
-
-```bash
-# [macOS], 需要先安装 Homebrew. See https://brew.sh/
-# Remember change your composer executable path. For M1/M2 Chip mac, "/opt/homebrew/bin/", for Intel mac, "/usr/local/bin/". Or add it to your own path.
-brew install php wget
-wget https://getcomposer.org/download/latest-stable/composer.phar -O /path/to/your/bin/composer && chmod +x /path/to/your/bin/composer
-
-# [Debian], you need to make sure your php version >= 8.4 and composer >= 2.0
-sudo apt install php-cli composer php-tokenizer
-```
-
-::: tip
-目前 Ubuntu 部分版本的 apt 安装的 php 版本较旧，故不提供安装命令。如有需要，建议先添加 ppa 等软件源后，安装最新版的 PHP 以及 tokenizer、xml、phar 扩展。
-
-较老版本的 Debian 默认安装的可能为旧版本（<= 8.3）版本的 PHP，建议先升级 Debian 或使用 Docker 或自带的静态二进制环境。
-:::
-
-## 使用 craft 构建（推荐）
-
-使用 `bin/spc craft` 可以使用一个配置文件，一个命令实现自动检查环境、下载源代码、构建依赖库、构建 PHP 及扩展等。
-
-你需要编写一个 `craft.yml` 文件，存放在当前工作目录下。`craft.yml` 可以由 [命令生成器](./cli-generator) 生成，或者手动编写。
-
-手动编写可参考 [craft.yml 配置](../develop/craft-yml.md) 中的注释来编写。我们下面假设你编译一个扩展组合，并选用 PHP 8.4，输出 `cli` 和 `fpm`：
-
-```yaml
-# path/to/craft.yml
-php-version: 8.4
-extensions: bcmath,posix,phar,zlib,openssl,curl,fileinfo,tokenizer
-sapi:
- - cli
- - fpm
-```
-
-然后使用 `bin/spc craft` 命令来编译：
-
-```bash
-bin/spc craft --debug
-```
-
-如果构建成功，你会在当前目录下看到 `buildroot/bin` 目录，里面包含了编译好的 PHP 二进制文件，或相应的 SAPI。
-
-- cli: Windows 下构建结果为 `buildroot/bin/php.exe`，其他平台为 `buildroot/bin/php`。
-- fpm: 构建结果为 `buildroot/bin/php-fpm`。
-- micro: 构建结果为 `buildroot/bin/micro.sfx`，如需进一步与 PHP 代码打包，请查看 [打包 micro 二进制](./manual-build#命令-micro-combine-打包-micro-二进制)。
-- embed: 参见 [embed 使用](./manual-build#embed-使用)。
-- frankenphp: 构建结果为 `buildroot/bin/frankenphp`。
-
-如果中途构建出错，你可以使用 `--debug` 参数查看详细的错误信息，或者使用 `--with-clean` 参数清除旧的编译结果，重新编译。
-
-如使用以上方式仍构建失败，请提交一个 issue，附上你的 `craft.yml` 文件、`log/` 目录的压缩包。
-
-## 分步构建命令
-
-如果你有定制化需求，或分开下载、编译 PHP 和依赖库的需求，可以使用 `bin/spc` 命令分步执行。
-
-### 命令 download - 下载依赖包
-
-使用命令 `bin/spc download` 可以下载编译需要的源代码，包括 php-src 以及依赖的各种库的源码。
-
-```bash
-# 仅下载要编译的扩展及依赖库（使用扩展名，包含可选库）
-bin/spc download --for-extensions=openssl,swoole,zip,pcntl,zstd
-
-# 仅下载要编译的扩展及依赖库（使用扩展名，不包含可选库）
-bin/spc download --for-extensions=openssl,swoole,zip,pcntl --without-suggestions
-
-# 仅下载要编译的库（包括其依赖，使用库名，包含可选库，可以和 --for-extensions 组合使用）
-bin/spc download --for-libs=liblz4,libevent --for-extensions=pcntl,rar,xml
-
-# 仅下载要编译的库（包括其依赖，使用库名，不包含可选库）
-bin/spc download --for-libs=liblz4,libevent --without-suggestions
-
-# 下载资源时，忽略部分资源的缓存，强制下载（如切换特定 PHP 版本）
-bin/spc download --for-extensions=curl,pcntl,xml --ignore-cache-sources=php-src --with-php=8.3.10
-
-# 下载资源时，优先下载有预编译包的依赖库（减少编译依赖的时间）
-bin/spc download --for-extensions="curl,pcntl,xml,mbstring" --prefer-pre-built
-
-# 下载所有依赖包
-bin/spc download --all
-
-# 下载所有依赖包，并指定下载的 PHP 主版本，可选：8.1，8.2，8.3，8.4，也可以使用特定的版本，如 8.3.10。
-bin/spc download --all --with-php=8.3
-
-# 下载时显示下载进度条（curl）
-bin/spc download --all --debug
-
-# 删除旧的下载数据
-bin/spc download --clean
-
-# 仅下载指定的资源（使用资源名）
-bin/spc download php-src,micro,zstd,ext-zstd
-
-# 设置重试次数
-bin/spc download --all --retry=2
-```
-
-如果你所在地区的网络不好，或者下载依赖包速度过于缓慢，可以从 GitHub Action 下载每周定时打包的 `download.zip`，并使用命令直接使用 zip 压缩包作为依赖。
-依赖包可以从 [Action](https://github.com/static-php/static-php-cli-hosted/actions/workflows/download-cache.yml) 下载到本地。
-进入 Action 并选择一个最新成功运行的 Workflow，下载 `download-files-x.y` 即可。
-
-```bash
-bin/spc download --from-zip=/path/to/your/download.zip
-```
-
-如果某个 source 始终无法下载，或者你需要下载一些特定版本的包，例如下载测试版 PHP、旧版本库等，可以使用参数 `-U` 或 `--custom-url` 重写下载链接，
-让下载器强制使用你指定的链接下载此 source 的包。使用方法为 `{source-name}:{url}` 即可，可同时重写多个库的下载地址。在使用 `--for-extensions` 选项下载时同样可用。
-
-```bash
-# 例如：指定下载 Alpha 版的 PHP8.5
-bin/spc download --all -U "php-src:https://downloads.php.net/~edorian/php-8.5.0alpha2.tar.xz"
-
-# 指定下载旧版本的 curl 库
-bin/spc download --all -U "curl:https://curl.se/download/curl-7.88.1.tar.gz"
-```
-
-如果你下载的资源不是链接，而是一个 Git 仓库，你可以使用 `-G` 或 `--custom-git` 重写下载链接，让下载器强制使用你指定的 Git 仓库下载此 source 的包。
-使用方法为 `{source-name}:{branch}:{url}` 即可，可同时重写多个库的下载地址。在使用 `--for-extensions` 选项下载时同样可用。
-
-```bash
-# 例如：下载 master 分支的 php-src
-bin/spc download --for-extensions=redis,phar -G "php-src:master:https://github.com/php/php-src.git"
-
-# 从 swoole-src 仓库下载 master 分支的最新代码，而不是发行版
-bin/spc download --for-extensions=swoole -G "swoole:master:https://github.com/swoole/swoole-src.git"
-```
-
-### 命令 doctor - 环境检查
-
-如果你可以正常运行 `bin/spc` 但无法正常编译静态的 PHP 或依赖库，可以先运行 `bin/spc doctor` 检查系统自身是否缺少依赖。
-
-```bash
-# 快速检查
-bin/spc doctor
-
-# 快速检查，并在可以自动修复的时候修复（使用包管理安装依赖包，仅支持上述提到的操作系统及发行版）
-bin/spc doctor --auto-fix
-```
-
-### 命令 build - 编译 PHP
-
-使用 build 命令可以开始构建静态 php 二进制，在执行 `bin/spc build` 命令前，务必先使用 `download` 命令下载资源，建议使用 `doctor` 检查环境。
-
-#### 基本用法
-
-你需要先到 [扩展列表](./extensions) 或 [命令生成器](./cli-generator) 选择你要加入的扩展，然后使用命令 `bin/spc build` 进行编译。你需要指定一个编译目标，从如下参数中选择：
-
-- `--build-cli`: 构建一个 cli sapi（命令行界面，可在命令行执行 PHP 代码）
-- `--build-fpm`: 构建一个 fpm sapi（php-fpm，用于和其他传统的 fpm 架构的软件如 nginx 配合使用）
-- `--build-cgi`: 构建一个 cgi sapi（cgi，可用于传统的 cgi 架构的软件如 apache 配合使用）
-- `--build-micro`: 构建一个 micro sapi（用于构建一个包含 PHP 代码的独立可执行二进制）
-- `--build-embed`: 构建一个 embed sapi（用于嵌入到其他 C 语言程序中）
-- `--build-frankenphp`: 构建一个 [frankenphp](https://github.com/php/frankenphp) 二进制
-- `--build-all`: 构建以上所有 sapi
-
-```bash
-# 编译 PHP，附带 bcmath,curl,openssl,ftp,posix,pcntl 扩展，编译目标为 cli
-bin/spc build bcmath,curl,openssl,ftp,posix,pcntl --build-cli
-
-# 编译 PHP，附带 phar,curl,posix,pcntl,tokenizer 扩展，编译目标为 micro
-bin/spc build phar,curl,posix,pcntl,tokenizer --build-micro
-```
-
-::: tip
-如果你需要重复构建、调试，你可以删除 `buildroot/` 和 `source/` 两个目录，这样你可以从已下载的源码压缩包重新解压并构建：
-
-```shell
-# remove
-rm -rf buildroot source
-# build again
-bin/spc build bcmath,curl,openssl,ftp,posix,pcntl --build-cli
-```
-:::
-
-::: tip
-如果你想构建多个版本的 PHP，且不想每次都重复构建其他依赖库，可以使用 `switch-php-version` 在编译好一个版本后快速切换至另一个版本并编译：
-
-```shell
-# switch to 8.4
-bin/spc switch-php-version 8.4
-# build
-bin/spc build bcmath,curl,openssl,ftp,posix,pcntl --build-cli
-# switch to 8.1
-bin/spc switch-php-version 8.1
-# build
-bin/spc build bcmath,curl,openssl,ftp,posix,pcntl --build-cli
-```
-:::
-
-#### 编译运行选项
-
-在编译过程中，有些特殊情况需要对编译器、编译目录的内容进行干预，可以尝试使用以下命令：
-
-- `--cc=XXX`: 指定 C 语言编译器的执行命令（Linux 默认 `musl-gcc` 或 `gcc`，macOS 默认 `clang`）
-- `--cxx=XXX`: 指定 C++ 语言编译器的执行命令（Linux 默认 `g++`，macOS 默认 `clang++`）
-- `--with-clean`: 编译 PHP 前先清理旧的 make 产生的文件
-- `--enable-zts`: 让编译的 PHP 为线程安全版本（默认为 NTS 版本）
-- `--no-strip`: 编译 PHP 库后不运行 `strip` 裁剪二进制文件缩小体积
-- `--with-libs=XXX,YYY`: 编译 PHP 前先编译指定的依赖库，激活部分扩展的可选功能（例如 gd 库的 libavif 等）
-- `--with-config-file-path=XXX`： 查找 `php.ini` 的路径（在 [这里](../faq/index.html#php-ini-的路径是什么) 查看默认路径）
-- `--with-config-file-scan-dir=XXX`： 读取 `php.ini` 后扫描 `.ini` 文件的目录（在 [这里](../faq/index.html#php-ini-的路径是什么) 查看默认路径）
-- `-I xxx=yyy`: 编译前将 INI 选项硬编译到 PHP 内（支持多个选项，别名是 `--with-hardcoded-ini`）
-- `--with-micro-fake-cli`: 在编译 micro 时，让 micro 的 SAPI 伪装为 `cli`（用于兼容一些检查 `PHP_SAPI` 的程序）
-- `--disable-opcache-jit`: 禁用 opcache jit（默认启用）
-- `-P xxx.php`: 在 static-php-cli 编译过程中注入外部脚本（详见下方 **注入外部脚本**）
-- `--without-micro-ext-test`: 在构建 micro.sfx 后，禁用测试不同扩展在 micro.sfx 的运行结果
-- `--with-suggested-exts`: 编译时将 `ext-suggests` 也作为编译依赖加入
-- `--with-suggested-libs`: 编译时将 `lib-suggests` 也作为编译依赖加入
-- `--with-upx-pack`: 编译后使用 UPX 减小二进制文件体积（需先使用 `bin/spc install-pkg upx` 安装 upx）
-- `--build-shared=XXX,YYY`: 编译时将指定的扩展编译为共享库（默认编译为静态库）
-
-硬编码 INI 选项适用于 cli、micro、embed。有关硬编码 INI 选项，下面是一个简单的例子，我们预设一个更大的 `memory_limit`，并且禁用 `system` 函数：
-
-```bash
-bin/spc build bcmath,pcntl,posix --build-all -I "memory_limit=4G" -I "disable_functions=system"
-```
-
-## 命令 micro:combine - 打包 micro 二进制
-
-使用 `micro:combine` 命令可以将上面编译好的 `micro.sfx` 和你的代码（`.php` 或 `.phar` 文件）构建为一个可执行二进制。
-你也可以使用该命令直接构建一个注入了 ini 配置的 micro 自执行二进制文件。
-
-::: tip
-注入 ini 配置指的是，在将 micro.sfx 和 PHP 源码结合前，在 micro.sfx 后追加一段特殊的结构用于保存 ini 配置项。
-
-micro.sfx 可通过特殊的字节来标识 INI 文件头，通过 INI 文件头可以实现 micro 带 INI 启动。
-
-此特性的原说明地址在 [phpmicro - Wiki](https://github.com/easysoft/phpmicro/wiki/INI-settings)，这个特性也有可能在未来发生变化。
-:::
-
-下面是常规用法，直接打包 php 源码到一个文件中：
-
-```bash
-# 在做打包流程前，你应该先使用 `build --build-micro` 编译好 micro.sfx
-echo " a.php
-bin/spc micro:combine a.php
-
-# 使用
-./my-app
-```
-
-你可以使用以下参数指定要输出的文件名，你也可以指定其他路径的 micro.sfx 进行打包。
-
-```bash
-# 指定输出文件名
-bin/spc micro:combine a.php --output=custom-bin
-# 使用绝对路径，也可以使用简化参数名
-bin/spc micro:combine a.php -O /tmp/my-custom-app
-
-# 指定其他位置的 micro.sfx 进行打包
-bin/spc micro:combine a.app --with-micro=/path/to/your/micro.sfx
-```
-
-如果想注入 ini 配置项，可以使用下面的参数，从文件或命令行选项添加 ini 到可执行文件中。
-
-```bash
-# 使用命令行选项指定（-I 是 --with-ini-set 的简写）
-bin/spc micro:combine a.php -I "a=b" -I "foo=bar"
-
-# 使用 ini 文件指定（-N 是 --with-ini-file 的简写）
-bin/spc micro:combine a.php -N /path/to/your/custom.ini
-```
-
-::: warning
-注意，请不要直接使用 PHP 源码或系统安装的 PHP 中的 `php.ini` 文件，最好手动编写一个自己需要的参数配置文件，例如：
-
-```ini
-; custom.ini
-curl.cainfo=/path/to/your/cafile.pem
-memory_limit=1G
-```
-
-该命令的注入 ini 是通过在 micro.sfx 后追加一段特殊的结构来实现的，和编译时插入硬编码 INI 的功能不同。
-:::
-
-如果要打包 phar，只需要将 `a.php` 替换为打包好的 phar 文件即可。但要注意，phar 下的 micro.sfx 需要额外注意路径问题，见 [Developing - Phar 路径问题](../develop/structure#phar-应用目录问题)
-
-## 调试
-
-如果你在编译过程中遇到了问题，或者想查看每个执行的 shell 命令，可以使用 `--debug` 开启 debug 模式，查看所有终端日志：
-
-```bash
-bin/spc build mysqlnd,pdo_mysql --build-all --debug
-```
-
-## 命令 extract - 手动解压某个库
-
-使用命令 `bin/spc extract` 可以解包和拷贝编译需要的源代码，包括 php-src 以及依赖的各种库的源码（需要自己指定要解包的库名）。
-
-例如，我们在下载好资源后，想分布执行构建流程，手动解包和拷贝包到指定位置，可以使用命令。
-
-```bash
-# 解压 php-src 和 libxml2 的下载压缩包，解压的源码存放在 source 目录
-bin/spc extract php-src,libxml2
-```
-
-## 命令 dump-extensions - 导出项目扩展依赖
-
-使用命令 `bin/spc dump-extensions` 可以导出当前项目的扩展依赖。
-
-```bash
-# 打印项目的扩展列表，传入项目包含composer.json的根目录
-bin/spc dump-extensions /path/to/your/project/
-
-# 打印项目的扩展列表，不包含开发依赖
-bin/spc dump-extensions /path-to/tour/project/ --no-dev
-
-# 输出为 spc 命令可接受的扩展列表格式（逗号分割）
-bin/spc dump-extensions /path-to/tour/project/ --format=text
-
-# 输出为 JSON 列表
-bin/spc dump-extensions /path-to/tour/project/ --format=json
-
-# 当项目没有任何扩展时，输出指定扩展组合，而不是返回失败
-bin/spc dump-extensions /path-to/your/project/ --no-ext-output=mbstring,posix,pcntl,phar
-
-# 输出时不排除 spc 不支持的扩展
-bin/spc dump-extensions /path/to/your/project/ --no-spc-filter
-```
-
-需要注意的是，项目的目录下必须包含 `vendor/installed.json` 和 `composer.lock` 文件，否则无法正常获取。
-
-## 调试命令 dev - 调试命令集合
-
-调试命令指的是你在使用 static-php-cli 构建 PHP 或改造、增强 static-php-cli 项目本身的时候，可以辅助输出一些信息的命令集合。
-
-- `dev:extensions`: 输出目前所有支持的扩展信息，或者输出指定的扩展信息
-- `dev:php-version`: 输出当前编译的 PHP 版本（通过读取 `php_version.h` 实现）
-- `dev:sort-config`: 对 `config/` 目录下的配置文件的列表按照字母表排序
-- `dev:lib-ver `: 从依赖库的源码中读取版本（仅特定依赖库可用）
-- `dev:ext-ver `: 从扩展的源码中读取对应版本（仅特定扩展可用）
-- `dev:pack-lib `: 打包指定的依赖库（仅发布者可用）
-- `dev:gen-ext-docs`: 生成扩展文档（仅发布者可用）
-
-```bash
-# 输出所有扩展
-bin/spc dev:extensions
-
-# 输出指定扩展的信息
-bin/spc dev:extensions mongodb,curl,openssl
-
-# 输出指定列，可选：lib-depends, lib-suggests, ext-depends, ext-suggests, unix-only, type
-bin/spc dev:extensions --columns=lib-depends,type,ext-depends
-
-# 输出当前编译的 PHP 版本（需要先将下载好的 PHP 源码解压到 source 目录，你可以使用 `bin/spc extract php-src` 单独解压缩源码）
-bin/spc dev:php-version
-
-# 排序配置文件 ext.json（也可以排序 lib、source）
-bin/spc dev:sort-config ext
-```
-
-## 命令 install-pkg - 下载二进制包
-
-使用命令 `bin/spc install-pkg` 可以下载一些预编译或闭源的工具，并将其安装到 `pkgroot` 目录中。
-
-在 `bin/spc doctor` 自动修复 Windows 环境时会下载 nasm、perl 等工具，使用的也是 `install-pkg` 的安装过程。
-
-下面是安装工具的示例：
-
-- 下载安装 UPX（仅限 Linux 和 Windows）: `bin/spc install-pkg upx`
-- 下载安装 nasm（仅限 Windows）: `bin/spc install-pkg nasm`
-- 下载安装 go-xcaddy: `bin/spc install-pkg go-xcaddy`
-
-## 命令 del-download - 删除已下载的资源
-
-一些情况下，你需要删除单个或多个指定的下载源文件，并重新下载他们，例如切换 PHP 版本，`2.1.0-beta.4` 版本后提供了 `bin/spc del-download` 命令，可以删除指定源文件。
-
-删除已下载的源文件包含预编译的包以及源代码，名称是 `source.json` 或 `pkg.json` 中的键名。下面是一些例子：
-
-- 删除 PHP 8.2 源码并切换下载为 8.3 版本: `bin/spc del-download php-src && bin/spc download php-src --with-php=8.3`
-- 删除 redis 扩展的下载文件: `bin/spc del-download redis`
-- 删除下载好的 musl-toolchain x86_64: `bin/spc del-download musl-toolchain-x86_64-linux`
-
-## 注入外部脚本
-
-注入外部脚本指的是在 static-php-cli 编译过程中插入一个或多个脚本，用于更灵活地支持不同环境下的参数修改、源代码补丁。
-
-一般情况下，该功能主要解决使用 `spc` 二进制进行编译时无法通过修改 static-php-cli 代码来实现修改补丁的功能。
-还有一种情况：你的项目直接依赖了 `crazywhalecc/static-php-cli` 仓库并同步，但因为项目特性需要做出一些专有的修改，而这些特性并不适合合并到主分支。
-
-鉴于以上情况，在 2.0.1 正式版本中，static-php-cli 加入了多个事件的触发点，你可以通过编写外部的 `xx.php` 脚本，并通过命令行参数 `-P` 传入并执行。
-
-在编写注入外部脚本时，你一定会用到的方法是 `builder()` 和 `patch_point()`。其中，`patch_point()` 获取的是当前正在执行的事件名称，`builder()` 获取的是 BuilderBase 对象。
-
-因为传入的注入点不区分事件，所以你必须将你要执行的代码写在 `if(patch_point() === 'your_event_name')` 中，否则会重复在其他事件中执行。
-
-下面是支持的 patch_point 事件名称及对应位置：
-
-| 事件名称 | 事件描述 |
-|------------------------------|-----------------------------------------------------------|
-| before-libs-extract | 在编译的依赖库解压前触发 |
-| after-libs-extract | 在编译的依赖库解压后触发 |
-| before-php-extract | 在 PHP 源码解压前触发 |
-| after-php-extract | 在 PHP 源码解压后触发 |
-| before-micro-extract | 在 phpmicro 解压前触发 |
-| after-micro-extract | 在 phpmicro 解压后触发 |
-| before-exts-extract | 在要编译的扩展解压到 PHP 源码目录前触发 |
-| after-exts-extract | 在要编译的扩展解压到 PHP 源码目录后触发 |
-| before-library[*name*]-build | 在名称为 `name` 的库编译前触发（如 `before-library[postgresql]-build`） |
-| after-library[*name*]-build | 在名称为 `name` 的库编译后触发 |
-| before-php-buildconf | 在编译 PHP 命令 `./buildconf` 前触发 |
-| before-php-configure | 在编译 PHP 命令 `./configure` 前触发 |
-| before-php-make | 在编译 PHP 命令 `make` 前触发 |
-| before-sanity-check | 在编译 PHP 后，运行扩展检查前触发 |
-
-下面是一个简单的临时修改 PHP 源码的例子，开启 CLI 下在当前工作目录查找 `php.ini` 配置的功能：
-
-```php
-// a.php
-php_ini_ignore_cwd = 1;',
- 'sapi_module->php_ini_ignore_cwd = 0;'
- );
-}
-```
-
-```bash
-bin/spc build mbstring --build-cli -P a.php
-echo 'memory_limit=8G' > ./php.ini
-```
-
-```
-$ buildroot/bin/php -i | grep Loaded
-Loaded Configuration File => /Users/jerry/project/git-project/static-php-cli/php.ini
-
-$ buildroot/bin/php -i | grep memory
-memory_limit => 8G => 8G
-```
-
-对于 static-php-cli 支持的对象、方法及接口，可以阅读源码，大部分的方法和对象都有相应的注释。
-
-一般使用 `-P` 功能常用的对象及函数有：
-
-- `SPC\store\FileSystem`: 文件管理类
- - `::replaceFileStr(string $filename, string $search, $replace)`: 替换文件字符串内容
- - `::replaceFileStr(string $filename, string $pattern, $replace)`: 正则替换文件内容
- - `::replaceFileUser(string $filename, $callback)`: 用户自定义函数替换文件内容
- - `::copyDir(string $from, string $to)`: 递归拷贝某个目录到另一个位置
- - `::convertPath(string $path)`: 转换路径的分隔符为当前系统分隔符
- - `::scanDirFiles(string $dir, bool $recursive = true, bool|string $relative = false, bool $include_dir = false)`: 遍历目录文件
-- `SPC\builder\BuilderBase`: 构建对象
- - `->getPatchPoint()`: 获取当前的注入点名称
- - `->getOption(string $key, $default = null)`: 获取命令行和编译时的选项
- - `->getPHPVersionID()`: 获取当前编译的 PHP 版本 ID
- - `->getPHPVersion()`: 获取当前编译的 PHP 版本号
- - `->setOption(string $key, $value)`: 设定选项
- - `->setOptionIfNotExists(string $key, $value)`: 如果选项不存在则设定选项
-
-::: tip
-static-php-cli 开放的方法非常多，文档中无法一一列举，但只要是 `public function` 并且不被标注为 `@internal`，均可调用。
-:::
-
-## 多次构建
-
-如果你在本地要多次构建，以下方法可以为你节省下载资源、编译的时间。
-
-- 仅切换 PHP 版本，不更换依赖库版本时，可以使用 `bin/spc switch-php-version` 快速切换 PHP 版本，然后重新运行同样的 `build` 命令。
-- 如果你想重新构建一次，但不重新下载源码，可以先 `rm -rf buildroot source` 删除编译目录和源码目录，然后重新构建。
-- 如果你想更新某个依赖的版本，可以使用 `bin/spc del-download ` 删除指定的源码，然后使用 `download ` 重新下载。
-- 如果你想更新所有依赖的版本，可以使用 `bin/spc download --clean` 删除所有下载的源码，然后重新下载。
-
-## embed 使用
-
-如果你想将 static-php 嵌入到其他 C 语言程序中，可以使用 `--build-embed` 构建一个 embed 版本的 PHP。
-
-```bash
-bin/spc build {your extensions} --build-embed --debug
-```
-
-在通常的情况下，PHP embed 编译后会生成 `php-config`。对于 static-php，我们提供了 `spc-config`，用于获取编译时的参数。
-另外，在使用 embed SAPI（libphp.a）时，你需要使用和编译 libphp 相同的编译器，否则会出现链接错误。
-
-下面是 spc-config 的基本用法：
-
-```bash
-# output all flags and options
-bin/spc spc-config curl,zlib,phar,openssl
-
-# output libs
-bin/spc spc-config curl,zlib,phar,openssl --libs
-
-# output includes
-bin/spc spc-config curl,zlib,phar,openssl --includes
-```
-
-默认情况下，static-php 在不同系统使用的编译器分别是：
-
-- macOS: `clang`
-- Linux (Alpine Linux): `gcc`
-- Linux (glibc based distros, x86_64): `/usr/local/musl/bin/x86_64-linux-musl-gcc`
-- Linux (glibc based distros, aarch64): `/usr/local/musl/bin/aarch64-linux-musl-gcc`
-- FreeBSD: `clang`
-
-下面是一个使用 embed SAPI 的例子：
-
-```c
-// embed.c
-#include
-
-int main(int argc,char **argv){
-
- PHP_EMBED_START_BLOCK(argc,argv)
-
- zend_file_handle file_handle;
-
- zend_stream_init_filename(&file_handle,"embed.php");
-
- if(php_execute_script(&file_handle) == FAILURE){
- php_printf("Failed to execute PHP script.\n");
- }
-
- PHP_EMBED_END_BLOCK()
- return 0;
-}
-```
-
-
-```php
- hello.php
+spc micro:combine hello.php --output=hello
+./hello
+
+# 打包 phar 文件
+spc micro:combine your-app.phar --output=your-app
+./your-app
+```
+
+### 注入 INI 配置
+
+打包时可以通过命令行参数或 ini 文件注入运行时配置：
+
+```bash
+# 通过命令行参数注入（-I 是 --with-ini-set 的简写）
+spc micro:combine your-app.phar --output=your-app -I "memory_limit=512M" -I "curl.cainfo=/etc/ssl/certs/ca-certificates.crt"
+
+# 通过 ini 文件注入（-N 是 --with-ini-file 的简写）
+spc micro:combine your-app.phar --output=your-app -N /path/to/custom.ini
+```
+
+::: tip
+`-I` 注入的 INI 是运行时配置，通过在 `micro.sfx` 末尾追加特殊结构实现。这与编译时用 `-I` 硬编码 INI 不同，两者可以共存。
+:::
+
+### 伪装为 cli SAPI
+
+部分框架会检查 `PHP_SAPI` 的值，并限制在非 `cli` 环境下运行。`micro` 的 `PHP_SAPI` 默认值为 `micro`，可通过编译参数让其伪装为 `cli`：
+
+```bash
+spc build:php "bcmath,phar" --build-micro --with-micro-fake-cli
+```
+
+### 指定自定义 micro.sfx 路径
+
+```bash
+spc micro:combine your-app.phar --output=your-app --with-micro=/path/to/your/micro.sfx
+```
+
+### 关于 phar 的路径问题
+
+将应用打包为 phar 后，phar 内部使用相对路径可能与预期不符。请参考[开发者文档 - Phar 目录问题](../develop/structure)了解详情。
+
+## embed
+
+`embed` SAPI 将 PHP 编译为静态库（Linux/macOS 下为 `libphp.a`，Windows 下为 `php8embed.lib`），可嵌入到其他 C/C++ 程序中运行 PHP 代码。
+
+### 构建
+
+```bash
+spc build:php "bcmath,openssl" --build-embed
+```
+
+产物：
+- Linux/macOS：`buildroot/lib/libphp.a`，头文件在 `buildroot/include/`
+- Windows：`buildroot/lib/php8embed.lib`，头文件在 `buildroot/include/`
+
+完整选项参见 [build:php — SAPI 选择](./cli-reference#sapi-selection)、[build:php — 通用构建选项](./cli-reference#common-build-options) 和 [build:php — embed 专用选项](./cli-reference#embed-options)。
+
+::: tip
+如何将 `libphp.a` / `php8embed.lib` 链接到你自己的项目（包括编译器选择、`dev:shell` 使用方式和完整 C 示例），将在开发者文档中专门介绍。
+:::
+
+## frankenphp
+
+`frankenphp` 是基于 [FrankenPHP](https://github.com/php/frankenphp) 的现代 PHP 应用服务器，内置 Caddy，支持 HTTP/2、HTTP/3、自动 HTTPS 等特性。
+
+::: tip
+StaticPHP 构建出的 `frankenphp` 是单个完全自包含的可执行文件。这与 FrankenPHP 官方提供的发行版不同，官方版本为动态链接二进制，需要单独安装 PHP。
+:::
+
+::: warning
+FrankenPHP 必须启用线程安全模式，构建时务必加上 `--enable-zts`。
+:::
+
+### 构建
+
+```bash
+spc build:php "bcmath,openssl,curl,pdo_mysql" --build-frankenphp --enable-zts
+```
+
+Linux/macOS 下产物为 `buildroot/bin/frankenphp`，Windows 下为 `buildroot/bin/frankenphp.exe`。
+
+完整选项参见 [build:php — SAPI 选择](./cli-reference#sapi-selection)、[build:php — 通用构建选项](./cli-reference#common-build-options) 和 [build:php — frankenphp 专用选项](./cli-reference#frankenphp-options)。
+
+### 使用
+
+```bash
+# 查看版本
+./buildroot/bin/frankenphp version
+
+# 以 PHP 内置服务器模式运行（用于开发调试）
+./buildroot/bin/frankenphp php-server
+
+# 运行 Worker 模式
+./buildroot/bin/frankenphp run --config /path/to/Caddyfile
+```
+
+更多用法请参考 [FrankenPHP 官方文档](https://frankenphp.dev/docs/)。
+
+## 动态扩展加载
+
+静态 PHP 二进制是否能够通过 `dl()` 在运行时加载扩展，取决于其链接方式。
+
+**macOS** — 构建产物始终动态链接系统库，支持通过 `dl()` 或 `php.ini` 在运行时加载 `.so` 扩展。
+
+**Linux** — StaticPHP 默认构建目标为 `native-native-musl`：完全静态链接 musl libc 的二进制。由于运行时不存在动态链接器，`dl()` 被禁用，FFI 扩展无法使用，也无法加载任何外部 `.so` 扩展。
+
+如需在 Linux 上支持动态扩展加载，请在构建前设置 `SPC_TARGET` 环境变量：
+
+```bash
+SPC_TARGET=native-native-gnu.2.17 spc build:php "bcmath,openssl" --build-cli
+```
+
+如果你采用的是源码安装，也可以在 `config/env.ini` 中设置 `SPC_TARGET=native-native-gnu.2.17`，将其作为所有构建的默认值。
+
+这将使用 Zig 工具链构建出一个准静态二进制，动态链接 glibc 2.17，可运行于大多数现代 GNU/Linux 发行版，无需 Docker，也无需额外的交叉编译工具链。该产物支持 `dl()`、FFI 和运行时加载 `.so` 扩展，但无法运行于 Alpine Linux 等基于 musl 的系统。
+
+**Windows** — Windows 上的 PHP 扩展均以 `.dll` 形式分发，且依赖官方动态构建的 PHP 中附带的 DLL 文件。StaticPHP 构建的静态 PHP 可执行文件不包含这些 DLL，因此 Windows 不支持动态扩展加载，所有扩展必须在构建时静态编译进去。
+
diff --git a/docs/zh/guide/troubleshooting.md b/docs/zh/guide/troubleshooting.md
index c65236547..da00dc622 100644
--- a/docs/zh/guide/troubleshooting.md
+++ b/docs/zh/guide/troubleshooting.md
@@ -1,6 +1,6 @@
# 故障排除
-使用 static-php-cli 过程中可能会碰到各种各样的故障，这里将讲述如何自行查看错误并反馈 Issue。
+使用 StaticPHP 过程中可能会碰到各种各样的故障，这里将讲述如何自行查看错误并反馈 Issue。
## 下载失败问题
@@ -8,7 +8,7 @@
在遇到下载失败后，可以多次尝试调用下载命令。
当下载资源时，你可能最终会看到类似 `curl: (56) The requested URL returned error: 403` 的错误，这通常是由于 GitHub 限制导致的。
-你可以通过在命令中添加 `--debug` 来验证，会看到类似 `[DEBU] Running command (no output) : curl -sfSL "https://api.github.com/repos/openssl/openssl/releases"` 的输出。
+你可以通过在命令中添加 `-vvv` 来验证，会看到类似 `[DEBU] Running command (no output) : curl -sfSL "https://api.github.com/repos/openssl/openssl/releases"` 的输出。
要解决这个问题，可以在 GitHub 上 [创建](https://github.com/settings/tokens) 一个个人访问令牌，并将其设置为环境变量 `GITHUB_TOKEN=`。
@@ -24,8 +24,9 @@
## 编译错误
-遇到编译错误时，如果没有开启 `--debug` 日志，请先开启调试日志，然后确定报错的命令。
+遇到编译错误时，如果没有开启 `-vvv` 日志，请先开启调试日志，然后确定报错的命令。
报错的终端输出对于修复编译错误非常重要。
在提交 Issue 时，请上传终端日志的最后报错片段（或整个终端日志输出），并且包含使用的 `spc` 命令和参数。
-如果你是重复构建，请参考 [本地构建 - 多次构建](./manual-build#多次构建) 章节。
+如果你是重复构建，请参考 [首次构建 - 调试与重新构建](./first-build#调试与重新构建) 章节。
+
diff --git a/docs/zh/index.md b/docs/zh/index.md
index 265d39745..71d12be00 100644
--- a/docs/zh/index.md
+++ b/docs/zh/index.md
@@ -3,23 +3,26 @@
layout: home
hero:
- name: "Static PHP"
- tagline: "在 Linux、macOS、FreeBSD、Windows 上与 PHP 项目一起构建独立的 PHP 二进制文件，并包含流行的扩展。"
+ name: "StaticPHP"
+ tagline: "StaticPHP 是一款强大的工具，旨在构建包含 PHP、扩展等在内的可移植可执行文件。"
image:
src: /images/static-php_nobg.png
- alt: Static PHP CLI Logo
+ alt: StaticPHP Logo
actions:
- theme: brand
text: 开始使用
- link: ./guide/
+ link: /zh/guide/
+ - theme: alt
+ text: English Docs
+ link: /en/
features:
- title: 静态 CLI 二进制
- details: 您可以轻松地编译一个独立的 PHP 二进制文件以供通用使用，包括 CLI、FPM SAPI。
+ details: 您可以轻松编译一个可独立运行的 PHP 二进制文件用于通用场景，支持 CLI、FPM、CGI、FrankenPHP SAPI。
- title: Micro 自解压可执行文件
- details: 您可以编译一个自解压的可执行文件，并将 PHP 源代码与二进制文件打包在一起。
+ details: 您可以编译一个自解压可执行文件，并通过 Micro SAPI 将其与 PHP 源代码一起构建。
- title: 依赖管理
- details: static-php-cli 附带依赖项管理，支持安装不同类型的 PHP 扩展。
+ details: StaticPHP 内置依赖管理，支持安装不同类型的 PHP 扩展、包和库。
---
-
-
-
-## 开源许可证
-
-本项目本身基于 MIT 许可证，
-一些新添加的扩展和依赖可能来自其他项目，
-这些代码文件的头部也会给出额外的许可证和作者说明。
-
-这些是类似的项目：
-
-- [dixyes/lwmbs](https://github.com/dixyes/lwmbs)
-- [swoole/swoole-cli](https://github.com/swoole/swoole-cli)
-
-本项目使用了 [dixyes/lwmbs](https://github.com/dixyes/lwmbs) 的一些代码，例如 Windows 静态构建目标和 libiconv 支持。
-lwmbs 基于 [Mulan PSL 2](http://license.coscl.org.cn/MulanPSL2) 许可证。
-
-由于本项目的特殊性，
-项目编译过程中会使用许多其他开源项目，如 curl 和 protobuf，
-它们都有自己的开源许可证。
-
-请在编译后使用 `bin/spc dump-license` 命令导出项目中使用的开源许可证，
-并遵守相应项目的 LICENSE。
+# StaticPHP
+
+[](README-zh.md)
+[](README.md)
+[](https://github.com/crazywhalecc/static-php-cli/releases)
+[](https://github.com/crazywhalecc/static-php-cli/actions/workflows/tests.yml)
+[](https://github.com/crazywhalecc/static-php-cli/blob/main/LICENSE)
+
+**StaticPHP** 是一个强大的工具，用于构建可移植的可执行文件，包括 PHP、扩展等。
+
+## 特性
+
+- :elephant: 支持多个 PHP 版本 - PHP 8.1, 8.2, 8.3, 8.4, 8.5
+- :handbag: 构建零依赖的单文件 PHP 可执行程序
+- :hamburger: 构建 **[phpmicro](https://github.com/static-php/phpmicro)** 自解压可执行文件（将 PHP 二进制和源码合并为单个文件）
+- :pill: 自动构建环境检查器，支持自动修复
+- :zap: 支持 `Linux`、`macOS`、`Windows`
+- :wrench: 通过 vendor 模式和自定义注册表实现便捷扩展
+- :books: 智能依赖管理
+- 📦 自包含 `spc` 可执行文件，便于自安装
+- :fire: 支持 100+ 热门 [PHP 扩展](https://static-php.dev/en/guide/extensions.html)
+- :floppy_disk: 支持 UPX 压缩（二进制体积可缩小 30-50%）
+
+**单文件独立 php-cli：**
+
+