Moving build dependencies out of trunk/master.

[NaN]

We have got vdrift\tools\win and vdrift\tools\osx folders containing VDrift build dependencies for Windows and Mac OS.

These files(headers and binaries) do not belong to the code base and I'd prefer them to be moved into dependency packages(vdrift-win32-dependencies.zip, ...)to be hosted on sourceforge for instance.

Issue: https://github.com/VDrift/vdrift/issues/24

Any opinions?

[joevenzon]

It'd be nice to get those out of our git repo, but it'd also be nice to keep the compilation instructions simple. Maybe we could use a git feature like this:
http://stackoverflow.com/questions/57123...nal-in-git
to automatically pull them in from a separate repo?

[NaN]

I've uploaded win32 dependencies to sourceforge:
http://sourceforge.net/projects/vdrift/f...endencies/

The instructions are in the included readme.txt.

The user has to extract them into vdrift directory and build vdrift(only mingw/codeblocks atm, scons support is wip).