This repository has been archived by the owner on May 26, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 310
Add support for standard-json. #200
Comments
Yes please +1 |
Thanks @MicahZoltu Will consider this |
@luongnt95 looks like support was added here--does it work? :) |
@beaugunderson it's not fully supported. Could you help me test this feature? Just report any problems you have with this feature. Thanks |
Below is a standard JSON output file for solidity, trying it with:
It'd be simplest if we could use the solidity json output as then we'd never run into path or build issues w/ oyente. From above, perhaps it takes the solidity json input instead? I tried that and got the same error though |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In a complex project like Augur, the contracts don't compile by just passing them to
solc
because the system is made up of dozens of contracts that have intertwining references and a non-trivial build system. "Standard JSON" seems to be the recommended mechanism for defining complex builds for solc, so it would be nice if Oyente supported building from a "Standard JSON" file as well so large projects can leverage Oyente (arguably, large projects need Oyente more than small projects).The text was updated successfully, but these errors were encountered: