[PR #3285] [MERGED] Build and test hickory-resolver for android #3710

New issue

Closed

opened 2026-03-16 11:58:35 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 11:58:35 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hickory-dns/hickory-dns/pull/3285
Author: @LAGonauta
Created: 9/29/2025
Status: ✅ Merged
Merged: 10/14/2025
Merged by: @djc

Base: main ← Head: android_dns_servers_with_tests_dev

📝 Commits (1)

7cbfbc4 Build and test hickory-resolver for android

📊 Changes

2 files changed (+40 additions, -0 deletions)

View changed files

📝 .github/workflows/test.yml (+28 -0)
📝 justfile (+12 -0)

📄 Description

This is a PR to add support for building and testing the hickory-resolver for the Android targets.

This currently call cross directly but I get the sense that I should create a just command instead. Is me assessment correct?
While this won't test the resolver itself (there is no NDK context in a basic test), I can know nothing broke.

I can try to get it to build a proper Android app and test in an emulator if desired.

Thanks!

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/hickory-dns/hickory-dns/pull/3285 **Author:** [@LAGonauta](https://github.com/LAGonauta) **Created:** 9/29/2025 **Status:** ✅ Merged **Merged:** 10/14/2025 **Merged by:** [@djc](https://github.com/djc) **Base:** `main` ← **Head:** `android_dns_servers_with_tests_dev` --- ### 📝 Commits (1) - [`7cbfbc4`](https://github.com/hickory-dns/hickory-dns/commit/7cbfbc4ac4a4452c90ba7d6ae8008a4734e2bc04) Build and test hickory-resolver for android ### 📊 Changes **2 files changed** (+40 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/test.yml` (+28 -0) 📝 `justfile` (+12 -0) </details> ### 📄 Description This is a PR to add support for building and testing the hickory-resolver for the Android targets. This currently call `cross` directly but I get the sense that I should create a `just` command instead. Is me assessment correct? While this won't test the resolver itself (there is no NDK context in a basic test), I can know nothing broke. I can try to get it to build a proper Android app and test in an emulator if desired. Thanks! --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>