Compilar para macOS
Nota
Esta página describe cómo compilar el editor y las plantillas de exportación de macOS desde el código fuente. Si estás buscando exportar tu proyecto a macOS, lee Exportando para macOS.
Requerimientos
Para compilar en macOS, se requiere lo siguiente:
SCons 4.0+ build system.
Xcode (o las herramientas de línea de comandos más ligeras para Xcode).
Vulkan SDK for MoltenVK (macOS doesn't support Vulkan out of the box). The latest Vulkan SDK version can be installed quickly by running
misc/scripts/install_vulkan_sdk_macos.shwithin the Godot source repository.
Nota
If you have Homebrew installed, you can easily install SCons using the following command:
brew install scons
La instalación de Homebrew también descargará automáticamente las Command Line Tools para Xcode si aún no las tienes.
Similarly, if you have MacPorts installed, you can easily install SCons using the following command:
sudo port install scons
Ver también
Para obtener el código fuente de Godot para compilarlo, consulta la sección Consiguiendo el código fuente.
Para obtener una visión general del uso de SCons para Godot, consulta la sección Introducción al sistema de compilación.
Compilar
Para comenzar, abre una terminal y ve al directorio raíz del código fuente del motor (game engine).
To compile for Intel (x86-64) powered Macs, use:
scons platform=macos arch=x86_64
To compile for Apple Silicon (ARM64) powered Macs, use:
scons platform=macos arch=arm64
Truco
If you are compiling Godot to make changes or contribute to the engine,
you may want to use the SCons options dev_build=yes or dev_mode=yes.
See Development and production aliases
for more info.
If all goes well, the resulting binary executable will be placed in the
bin/ subdirectory. This executable file contains the whole engine and
runs without any dependencies. Executing it will bring up the Project
Manager.
Nota
Using a standalone editor executable is not recommended, it should be always packaged into a
.app bundle to avoid UI activation issues.
Nota
Si deseas utilizar configuraciones de editor separadas para tus propias compilaciones de Godot y las versiones oficiales, puedes habilitar Modo autónomo creando un archivo llamado ._sc_ o _sc_ en la carpeta bin/.
Creación automática de paquetes .app
To automatically create a .app bundle like in the official builds, use the generate_bundle=yes option on the last
SCons command used to build editor:
scons platform=macos arch=x86_64
scons platform=macos arch=arm64 generate_bundle=yes
Manual .app bundle creation
To support both architectures in a single "Universal 2" binary,
run the above two commands and then use lipo to bundle them together:
lipo -create bin/godot.macos.editor.x86_64 bin/godot.macos.editor.arm64 -output bin/godot.macos.editor.universal
To create a .app bundle, you need to use the template located in misc/dist/macos_tools.app. Typically, for an optimized
editor binary built with dev_build=yes:
cp -r misc/dist/macos_tools.app ./bin/Godot.app
mkdir -p bin/Godot.app/Contents/MacOS
cp bin/godot.macos.editor.universal bin/Godot.app/Contents/MacOS/Godot
chmod +x bin/Godot.app/Contents/MacOS/Godot
codesign --force --timestamp --options=runtime --entitlements misc/dist/macos/editor.entitlements -s - bin/Godot.app
Nota
If you are building the master branch, you also need to include support
for the MoltenVK Vulkan portability library. By default, it will be linked
statically from your installation of the Vulkan SDK for macOS.
You can also choose to link it dynamically by passing use_volk=yes and
including the dynamic library in your .app bundle:
mkdir -p <Godot bundle name>.app/Contents/Frameworks
cp <Vulkan SDK path>/macOS/lib/libMoltenVK.dylib <Godot bundle name>.app/Contents/Frameworks/libMoltenVK.dylib
Running a headless/server build
To run in headless mode which provides editor functionality to export projects in an automated manner, use the normal build:
scons platform=macos target=editor
And then use the --headless command line argument:
./bin/godot.macos.editor.x86_64 --headless
To compile a debug server build which can be used with remote debugging tools, use:
scons platform=macos target=template_debug
To compile a release server build which is optimized to run dedicated game servers, use:
scons platform=macos target=template_release production=yes
Construyendo plantillas de exportación
To build macOS export templates, you have to compile using the targets without
the editor: target=template_release (release template) and
target=template_debug.
Official templates are Universal 2 binaries which support both ARM64 and Intel x86_64 architectures.
To support ARM64 (Apple Silicon) + Intel x86_64:
scons platform=macos target=template_debug arch=arm64 scons platform=macos target=template_release arch=arm64 scons platform=macos target=template_debug arch=x86_64 scons platform=macos target=template_release arch=x86_64 generate_bundle=yes
To support ARM64 (Apple Silicon) only (smaller file size, but less compatible with older hardware):
scons platform=macos target=template_debug arch=arm64 scons platform=macos target=template_release arch=arm64 generate_bundle=yes
To create a .app bundle like in the official builds, you need to use the
template located in misc/dist/macos_template.app. This process can be automated by using
the generate_bundle=yes option on the last SCons command used to build export templates
(so that all binaries can be included). This option also takes care of calling lipo to create
a Universal 2 binary from two separate ARM64 and x86_64 binaries (if both were compiled beforehand).
Nota
You also need to include support for the MoltenVK Vulkan portability
library. By default, it will be linked statically from your installation of
the Vulkan SDK for macOS. You can also choose to link it dynamically by
passing use_volk=yes and including the dynamic library in your .app
bundle:
mkdir -p macos_template.app/Contents/Frameworks
cp <Vulkan SDK path>/macOS/libs/libMoltenVK.dylib macos_template.app/Contents/Frameworks/libMoltenVK.dylib
In most cases, static linking should be preferred as it makes distribution easier. The main upside of dynamic linking is that it allows updating MoltenVK without having to recompile export templates.
You can then zip the macos_template.app folder to reproduce the macos.zip
template from the official Godot distribution:
zip -r9 macos.zip macos_template.app
Compilar para macOS desde Linux
Es posible compilar para macOS en un entorno Linux (y tal vez también en Windows utilizando el Subsistema de Windows para Linux). Para ello, deberás instalar OSXCross para poder utilizar macOS como destino. Primero, sigue las instrucciones para instalarlo:
Clone the OSXCross repository somewhere on your machine (or download a ZIP file and extract it somewhere), e.g.:
git clone --depth=1 https://github.com/tpoechtrager/osxcross.git "$HOME/osxcross"
Sigue las instrucciones para empaquetar el SDK en el siguiente enlace: https://github.com/tpoechtrager/osxcross#packaging-the-sdk
Para instalar OSXCross, sigue las instrucciones en el siguiente enlace: https://github.com/tpoechtrager/osxcross#installation
After that, you will need to define the OSXCROSS_ROOT as the path to
the OSXCross installation (the same place where you cloned the
repository/extracted the zip), e.g.:
export OSXCROSS_ROOT="$HOME/osxcross"
Now you can compile with SCons like you normally would:
scons platform=macos
If you have an OSXCross SDK version different from the one expected by the SCons buildsystem, you can specify a custom one with the osxcross_sdk argument:
scons platform=macos osxcross_sdk=darwin15
Solución De Problemas
Fatal error: 'cstdint' file not found
If you get a compilation error of this form early on, it's likely because the Xcode command line tools installation needs to be repaired after a macOS or Xcode update:
./core/typedefs.h:45:10: fatal error: 'cstdint' file not found
45 | #include <cstdint>
| ^~~~~~~~~
Run these two commands to reinstall Xcode command line tools (enter your administrator password as needed):
sudo rm -rf /Library/Developer/CommandLineTools
sudo xcode-select --install
If it still does not work, try updating Xcode from the Mac App Store and try again.