Commit Graph

7 Commits

Author SHA1 Message Date
Paweł Bylica
48e0e3b97f
Circle CI: Emscripten build 2017-09-15 16:06:05 +02:00
chriseth
b28aefe28c Use "nightly" version string for all CI built binaries. 2017-03-23 09:56:17 +01:00
chriseth
10c0953d0c Do not create prerelease build for release branch. 2016-09-17 18:37:42 +02:00
chriseth
29ecc6fe31 Remove leading zeroes in prerelease components. 2016-09-09 14:23:33 +02:00
chriseth
4588eda622 Store commit hash and handle prerelease vor all automation tools. 2016-08-26 10:14:44 +02:00
chriseth
168261254b Fix emscripten build. 2016-08-01 16:49:19 +02:00
Bob Summerwill
4ee2114127 Make the Solidity repository standalone.
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 :-)
2016-08-01 01:45:11 -07:00