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
Is your feature request related to a problem? Please describe.
I am unable to run kptools-linux in distros that don't use glibc (example: alpine linux).
Also unable to run kptools-android in recovery mode.
Describe the solution you'd like
Statically compiling kptools-linux will allow it to run on any x86_64 distro, regardless if they are using glibc or not.
And statically compiling kptools-android will allow it to run in recovery mode, assuming:
flashing apatch.zip fails, and user has to manual patch
user extracting stock boot.img from device using recovery mode
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Current versions of kptools-android and kptools-linux are dynamically compiled, meaning they need the system's libraries to function.
Static compile will solve this issue by bundling all dependencies inside the binary.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I am unable to run kptools-linux in distros that don't use glibc (example: alpine linux).
Also unable to run kptools-android in recovery mode.
Describe the solution you'd like
Statically compiling kptools-linux will allow it to run on any x86_64 distro, regardless if they are using glibc or not.
And statically compiling kptools-android will allow it to run in recovery mode, assuming:
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Current versions of kptools-android and kptools-linux are dynamically compiled, meaning they need the system's libraries to function.
Static compile will solve this issue by bundling all dependencies inside the binary.
The text was updated successfully, but these errors were encountered: