メニュー
Use when building Fortran projects with xmake — binary/library targets with `.f`/`.f90`/`.for` sources, gfortran or Intel Fortran (`ifort`) toolchain selection, and mixing Fortran with C interoperability.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use 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.
| name | xmake-fortran |
| description | Use when building Fortran projects with xmake — binary/library targets with `.f`/`.f90`/`.for` sources, gfortran or Intel Fortran (`ifort`) toolchain selection, and mixing Fortran with C interoperability. |
Xmake supports Fortran since v2.3.6 via gfortran, and Intel Fortran (ifort) since v2.3.8.
xmake create -l fortran -t console hello
cd hello
xmake run
add_rules("mode.debug", "mode.release")
target("hello")
set_kind("binary")
add_files("src/*.f90")
Recognized extensions: .f, .F, .f90, .F90, .f95, .F95, .f03, .F03, .f08, .F08, .for, .FOR. The uppercase variants get preprocessed.
target("app") set_kind("binary")
target("mylib") set_kind("static")
target("mydyn") set_kind("shared")
xmake f --toolchain=gfortran # default gfortran
xmake f --toolchain=ifort # Intel Fortran
xmake f --toolchain=ifx # Intel oneAPI LLVM-based Fortran
Pin a specific install with --sdk=/opt/intel/oneapi.
target("app")
add_files("src/*.f90")
add_fcflags("-O3", "-ffree-form") -- gfortran flags
add_ldflags("-lm")
add_fcflags = Fortran compiler flags.
target("solver")
set_kind("static")
add_files("src/*.f90", "src/*.c")
add_includedirs("include", {public = true})
target("app")
set_kind("binary")
add_files("src/main.cpp")
add_deps("solver")
set_languages("c++17")
Use iso_c_binding on the Fortran side and extern "C" on the C++ side. Xmake handles the link step — gfortran's runtime is added automatically when Fortran objects are present.
Fortran module/end module produces .mod files. Xmake tracks them automatically for dependency ordering — list source files in add_files in any order; xmake scans USE statements.
.f/.for default to fixed form (columns matter); .f90+ default to free form. Flag overrides work per-file if needed..mod leaking across targets. Each target has its own module cache. Share modules by linking the static/shared library and letting xmake propagate the -I path.ifort and ifx differ from gfortran in many flag names. Gate with is_toolchain.xmake-targetsxmake-cross-compilationxmake-targets