Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/en/manuals/bob.md
Original file line number Diff line number Diff line change
Expand Up @@ -197,8 +197,8 @@ Available platforms and architectures:
`arm64-linux`
: Linux ARM64 for Raspberry Pi and Linux-based handheld devices.

`x86_64-ios`
: iOS macOS 64 bit (iOS Simulator)
`arm64_sim-ios`
: iOS Simulator on Apple Silicon Macs. Simulator bundles do not use a signing identity or provisioning profile, so `--identity` and `--mobileprovisioning` are ignored.

`arm64-ios`
: iOS 64 bit. By default, `--architectures` argument value is `arm64-ios`.
Expand Down
2 changes: 1 addition & 1 deletion docs/en/manuals/extensions-best-practices.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ In certain places, the platform architecture is used as a folder name, to know w

The current list is:

arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
arm64-ios, arm64_sim-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32

So for instance, put platform specific libraries under:

Expand Down
2 changes: 1 addition & 1 deletion docs/en/manuals/extensions-ext-manifests.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ platforms:
libs: ["z", "c++", "sqlite3"]
defines: ["MY_DEFINE"]

armv7-ios:
arm64_sim-ios:
context:
frameworks: ["CoreGraphics", "CFNetwork", "GLKit", "CoreMotion", "MessageUI", "MediaPlayer", "StoreKit", "MobileCoreServices", "AdSupport", "AudioToolbox", "AVFoundation", "CoreGraphics", "CoreMedia", "CoreMotion", "CoreTelephony", "CoreVideo", "Foundation", "GLKit", "JavaScriptCore", "MediaPlayer", "MessageUI", "MobileCoreServices", "OpenGLES", "SafariServices", "StoreKit", "SystemConfiguration", "UIKit", "WebKit"]
flags: ["-stdlib=libc++"]
Expand Down
4 changes: 2 additions & 2 deletions docs/en/manuals/ios.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,10 +91,10 @@ When you have the code signing identity and provisioning profile, you are ready

![Signing iOS bundle](images/ios/sign_bundle.png)

Select your code signing identity and browse for your mobile provisioning file. Select the `arm64-ios` device architecture and, when needed, the `x86_64-ios` simulator architecture, as well as the variant (Debug or Release). You can optionally uncheck the `Sign application` checkbox to skip the signing process and then manually sign at a later stage.
Select your code signing identity and browse for your mobile provisioning file, as well as the variant (Debug or Release). You can optionally uncheck the `Sign application` checkbox to skip the signing process and then manually sign at a later stage. Check `Simulator` to create an `arm64_sim-ios` bundle for the iOS Simulator instead of a device bundle.

::: important
You **must** uncheck the `Sign application` checkbox when testing your game on the iOS simulator. You will be able to install the application but it will not boot.
Simulator bundles run only in the iOS Simulator on Apple Silicon Macs. They do not use a signing identity or provisioning profile, so the signing, install and launch options are disabled when `Simulator` is checked. Install the bundle with `xcrun simctl` as described below.
:::

Press *Create Bundle* and you will then be prompted to specify where on your computer the bundle will be created.
Expand Down
2 changes: 1 addition & 1 deletion docs/en/shared/platforms.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
Supported platforms are `ios`, `android`, `osx`, `win32`, `linux`, `web`.

Supported `arc-platform` pairs are `arm64-ios`, `x86_64-ios`, `armv7-android`, `arm64-android`, `x86_64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web` and `wasm_pthread-web`.
Supported `arc-platform` pairs are `arm64-ios`, `arm64_sim-ios`, `armv7-android`, `arm64-android`, `x86_64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web` and `wasm_pthread-web`.
4 changes: 2 additions & 2 deletions docs/es/manuals/bob.md
Original file line number Diff line number Diff line change
Expand Up @@ -197,8 +197,8 @@ Plataformas y arquitecturas disponibles:
`arm64-linux`
: Linux ARM64 para Raspberry Pi y dispositivos portátiles basados en Linux.

`x86_64-ios`
: iOS macOS 64 bits (iOS Simulator)
`arm64_sim-ios`
: iOS Simulator en Macs con Apple Silicon. Los bundles para el simulador siempre se firman ad-hoc, por lo que `--identity` y `--mobileprovisioning` se ignoran.

`arm64-ios`
: iOS 64 bits. De forma predeterminada, el valor del argumento `--architectures` es `arm64-ios`.
Expand Down
2 changes: 1 addition & 1 deletion docs/es/manuals/extensions-best-practices.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ En ciertos lugares, la arquitectura de la plataforma se usa como nombre de carpe

La lista actual es:

arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
arm64-ios, arm64_sim-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32

Por ejemplo, coloca las bibliotecas específicas de plataforma en:

Expand Down
2 changes: 1 addition & 1 deletion docs/es/manuals/extensions-ext-manifests.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ platforms:
libs: ["z", "c++", "sqlite3"]
defines: ["MY_DEFINE"]

armv7-ios:
arm64_sim-ios:
context:
frameworks: ["CoreGraphics", "CFNetwork", "GLKit", "CoreMotion", "MessageUI", "MediaPlayer", "StoreKit", "MobileCoreServices", "AdSupport", "AudioToolbox", "AVFoundation", "CoreGraphics", "CoreMedia", "CoreMotion", "CoreTelephony", "CoreVideo", "Foundation", "GLKit", "JavaScriptCore", "MediaPlayer", "MessageUI", "MobileCoreServices", "OpenGLES", "SafariServices", "StoreKit", "SystemConfiguration", "UIKit", "WebKit"]
flags: ["-stdlib=libc++"]
Expand Down
4 changes: 2 additions & 2 deletions docs/es/manuals/ios.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,10 +91,10 @@ Cuando tengas la identidad de firmado de código y el perfil provisional, estar

![Firmar bundle iOS](images/ios/sign_bundle.png)

Selecciona tu identidad de firmado de código y busca tu archivo de mobile provisioning. Selecciona la arquitectura de dispositivo `arm64-ios` y, cuando sea necesario, la arquitectura de simulador `x86_64-ios`, así como la variante (Debug o Release). Opcionalmente puedes desmarcar la casilla `Sign application` para omitir el proceso de firmado y firmar manualmente en una etapa posterior.
Selecciona tu identidad de firmado de código y busca tu archivo de mobile provisioning, así como la variante (Debug o Release). Opcionalmente puedes desmarcar la casilla `Sign application` para omitir el proceso de firmado y firmar manualmente en una etapa posterior. Marca `Simulator` para crear un bundle `arm64_sim-ios` para el iOS Simulator en lugar de un bundle para dispositivo.

::: important
**Debes** desmarcar la casilla `Sign application` al probar tu juego en el simulador de iOS. Podrás instalar la aplicación, pero no arrancará.
Los bundles para el simulador solo se ejecutan en el iOS Simulator en Macs con Apple Silicon. Siempre se firman ad-hoc, por lo que las opciones de firmado, instalación y lanzamiento se desactivan cuando `Simulator` está marcado. Instala el bundle con `xcrun simctl` como se describe más abajo.
:::

Pulsa *Create Bundle* y se te pedirá que especifiques en qué lugar de tu computadora se creará el bundle.
Expand Down
2 changes: 1 addition & 1 deletion docs/es/shared/platforms.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
Las plataformas compatibles son `ios`, `android`, `osx`, `win32`, `linux`, `web`.

Los pares `arc-platform` compatibles son `arm64-ios`, `x86_64-ios`, `armv7-android`, `arm64-android`, `x86_64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web` y `wasm_pthread-web`.
Los pares `arc-platform` compatibles son `arm64-ios`, `arm64_sim-ios`, `armv7-android`, `arm64-android`, `x86_64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web` y `wasm_pthread-web`.
4 changes: 2 additions & 2 deletions docs/ko/manuals/bob.md
Original file line number Diff line number Diff line change
Expand Up @@ -197,8 +197,8 @@ usage: bob [options] [commands]
`arm64-linux`
: Raspberry Pi 및 Linux 기반 휴대용 기기용 Linux ARM64

`x86_64-ios`
: iOS macOS 64 bit (iOS Simulator)
`arm64_sim-ios`
: Apple Silicon Mac용 iOS Simulator. Simulator 번들은 항상 ad-hoc 서명되므로 `--identity`와 `--mobileprovisioning`은 무시됩니다.

`arm64-ios`
: iOS 64 bit. 기본적으로 `--architectures` 인자 값은 `arm64-ios`입니다.
Expand Down
2 changes: 1 addition & 1 deletion docs/ko/manuals/extensions-best-practices.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ Lua API는 하나만 있어야 하며, 그 구현도 하나만 있어야 합니

현재 목록은 다음과 같습니다.

arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
arm64-ios, arm64_sim-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32

예를 들어 플랫폼별 라이브러리는 다음 위치에 넣습니다.

Expand Down
2 changes: 1 addition & 1 deletion docs/ko/manuals/extensions-ext-manifests.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ platforms:
libs: ["z", "c++", "sqlite3"]
defines: ["MY_DEFINE"]

armv7-ios:
arm64_sim-ios:
context:
frameworks: ["CoreGraphics", "CFNetwork", "GLKit", "CoreMotion", "MessageUI", "MediaPlayer", "StoreKit", "MobileCoreServices", "AdSupport", "AudioToolbox", "AVFoundation", "CoreGraphics", "CoreMedia", "CoreMotion", "CoreTelephony", "CoreVideo", "Foundation", "GLKit", "JavaScriptCore", "MediaPlayer", "MessageUI", "MobileCoreServices", "OpenGLES", "SafariServices", "StoreKit", "SystemConfiguration", "UIKit", "WebKit"]
flags: ["-stdlib=libc++"]
Expand Down
4 changes: 2 additions & 2 deletions docs/ko/manuals/ios.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,10 +91,10 @@ code signing identity와 provisioning profile이 있으면 에디터에서 게

![Signing iOS bundle](images/ios/sign_bundle.png)

code signing identity를 선택하고 mobile provisioning 파일을 찾습니다. `arm64-ios` 디바이스 아키텍처와 필요한 경우 `x86_64-ios` simulator 아키텍처, 그리고 variant(Debug 또는 Release)를 선택합니다. 원한다면 `Sign application` 체크박스를 해제해 서명 프로세스를 건너뛰고 나중에 수동으로 서명할 수 있습니다.
code signing identity를 선택하고 mobile provisioning 파일을 찾은 뒤 variant(Debug 또는 Release)를 선택합니다. 원한다면 `Sign application` 체크박스를 해제해 서명 프로세스를 건너뛰고 나중에 수동으로 서명할 수 있습니다. 디바이스 번들 대신 iOS Simulator용 `arm64_sim-ios` 번들을 만들려면 `Simulator`를 체크합니다.

::: important
iOS simulator에서 게임을 테스트할 때는 `Sign application` 체크박스를 **반드시** 해제해야 합니다. 어플리케이션을 설치할 수는 있지만 부팅되지 않습니다.
Simulator 번들은 Apple Silicon Mac의 iOS Simulator에서만 실행됩니다. 항상 ad-hoc 서명되므로 `Simulator`를 체크하면 서명, 설치, 실행 옵션이 비활성화됩니다. 아래 설명대로 `xcrun simctl`로 번들을 설치하세요.
:::

*Create Bundle*을 누르면 컴퓨터에서 번들이 생성될 위치를 지정하라는 프롬프트가 표시됩니다.
Expand Down
2 changes: 1 addition & 1 deletion docs/ko/shared/platforms.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
지원되는 플랫폼은 `ios`, `android`, `osx`, `win32`, `linux`, `web`입니다.

지원되는 `arc-platform` 쌍은 `arm64-ios`, `x86_64-ios`, `armv7-android`, `arm64-android`, `x86_64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web`, `wasm_pthread-web`입니다.
지원되는 `arc-platform` 쌍은 `arm64-ios`, `arm64_sim-ios`, `armv7-android`, `arm64-android`, `x86_64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web`, `wasm_pthread-web`입니다.
4 changes: 2 additions & 2 deletions docs/pl/manuals/bob.md
Original file line number Diff line number Diff line change
Expand Up @@ -197,8 +197,8 @@ Dostępne platformy i architektury:
`arm64-linux`
: Linux ARM64 dla Raspberry Pi i urządzeń przenośnych opartych na systemie Linux.

`x86_64-ios`
: iOS na macOS 64-bit (symulator iOS)
`arm64_sim-ios`
: Symulator iOS na komputerach Mac z Apple Silicon. Pakiety dla symulatora są zawsze podpisywane ad-hoc, więc `--identity` i `--mobileprovisioning` są ignorowane.

`arm64-ios`
: iOS 64-bit. Domyślnie wartość argumentu `--architectures` to `arm64-ios`.
Expand Down
2 changes: 1 addition & 1 deletion docs/pl/manuals/extensions-best-practices.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ W niektórych miejscach architektura platformy jest używana jako nazwa folderu,

Aktualna lista to:

arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
arm64-ios, arm64_sim-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32

Na przykład biblioteki specyficzne dla platformy umieszczaj w:

Expand Down
2 changes: 1 addition & 1 deletion docs/pl/manuals/extensions-ext-manifests.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ platforms:
libs: ["z", "c++", "sqlite3"]
defines: ["MY_DEFINE"]

armv7-ios:
arm64_sim-ios:
context:
frameworks: ["CoreGraphics", "CFNetwork", "GLKit", "CoreMotion", "MessageUI", "MediaPlayer", "StoreKit", "MobileCoreServices", "AdSupport", "AudioToolbox", "AVFoundation", "CoreGraphics", "CoreMedia", "CoreMotion", "CoreTelephony", "CoreVideo", "Foundation", "GLKit", "JavaScriptCore", "MediaPlayer", "MessageUI", "MobileCoreServices", "OpenGLES", "SafariServices", "StoreKit", "SystemConfiguration", "UIKit", "WebKit"]
flags: ["-stdlib=libc++"]
Expand Down
4 changes: 2 additions & 2 deletions docs/pl/manuals/ios.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,10 +91,10 @@ Gdy masz tożsamość podpisywania kodu i profil provisioningowy, możesz utworz

![Podpisywanie pakietu iOS](images/ios/sign_bundle.png)

Wybierz tożsamość podpisywania kodu i wskaż plik profilu provisioningowego. Wybierz architekturę urządzenia `arm64-ios`, a w razie potrzeby również architekturę symulatora `x86_64-ios`, oraz wariant Debug lub Release. Opcjonalnie możesz odznaczyć pole wyboru `Sign application`, aby pominąć proces podpisywania i podpisać pakiet ręcznie później.
Wybierz tożsamość podpisywania kodu i wskaż plik profilu provisioningowego oraz wariant Debug lub Release. Opcjonalnie możesz odznaczyć pole wyboru `Sign application`, aby pominąć proces podpisywania i podpisać pakiet ręcznie później. Zaznacz `Simulator`, aby zamiast pakietu na urządzenie utworzyć pakiet `arm64_sim-ios` dla symulatora iOS.

::: important
Musisz **odznaczyć** pole `Sign application`, gdy testujesz grę na symulatorze iOS. Aplikację będzie można zainstalować, ale nie uruchomi się.
Pakiety dla symulatora działają wyłącznie w symulatorze iOS na komputerach Mac z Apple Silicon. Są zawsze podpisywane ad-hoc, więc po zaznaczeniu `Simulator` opcje podpisywania, instalacji i uruchamiania są wyłączone. Zainstaluj pakiet za pomocą `xcrun simctl`, jak opisano poniżej.
:::

Naciśnij *Create Bundle*, a potem zostaniesz poproszony o wskazanie miejsca na komputerze, w którym pakiet ma zostać utworzony.
Expand Down
2 changes: 1 addition & 1 deletion docs/pl/shared/platforms.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
Obsługiwane platformy to `ios`, `android`, `osx`, `win32`, `linux`, `web`.

Obsługiwane pary `arc-platform` to `arm64-ios`, `x86_64-ios`, `armv7-android`, `arm64-android`, `x86_64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web` oraz `wasm_pthread-web`.
Obsługiwane pary `arc-platform` to `arm64-ios`, `arm64_sim-ios`, `armv7-android`, `arm64-android`, `x86_64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web` oraz `wasm_pthread-web`.
4 changes: 2 additions & 2 deletions docs/pt/manuals/bob.md
Original file line number Diff line number Diff line change
Expand Up @@ -197,8 +197,8 @@ Plataformas e arquiteturas disponíveis:
`arm64-linux`
: Linux ARM64 para Raspberry Pi e dispositivos portáteis baseados em Linux.

`x86_64-ios`
: iOS macOS 64 bit (iOS Simulator)
`arm64_sim-ios`
: iOS Simulator em Macs com Apple Silicon. Bundles para o simulador são sempre assinados ad-hoc, portanto `--identity` e `--mobileprovisioning` são ignorados.

`arm64-ios`
: iOS 64 bit. Por padrão, o valor do argumento `--architectures` é `arm64-ios`.
Expand Down
2 changes: 1 addition & 1 deletion docs/pt/manuals/extensions-best-practices.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ Em certos lugares, a arquitetura da plataforma é usada como nome de pasta, para

A lista atual é:

arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
arm64-ios, arm64_sim-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32

Então, por exemplo, coloque bibliotecas específicas de plataforma em:

Expand Down
2 changes: 1 addition & 1 deletion docs/pt/manuals/extensions-ext-manifests.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ platforms:
libs: ["z", "c++", "sqlite3"]
defines: ["MY_DEFINE"]

armv7-ios:
arm64_sim-ios:
context:
frameworks: ["CoreGraphics", "CFNetwork", "GLKit", "CoreMotion", "MessageUI", "MediaPlayer", "StoreKit", "MobileCoreServices", "AdSupport", "AudioToolbox", "AVFoundation", "CoreGraphics", "CoreMedia", "CoreMotion", "CoreTelephony", "CoreVideo", "Foundation", "GLKit", "JavaScriptCore", "MediaPlayer", "MessageUI", "MobileCoreServices", "OpenGLES", "SafariServices", "StoreKit", "SystemConfiguration", "UIKit", "WebKit"]
flags: ["-stdlib=libc++"]
Expand Down
4 changes: 2 additions & 2 deletions docs/pt/manuals/ios.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,10 +91,10 @@ Quando você tiver a identidade de assinatura de código e o perfil de provision

![Signing iOS bundle](images/ios/sign_bundle.png)

Selecione sua identidade de assinatura de código e procure seu arquivo de provisionamento mobile. Selecione a arquitetura de dispositivo `arm64-ios` e, quando necessário, a arquitetura de simulador `x86_64-ios`, bem como a variante (Debug ou Release). Opcionalmente, você pode desmarcar a caixa de seleção `Sign application` para pular o processo de assinatura e assinar manualmente em uma etapa posterior.
Selecione sua identidade de assinatura de código e procure seu arquivo de provisionamento mobile, bem como a variante (Debug ou Release). Opcionalmente, você pode desmarcar a caixa de seleção `Sign application` para pular o processo de assinatura e assinar manualmente em uma etapa posterior. Marque `Simulator` para criar um bundle `arm64_sim-ios` para o iOS Simulator em vez de um bundle para dispositivo.

::: important
Você **deve** desmarcar a caixa de seleção `Sign application` ao testar seu jogo no simulador iOS. Você conseguirá instalar a aplicação, mas ela não iniciará.
Bundles para o simulador só rodam no iOS Simulator em Macs com Apple Silicon. Eles são sempre assinados ad-hoc, portanto as opções de assinatura, instalação e execução ficam desativadas quando `Simulator` está marcado. Instale o bundle com `xcrun simctl` como descrito abaixo.
:::

Pressione *Criar Pacote…* e então será solicitado que você especifique onde no seu computador o pacote será criado.
Expand Down
2 changes: 1 addition & 1 deletion docs/pt/shared/platforms.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
As plataformas suportadas são `ios`, `android`, `osx`, `win32`, `linux`, `web`.

Os pares `arc-platform` suportados são `arm64-ios`, `x86_64-ios`, `armv7-android`, `arm64-android`, `x86_64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web` e `wasm_pthread-web`.
Os pares `arc-platform` suportados são `arm64-ios`, `arm64_sim-ios`, `armv7-android`, `arm64-android`, `x86_64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web` e `wasm_pthread-web`.
4 changes: 2 additions & 2 deletions docs/ru/manuals/bob.md
Original file line number Diff line number Diff line change
Expand Up @@ -197,8 +197,8 @@ Available platforms and architectures:
`arm64-linux`
: Linux ARM64 для Raspberry Pi и портативных устройств на базе Linux.

`x86_64-ios`
: iOS macOS 64 бита (Эмулятор iOS)
`arm64_sim-ios`
: Симулятор iOS на Mac с Apple Silicon. Сборки для симулятора всегда подписываются ad-hoc, поэтому `--identity` и `--mobileprovisioning` игнорируются.

`arm64-ios`
: iOS 64 бита. По умолчанию значение аргумента `--architectures` - `arm64-ios`.
Expand Down
2 changes: 1 addition & 1 deletion docs/ru/manuals/extensions-best-practices.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ brief: В этом руководстве описаны лучшие метод

Текущий список:

arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
arm64-ios, arm64_sim-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32

Например, для платформоспецифичных библиотек:

Expand Down
2 changes: 1 addition & 1 deletion docs/ru/manuals/extensions-ext-manifests.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ platforms:
libs: ["z", "c++", "sqlite3"]
defines: ["MY_DEFINE"]

armv7-ios:
arm64_sim-ios:
context:
frameworks: ["CoreGraphics", "CFNetwork", "GLKit", "CoreMotion", "MessageUI", "MediaPlayer", "StoreKit", "MobileCoreServices", "AdSupport", "AudioToolbox", "AVFoundation", "CoreGraphics", "CoreMedia", "CoreMotion", "CoreTelephony", "CoreVideo", "Foundation", "GLKit", "JavaScriptCore", "MediaPlayer", "MessageUI", "MobileCoreServices", "OpenGLES", "SafariServices", "StoreKit", "SystemConfiguration", "UIKit", "WebKit"]
flags: ["-stdlib=libc++"]
Expand Down
Loading
Loading