Erik Wierich
Erik Wierich
Looks simple enough. Building with cmake and then packaging up the result certainly makes things easier for you. You might want to take some inspiration from the compiler flags that...
The error is in the log: ``` Please install GNU autoconf-archive. ``` You will need that to run the configuration. Probably `opkg install autoconf-archive` should get you covered. Please note...
> In theory you should be able to `nix build .#appimage` on aarch64 and get a "static" binary (technically an appimage): https://github.com/iovisor/bpftrace/blob/master/docs/nix.md#build-bpftrace-as-a-statically-linked-binary > > But I don't have an aarch64...
This does not seem to consider release APK builds
Here is my approach regarding the changed .apk filepath: https://github.com/benlau/qtci/pull/28
> caching is useful, but not trivial to implement: I should design it with a grain of salt so concurrent modifications are handled well, without losing data (duplication, merging?). Sure....
No worries :). No need to give me any estimations ;)
> autoreconf: configure.ac: not using Libtool Could you check whether you have `libtool` installed?
Ah, sorry. I missed that this is for staging only... So maybe my comments were overly strict...
> This includes two interfaces: and . This reads like there should be the interfaces spelled out? :)