Those dependencies are used for bittorent and metalink.
For now, we don't support those features (we should in the future).
However, it seems that if development package are installed on the system,
libaria will try to link with libsqlite3 and libxml3 anyway.
We have to investigate this, but it breaks static build of kiwix-tools.
As we are not using those feature for now, let's just explicitly
compile libaria2 without sqlite3 and libxml2.
libaria2 use xz to configure its source.
If we compile the xz tool, libaria2 will use the compiled binary.
However, on cross compilation, xz will be compiled for the target platform
and run on the host platform. And so, it will fails.
As we do not use those tools at all, lets not compile them.
Make kiwix-build installable using pip.
Module is now called `kiwixbuild` because `kiwix-build` is not a valid
python identifier.
Also split toolchains in separated directory.
Matthieu Gautier
mhutti1