Add mention for Swift projects via -load-pass-plugin option

omvll/_index.md

@@ -1,6 +1,6 @@
 +++
 title       = "O-MVLL Documentation"
-description = "O-MVLL is an LLVM-based obfuscator driven by a user-friendly Python API. It supports C/C++/Objective C."
+description = "O-MVLL is an LLVM-based obfuscator driven by a user-friendly Python API. It supports C/C++/Objective-C/Swift."
 name        = "O-MVLL"
 token       = "omvll"
 logo        = "static/img/omvll/logo.svg"

omvll/introduction/_index.md

@@ -15,7 +15,8 @@ Welcome to the O-MVLL documentation. This documentation is split into three sect
 3. The last section, [other topics]({{< ref "/omvll/other-topics" >}}), contains different information
    for those who are already familiar with the project.
 
-O-MVLL is an obfuscator based on LLVM that uses the new LLVM pass manager, `-fpass-plugin` to perform
+O-MVLL is an obfuscator based on LLVM that uses the new LLVM pass manager, and `-fpass-plugin` / `-load-pass-plugin`
+command options, respectively for Clang and Swift compilers (starting with Xcode 26), are leveraged to perform
 native code obfuscation. These obfuscation rules are driven by a Python API defined as follows:
 
 {{< alert type="danger" icon="fa-light fa-microchip">}}

omvll/introduction/getting-started/index.md

@@ -8,19 +8,24 @@ weight      = 10
 
 O-MVLL is a code obfuscator based on LLVM and designed to work with Android and iOS toolchains.
 It supports AArch64 and AArch32 as target architectures. Theoretically, it could be run as
-simply as using the compiler flag `-fpass-plugin=`, as follows:
+simply as using the Clang compiler flag `-fpass-plugin=`, or, starting with Xcode 26, on Swift
+projects via the Swift compiler's `-load-pass-plugin=` option, as follows:
 
 ```cpp
-# Create/edit './omvll_config.py' to configure the obfuscator and run:
+# Create/edit './omvll_config.py' to configure the obfuscator and
+# run Clang for C/C++/Objective-C projects:
 $ clang -fpass-plugin=OMVLL.{so, dylib} main.c -o main
+
+# For Swift projects:
+$ swiftc -load-pass-plugin=OMVLL.{dylib} main.swift -o main
 ```
 
 **Practically, there are additional configuration steps.**
 
-
 ### O-MVLL Configuration File
 
-Firstly, the O-MVLL Python configuration file is not always located next to the clang binary and we might want
+We refer to the Clang compiler (`-fpass-plugin` option) for the configuration, though the same applies to Swift.
+Firstly, the O-MVLL Python configuration file is not always located next to the compiler binary and we might want
 to change the name of the file.
 
 By default, O-MVLL tries to import `omvll_config.py` from **the current directory** in which **clang is called**.
@@ -522,14 +527,21 @@ Finally:
 
 ## iOS
 
-Using O-MVLL with Xcode is a bit easier than Android since we don't need to deal with different `libstdc++/libc++`.
-To enable O-MVLL, one needs to set the following in Xcode:
+Using O-MVLL with Xcode is a bit easier than Android since we don't need to deal
+with different `libstdc++/libc++`. When targeting C/C++/Objective-C projects, O-MVLL
+can be invoked by adding `-fpass-plugin=/path/to/omvll.dylib` under the following
+Xcode setting:
 
 `Build Settings > Apple Clang - Custom Compiler Flags > Other C/C++ Flags`
 
-and add `-fpass-plugin=<path>/omvll_xcode_15_2.dylib`. For versions targeting Xcode 14.5 and lower, the legacy pass manager
+For versions targeting Xcode 14.5 and lower, the legacy pass manager
 needs to be disabled as well via `-fno-legacy-pass-manager`.
 
+Likewise, when targeting Swift projects, O-MVLL can be enabled by specifying
+`-load-pass-plugin=/path/to/omvll.dylib` under the setting:
+
+`Build Settings > Swift Compiler - Custom Flags > Other Swift Flags`
+
 Finally, we can create an `omvll.yml` file next to the `*.xcodeproj` file which defines `OMVLL_PYTHONPATH` and `OMVLL_CONFIG`.
 
 Et voila :)