From 48629d0bd51142514dff7c2da5b345582b38328e Mon Sep 17 00:00:00 2001 From: Anthony Shoumikhin Date: Wed, 30 Apr 2025 14:09:30 -0700 Subject: [PATCH] Update using-executorch-ios.md --- docs/source/using-executorch-ios.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/using-executorch-ios.md b/docs/source/using-executorch-ios.md index ee961a833b9..4cec8529c4f 100644 --- a/docs/source/using-executorch-ios.md +++ b/docs/source/using-executorch-ios.md @@ -143,7 +143,7 @@ Copy them to your project and link them against your targets. ## Linkage -ExecuTorch initializes its backends and kernels (operators) during app startup by registering them in a static dictionary. If you encounter errors like "unregistered kernel" or "unregistered backend" at runtime, you may need to explicitly force-load certain components. Use the `-all_load` or `-force_load` linker flags in your Xcode build configuration to ensure components are registered early. +ExecuTorch initializes its backends and kernels (operators) during app startup by registering them in a static dictionary. If you encounter errors like "unregistered kernel" or "unregistered backend" at runtime, you may need to explicitly force-load certain components. Use the `-all_load` or `-force_load` linker flags in your Xcode build configuration to ensure components are registered early. Also, you may need to link against the C++ standard library, if not already, e.g. by adding the `-lc++` linker flag. Here's an example of a Xcode configuration file (`.xcconfig`):