35 lines
2.6 KiB
Markdown
35 lines
2.6 KiB
Markdown
# AVA2 cross-platform client
|
|
|
|
Independent AVA2 port, Android arm64 first with macOS arm64 for development. The host, login/selection transport, supported loading/game socket bridge and Python 2 bootstrap are implemented. It is not yet a playable client.
|
|
|
|
```sh
|
|
git submodule update --init --recursive
|
|
cmake -S . -B build/dev -DCMAKE_BUILD_TYPE=Debug
|
|
cmake --build build/dev -j 8
|
|
ctest --test-dir build/dev --output-on-failure
|
|
python3 tools/verify_baseline.py
|
|
./build/dev/ava2_client --frames 60 --stdlib build/dev/python27.zip --python-root upstream/python-root
|
|
```
|
|
|
|
SDL3 development package is required for the window host. Use `-DAVA2_BUILD_HOST=OFF` for a build without a window, or `-DAVA2_EMBED_PYTHON=OFF` to disable Python. Python 3 only runs developer tools; gameplay retains Python 2.
|
|
|
|
`build/dev/ava2_login AUTH_HOST AUTH_PORT GAME_HOST GAME_PORT ACCOUNT` exercises the authentication transport and lists five character slots. Set `AVA2_PASSWORD` securely in the launching environment. No default server is configured. Real AVA2 server verification remains pending; use an isolated development server.
|
|
|
|
Android CMake builds require the NDK toolchain and an Android SDL3 SDK prefix. The `main` shared library compiles and links for arm64; APK packaging and device verification are pending. Original decoded assets remain in the sibling AVA2 directory; only immutable source/script references are copied into this repository.
|
|
|
|
See [port status](docs/PORT-PLAN.md), [login implementation and verification](docs/LOGIN-TRANSPORT.md), and [active login profile](docs/LOGIN-PROFILE.json).
|
|
|
|
Windows equivalence is tracked in [the parity audit](docs/WINDOWS-PARITY.md). Preview characters require `--preview-data`; game previews do not prove server gameplay. The static [placeholder inventory](docs/WINDOWS-PARITY-INVENTORY.json) is regenerated with `python3 tools/audit_windows_parity.py`.
|
|
|
|
The SDK is maintained in its own Git repository and pinned by the `sdk` submodule.
|
|
Clone with `git clone --recurse-submodules`, or run the initialization command above
|
|
before configuring. To develop against an existing SDK checkout, configure with
|
|
`-DAVA2_SDK_ROOT=/absolute/path/to/sdk`; normal builds use the pinned submodule.
|
|
|
|
Keep build outputs in `build/dev`, `build/release`, or another named directory
|
|
under `build/`, rather than configuring directly into `build/`. Put diagnostic
|
|
screenshots, logs, and one-off probes under `build/verification/`; permanent tests
|
|
belong in `tests/` and reusable tools in `tools/`. `dist/` contains generated
|
|
release packages. Loose game resource directories are used by development and
|
|
packaging and should not be treated as disposable caches.
|