1. Update `ANDROID_SDK_ROOT` to `ANDROID_HOME`. The former variable is
deprecated. (see https://developer.android.com/tools/variables#envar)
2. Remove `ANDROID_NDK_HOME` environment variable. This should allow the
build script to work out of the box for more folks.
3. Check that Java is on the `PATH` as opposed to just installing it.
`asdf` and other runtime management tools are pretty popular, and all
we care about is that the Java version is accessible.
4. Remove calls to `sudo`. Check to see if CocoaPods exists, if it
doesn't install it using Homebrew which doesn't require `sudo`.
This changes the Windows instructions to specify
capnproto-c++-win32-1.0.1. Previously, users may have been trying to
use Veilid with 0.10.4, especially in the common case of using the
winget package manager.
Also, the suggested Protocol Buffers version is updated to 24.3, and a
note is added about rustup behavior on Windows machines that have
never previously been used for development.
This provides one method for getting the Veilid source code on
Windows, and launching a node. It is mainly intended to confirm that
https://gitlab.com/veilid/cursive-flexi-logger-view/-/merge_requests/1
addresses a build problem.
It provides a "development" environment in the sense that one could,
in theory, edit the .rs files in Notepad. It does not discuss whether
there is any value in seeing the debug messages in a cmd.exe window,
and does not document other deployment options that may be possible,
such as a Windows service. The information could be revised later to
be more maintainable, e.g., by avoiding the hardcoded protoc and capnp
version numbers and removing the x86_64 assumption.
Added and modified documentation for the contribution process.
Added the code of conduct file.
Modified bump version's conf to auto create tags and commits.
