القائمة
Use when building Objective-C or Objective-C++ projects with xmake — `.m` / `.mm` sources, Cocoa / Foundation frameworks via `add_frameworks`, mixing with C++, and targeting macOS / iOS / tvOS.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | xmake-objc |
| description | Use when building Objective-C or Objective-C++ projects with xmake — `.m` / `.mm` sources, Cocoa / Foundation frameworks via `add_frameworks`, mixing with C++, and targeting macOS / iOS / tvOS. |
Objective-C (.m) and Objective-C++ (.mm) are first-class in xmake. Primary use case: macOS / iOS / tvOS apps, Cocoa frameworks, and mixed C++ / Objective-C projects.
add_rules("mode.debug", "mode.release")
target("hello")
set_kind("binary")
add_files("src/*.m")
add_frameworks("Foundation")
// src/main.m
#import <Foundation/Foundation.h>
int main() {
@autoreleasepool {
NSLog(@"hello from xmake");
}
return 0;
}
Use .mm extension and set the C++ language level:
target("app")
set_kind("binary")
set_languages("c++17")
add_files("src/*.mm", "src/*.cpp")
add_frameworks("Foundation", "AppKit")
.mm files compile with the Objective-C++ front-end — you can freely mix @interface/@implementation with C++ classes and templates.
target("app")
add_frameworks("Foundation", "Cocoa", "AppKit", "Metal", "MetalKit", "CoreGraphics")
add_frameworkdirs("/Library/Frameworks", "$(projectdir)/vendor/frameworks")
add_frameworks(...) — system or user frameworks (equivalent of -framework <name>).add_frameworkdirs(...) — additional search paths for non-system frameworks.target("app")
add_mflags("-fobjc-arc") -- Objective-C flag (.m)
add_mxxflags("-fobjc-arc") -- Objective-C++ flag (.mm)
add_mflags / add_mxxflags target .m / .mm respectively; add_cxflags still flows through to both.
ARC is the default in modern Xcode; include -fobjc-arc explicitly if you want to be sure.
xmake f -p macosx -a arm64
xmake f -p iphoneos -a arm64
xmake f -p iphonesimulator -a arm64
xmake f -p appletvos -a arm64
xmake f -p watchos -a arm64
xmake
Pin SDK version and minimum deployment:
xmake f -p iphoneos --xcode_sdkver=17.2 --target_minver=14.0
For a proper .app bundle on macOS:
target("myapp")
add_rules("xcode.application") -- produces .app
add_files("src/*.m", "res/*.storyboard", "res/*.xcassets")
add_files("res/Info.plist")
add_frameworks("Foundation", "AppKit")
iOS app:
target("myapp")
add_rules("xcode.application")
set_plat("iphoneos")
add_files("src/*.m", "res/Info.plist")
add_frameworks("Foundation", "UIKit")
xcode.application is a built-in rule that produces a proper bundle with Info.plist, code signing hooks, etc.
See xmake-swift — Swift interop picks up Objective-C headers via set_values("swift.interop", "objc").
Objective-C is a strict superset of C, so a .m file can #include <stdio.h> freely. Pure C headers compile inside .m/.mm files without extra flags.
.mm without set_languages("c++XX"). Defaults to C++98 which is almost never what you want. Set it explicitly.add_frameworks("SwiftUI") fails on old macOS SDKs. Pin with --xcode_sdkver= or gate with is_plat + minver.-fobjc-arc on old code. Pre-ARC code uses retain/release; modern code uses ARC. Don't mix arbitrarily.xcode.application needs an Info.plist in add_files or it produces a broken bundle.xmake-cross-compilation, xmake-toolchainsxmake-swiftxmake-targetsxmake-xpackUse when switching xmake's output theme (colors, progress style, emoji) or fixing garbled/unreadable terminal output — `xmake g --theme=...`. Built-in themes: default, ninja, emoji, dark, light, plain, powershell.
Use when the user is starting a new Xmake project, installing Xmake, or needs the minimal xmake.lua structure. Covers installation, `xmake create`, the project layout, and the smallest valid xmake.lua.
Use when writing or reviewing an `xmake.lua` (project, package recipe, or toolchain) and you want to follow idiomatic xmake style — description vs script domain separation, naming, indentation, `set_` vs `add_`, option/config organization, and common conventions used across xmake-repo and the xmake project itself. Apply this alongside `xmake-targets`/`xmake-packages`/etc. as a stylistic overlay.
Use when creating a new xmake project from a built-in or third-party template (`xmake create -t <template>`), listing available templates, or authoring and distributing custom templates (built-in, user-global, or via xmake-repo). Covers template layout, `${TARGET_NAME}` / `${FAQ}` substitution, and language selection.
Use when invoking Xmake from the command line — configuring, building, running, cleaning, installing, packing, or inspecting a project. Covers the common flags for `xmake f`, `xmake`, `xmake run`, `xmake install`, `xmake pack`, and friends.
Use when exporting an xmake project to another build system or IDE — `compile_commands.json` for clangd/LSP, `CMakeLists.txt`, `build.ninja`, Visual Studio solution (`vsxmake`), or an Xcode project. Covers `xmake project -k <kind>` and how each generator is typically used.