build package for Opkg to install tunneler on OpenWRT

[qrkourier]

Idealized user experience for OpenWRT:

opkg install ziti-edge-tunnel

As a first step in that direction we could provide a build script that generates an IPK file for the target architecture, extending the idea of Nic's builder script. In this scenario the user needs to cross-compile the IPK with our script and copy it to their device before running opkg install /tmp/ziti-edge-tunnel.ipk.

Later, if it's possible to identify a few high-value build artifacts, we should consider vending those builds to OpenWRT so users can have the idealized experience of automatically downloading the IPK with one install command.

[sabedevops]

I believe @NicFragale is currently vendoring builds per the following table:

Target	Subtarget	OpenWRT Package Architecture
ath79	generic	mips_24kc
ipq806x	generic	arm_cortex-a15_neon-vfpv4
x86	64	x86_64

Some work here should be prioritized in the near future to import or sanction the OpenWRT builds. These unofficial builds are actually vendored in a production capacity. Additionally, we don't have a means to test whether new code contributions impact the ability to build for OpenWRT targets. This creates friction, is perilous for the production users, and slows down the development cycle.

It may be in the best interest of the project to offer a native build pipeline for this purpose. It seems prudent to at least have a pipeline to compile a binary for one of the above "triplets" (preferably for something foreign like MIPS?) in order to have some guarantee that new code changes won't break the ability to build for OpenWRT.

I agree with @qrkourier in taking it a step further and supplying opkg repositories. Artifactory already supports this package repository type.