NDK Specific

Can’t load
error: unable to load plugin '<path>/':
'Could not load library '<path>/': cannot open shared object file:
No such file or directory'
Set export LD_LIBRARY_PATH to the NDK directory which contains these libraries: <ndk>/toolchains/llvm/prebuilt/linux-x86_64/lib64


ModuleNotFoundError: No module named ’encodings'
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
  Python runtime state: core initialized
  ModuleNotFoundError: No module named 'encodings'

  Current thread 0x00007fd10ad91040 (most recent call first):
    <no Python frame>
  ninja: build stopped: subcommand failed.
Set the environment variable OMVLL_PYTHONPATH to the Python STL as mentioned in Getting Started. You can also set the yaml key: OMVLL_PYTHONPATH.
ModuleNotFoundError: No module named ‘omvll_config’:
error: ModuleNotFoundError: No module named 'omvll_config'
  ninja: build stopped: subcommand failed.
You should set the environment variable OMVLL_CONFIG with the path to the O-MVLL Python configuration file. Alternatively, you can set this value in the yaml file.
The C++ compiler is not able to compile a simple test program:
CMake Error at /opt/android/sdk/cmake/3.22.1/share/cmake-3.22/Modules/CMakeTestCXXCompiler.cmake:62 (message):
The C++ compiler


is not able to compile a simple test program.

It fails with the following output:
This error is likely due to an error in the O-MVLL configuration file. You could try to set -DCMAKE_CXX_COMPILER_WORKS=1 and see if the error message is more meaningful.

How to open a GitHub issue

O-MVLL might crash while trying to obfuscate code that is not well supported by the passes,
or it could also introduce an inconsistency in the obfuscated code.

If you think that you identified a bug, please, feel free to
open a GitHub issue with the following information:


Description of the bug or the problem.

How to reproduce the issue

Please describe and attach all the necessary
materials (backtrace, binary, snippet, code) to reproduce the issue.

O-MVLL Python Configuration

You can put the O-MVLL configuration that triggers the bug (if relevant)

  • Target: Android/iOS?
  • O-MVLL Version: strings|grep "OMVLL Version:"
  • Compilation of O-MVLL: CI/By your own

If you compiled O-MVLL by yourself, please attach the library to the issue.

Additional context

Any other information that could help to address the issue?