Issue #18: pin versions

We don't want our build process to rely on stability of remote masters. Hence, I've refactored the build scripts and pinned the latest stable version for each dependency.
Oh, right, that's run on the VM. All cool. :+1:


On Tue, Jun 24, 2014 at 6:45 PM, Kevin P. Dyer <notifications@github.com>
wrote:

> In vagrant/set_env.sh:
>
> > @@ -0,0 +1,31 @@
> > +export WORKING_DIR=/home/vagrant
> > +export BUILD_DIR=$WORKING_DIR/build
> > +export INSTALL_DIR=$WORKING_DIR/install
> > +export PATH=$INSTALL_DIR/bin:$BUILD_DIR/emscripten-fastcomp/Release/bin:$BUILD_DIR/emscripten:$PATH
> > +
> > +export GMP_VERSION=6.0.0a
> > +export HTTP_GMP=https://ftp.gnu.org/gnu/gmp/$GMP_VERSION.tar.bz2
> > +
> > +export LIBFTE_VERSION=0.1.1
> > +export GIT_LIBFTE=https://github.com/uProxy/libfte.git
> > +
> > +export UTRANSFORMERS_VERSION=0.1.3
> > +export GIT_OBFUSCATION=https://github.com/uProxy/uTransformers.git
> > +
> > +export CORES=`nproc`
>
> At the moment, this code is assumed to run in a 32-bit linux VM. There are
> a whole host of serious problems if this is run on OSX, or any 64-bit
> platform.
>
> I currently have this documented a bit in vagrant/README.md. However, it
> might be useful to explain this in greater details.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/uProxy/uTransformers/pull/22/files#r14160230>.
>



-- 
Lucas Dixon | Google Ideas