Add mention for Swift projects via -load-pass-plugin option
#13
Conversation
omvll/introduction/_index.md
Outdated
|
|
||
| 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 |
There was a problem hiding this comment.
Sounds a bit convoluted to me. What about
O-MVLL is an LLVM-based obfuscator that leverages the new LLVM pass manager. It integrates via -fpass-plugin in Clang or -load-pass-plugin in the Swift compiler (starting with Xcode 26) to perform native code obfuscation.
There was a problem hiding this comment.
Here I'd add a note saying something like "throughout this docu, whenever we refer to Clang we mean the host compiler being used, which can be Clang or the Swift compiler"
| 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: |
There was a problem hiding this comment.
We don't need to repeat the Xcode26 minimum version again:
simply as using the compiler flag -fpass-plugin= (-load-pass-plugin= in Swift), as follows:
There was a problem hiding this comment.
Much better, updated, thanks!
| ```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: |
There was a problem hiding this comment.
# Create/edit './omvll_config.py' to configure the obfuscator and run:
# 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 |
There was a problem hiding this comment.
no need for curly braces around dylib
| 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 |
There was a problem hiding this comment.
I'd add the note I mentioned above ("throughout this docu, whenever we refer to Clang we mean the host compiler being used, which can be Clang or the Swift compiler") and undo this change
There was a problem hiding this comment.
Makes sense, undone here, thanks.
3 participants
Mention new Swift compiler
-load-pass-pluginoption for Swift projects.