Added script to build portable binaries

[ghost]

#65

[osa1]

We need --target=x86_64-unknown-linux-musl here, otherwise it won't be a statically linked binary.

[osa1]

This works but depends on where I'm running it from (e.g. running it from top-level doesn't work, I have to cd into pkg/bin).

Also, we should pass a --target=... parameter to cargo build.

I wonder if there's an easy-to-use build system for this kind of stuff. It'd be great if we could cache OpenSSL builds, check for clang etc. availability easily etc.

[ghost]

I accidentally stashed a commit, before fetching and rebasing, so I had to do a merge to get my stashed commit to push. Github is now not showing one of your comments, but I fixed the cd command (this is such a learning process...).

Earlier, I couldn't get it working with --target=x86_64-unknown-linux-musl and then it started working inexplicably. I should have double checked, it seems that I somehow removed that part of the line with a git operation or something. If I try to run it with --target=x86_64-unknown-linux-musl, I get the following errors:

   Compiling lazycell v0.5.1
   Compiling foreign-types-shared v0.1.1
error[E0463]: can't find crate for `core`
  |
  = note: the `x86_64-unknown-linux-musl` target may not be installed

error: aborting due to previous error

error: Could not compile `foreign-types-shared`.
warning: build failed, waiting for other jobs to finish...
error[E0463]: can't find crate for `std`
  |
  = note: the `x86_64-unknown-linux-musl` target may not be installed

error: aborting due to previous error

error: Could not compile `lazycell`.

To learn more, run the command again with --verbose.

I don't know how to cross-compile with Rust from Arch Linux. I will look into it, but the command does work for you and @seathlin , right?

This works but depends on where I'm running it from (e.g. running it from top-level doesn't work, I have to cd into pkg/bin).

Also, we should pass a --target=... parameter to cargo build.

I wonder if there's an easy-to-use build system for this kind of stuff. It'd be great if we could cache OpenSSL builds, check for clang etc. availability easily etc.

Does this need to work for more than one developer(you, when you make the binary releases)?

I'm not familiar with build systems. The features you mentioned shouldn't be hard to write in bash but there may be a better way to do this.