EOSIO/eosio.contracts

Modify `build.sh` once consistencies of installation paths have been established.

johndebord opened this issue · 1 comments

When building the contracts, build.sh defaults to look for eosio in directory $HOME/eosio/X.Y, and looks for eosio.cdt in directory /usr/local/include/eosio.cdt.

screenshot

This can be especially confusing for on-boarding new developers who expect consistency.

Fix once eosio.cdt Issue #753 has been addressed.

deckb commented

Is this still an issue?