aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/travis-emscripten/install_deps.sh
Commit message (Collapse)AuthorAgeFilesLines
* Use emscripten 1.37.21 and boost 1.67.0 on both travis and circle.Daniel Kirchner2018-11-211-5/+13
|
* Circle CI: Emscripten buildPaweł Bylica2017-09-151-4/+2
|
* Drop CryptoPP leftoversPaweł Bylica2016-11-081-1/+0
| | | | Especially, do not compile CryptoPP for Emscripten.
* Build jsoncpp from source using jsoncpp.cmake scriptPaweł Bylica2016-10-211-1/+0
|
* Make the Solidity repository standalone.Bob Summerwill2016-08-011-0/+44
This commit is the culmination of several months of work to decouple Solidity from the webthree-umbrella so that it can be developed in parallel with cpp-ethereum (the Ethereum C++ runtime) and so that even for the Solidity unit-tests there is no hard-dependency onto the C++ runtime. The Tests-over-IPC refactoring was a major step in the same process which was already committed. This commit contains the following changes: - A subset of the CMake functionality in webthree-helpers was extracted and tailored for Solidity into ./cmake. Further cleanup is certainly possible. - A subset of the libdevcore functionality in libweb3core was extracted and tailored for Solidity into ./libdevcore. Further cleanup is certainly possible - The gas price constants in EVMSchedule were orphaned into libevmasm. - Some other refactorings and cleanups were made to sever unnecessary EVM dependencies in the Solidity unit-tests. - TravisCI and Appveyor support was added, covering builds and running of the unit-tests (Linux and macOS only for now) - A bug-fix was made to get the Tests-over-IPC running on macOS. - There are still reliability issues in the unit-tests, which need immediate attention. The Travis build has been flipped to run the unit-tests 5 times, to try to flush these out. - The Emscripten automation which was previously in webthree-umbrella was merged into the TravisCI automation here. - The development ZIP deployment step has been commented out, but we will want to read that ONLY for release branch. Further iteration on these changes will definitely be needed, but I feel these have got to sufficient maturity than holding them back further isn't winning us anything. It is go time :-)