1. Sometimes, it is necessary to run multiple parallel CI jobs on the same
physical machine w/o any virtualization or containerization (a good
example of that is building an iOS app). To work properly in that
environment, realm should download a temp file to it's own unique temp
folder to avoid clashes (that are actually fail with `symlink` syscall
failing with `EEXISTS`).
2. To avoid an ever-growing temp folder, a new environment variable was
introduced, that you can set to be inside a job's folder. That way, CI
will be responsible for cleaning up after itself and keeping only the
necessary amount of files.
Theoretically, all of that can be solved by overriding `TMP` env
variable but in practice in many-many environments it breaks the other
part of toolchain (even Xcode builds themselves sometimes).
The CMake packaging added shared libraries to the node release package, but the
build system isn't set up to work with them so just go back to using the static
libraries.
* Remove the windows install check
* Node.js Win32 support
* Bring back the `REALM_HAVE_CONFIG` definition
* Download core for Windows when building
* Implement cross-platform node platform.cpp with libuv
* wip
* Make jasmine run quicker
https://github.com/jasmine/jasmine/issues/1204
* Wait for worker process to close in AsyncTests
* Cross-platform paths in tests
* Normalize path separator for forward slash on Windows
* MSVC exception voodoo
* cross-platform uv_cwd
* fix linux build
* make the prepublish script cross-platform
* Disable encryption tests on windows
* ignore vendor/realm-node
* jenkinsfile work
* Only run the prepublish script for publish and pack
* Jenkinsfile work
* Include gyp files in package
* rewrite default_realm_file_directory()
* fix React Native Android build
* delete all realm artifacts in remove_realm_files_from_directory
* bring back build environment variables
* node-pre-gyp windows
* Update CHANGELOG.md
Igor Mandrigin
Kenneth Geisshirt
Emanuele Zattin
blagoev
Thomas Goyne
rh389
Yavor Georgiev
Yavor Georgiev