You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 25, 2023. It is now read-only.
Hikari would not even compile if you are targeting the upcoming LLVM 15, which should be the LLVM version for Swift 5.8 or Swift 5.9, as well as corresponding NDK.
This only applies to OSS Hikari, Private version works on NPM since day one.
PrivateVersion is not for sale, and has never been sold, for now
Hints
Opaque Pointers
In LLVM 15+, you should turn off opaque pointer with -mllvm -opaque-pointers=false -Xclang -no-opaque-pointers, or patch default values in Clang/LLVM.
The places to patch are: Clang LLVM
Since D123609 or 2978d0, LLVM has fully removed LegacyPassManager support in Clang.
Your choice would be reimplement the passes in NewPM as well as a fully new Obfuscation.cpp that does its scheduling in the NewPM way. That being said, as a toy project, Hikari had way too much design issues so it's probably not worthwhile.
The text was updated successfully, but these errors were encountered:
Hikari would not even compile if you are targeting the upcoming
LLVM 15
, which should be the LLVM version forSwift 5.8
orSwift 5.9
, as well as corresponding NDK.Previous discussion from 2020
RIP
P.S. :
Hints
Opaque Pointers
In LLVM 15+, you should turn off opaque pointer with
-mllvm -opaque-pointers=false -Xclang -no-opaque-pointers
, or patch default values in Clang/LLVM.The places to patch are:
Clang
LLVM
Reference : OpaquePointers
New Pass Manager
Since D123609 or 2978d0, LLVM has fully removed LegacyPassManager support in Clang.
Your choice would be reimplement the passes in NewPM as well as a fully new
Obfuscation.cpp
that does its scheduling in the NewPM way. That being said, as a toy project, Hikari had way too much design issues so it's probably not worthwhile.The text was updated successfully, but these errors were encountered: