已安装Linux虚拟机，Windows下打包Kivy应用为APK的后续步骤

Hey there! Let’s take this one step at a time—since you’re new to this, I’ll keep things straightforward and skip the fancy jargon.

You’re on the right track! Here’s what you’ll need to get sorted:

• Python: Most Linux distros come with Python 3 pre-installed, but double-check it’s version 3.8 or newer (Kivy works best with recent releases). Verify with python3 --version in the terminal. If you need to update, use your distro’s package manager—for Ubuntu-based systems, run sudo apt update && sudo apt install python3.
• Kivy: Install it via pip with pip3 install kivy. Test if it works by running python3 -c "import kivy; kivy.require('2.0.0')"—no errors means you’re good to go.
• PyCharm (Optional but Helpful): If you prefer a GUI editor, installing PyCharm Community Edition will make editing your code easier. You can download it directly or use sudo snap install pycharm-community (if your distro supports snaps). That said, you could also use VS Code or even a simple terminal editor like Nano—whatever feels most comfortable for you.
• Transfer Your App Files: Absolutely, you need to get your Windows project into the VM. The easiest ways are:
  • Use your VM’s shared folder feature (VirtualBox and VMware both have this—enable it in VM settings, and your Windows folder will show up inside Linux).
  • Zip your project on Windows, transfer it via USB (if your VM has USB access), then unzip it in Linux with unzip your-project.zip.

Kivy’s official go-to tool for building APKs is Buildozer—it handles all the messy work like downloading the Android SDK, NDK, and compiling your app into an installable APK. Here’s how to set it up and use it:

Step 1: Install Buildozer Dependencies #

First, install all the system packages Buildozer needs. For Ubuntu/Debian-based distros, run these commands in the terminal:

sudo apt-get update
sudo apt-get install -y git zip unzip openjdk-17-jdk python3-pip autoconf libtool pkg-config zlib1g-dev libncurses5-dev libncursesw5-dev libtinfo5 cmake libffi-dev libssl-dev

Step 2: Install Buildozer #

Once dependencies are done, install Buildozer via pip:

pip3 install --user buildozer

Add Buildozer to your system PATH so you can run it from any folder:

echo 'export PATH=$PATH:~/.local/bin' >> ~/.bashrc
source ~/.bashrc

Step 3: Prepare Your App for Building #

1. Navigate to your project folder in the terminal using cd path/to/your/project.
2. Run buildozer init—this creates a buildozer.spec file, which controls every aspect of how your APK is built.

Step 4: Configure the Buildozer Spec File #

Open the buildozer.spec file in your editor and tweak these critical settings:

• title: The name of your app (e.g., "My First Kivy App").
• package.name: A unique identifier for your app (use reverse domain notation, like com.auggie.myapp—no spaces or special characters allowed).
• package.domain: Your "domain" (e.g., org.auggie—it can be anything if you don’t have a real domain).
• source.dir: Make sure this points to the folder with your main Kivy file (usually main.py—the default . works if your main file is in the project root).
• requirements: Add any dependencies your app needs. The default includes kivy, but if you use other libraries (like requests), add them here (e.g., requirements = python3,kivy==2.2.1,requests).

Step 5: Build the APK #

Go back to the terminal in your project folder and run:

buildozer android debug deploy run

• First run note: This will download a ton of large files (Android SDK, NDK, etc.)—it can take 30+ minutes depending on your internet speed. Don’t panic if it seems stuck; it’s just fetching what it needs.
• If it succeeds: Your APK will be in the bin folder of your project (look for something like MyFirstKivyApp-0.1-debug.apk).
• If it fails: Read the error message in the terminal—most issues are missing dependencies or typos in the buildozer.spec file. Google the error, and you’ll almost always find a fix (Stack Overflow is full of solutions for common Buildozer headaches!).

• Give your VM at least 4GB of RAM (preferably 8GB)—building APKs is resource-heavy, and a slow VM will make this process way more frustrating.
• If you get a "permission denied" error, add sudo to the front of the command (but be careful with sudo—only use it when necessary).
• Test your app on Linux first before building the APK! Run python3 main.py to make sure it works without errors—fixing bugs in Linux is way easier than debugging a broken APK.

内容的提问来源于stack exchange，提问作者Auggie