Hot answers tagged

2

The solution to my problem was that the wasm file had to exactly match the name of the contract in the attributes of the contract class. So as my file was called mycontract.wasm, I had to have the following in my contract class: class [[eosio::contract("mycontract")]] token : public contract { // the name of the class must be mycontract ... }; After this, ...


1

I wasn't getting an abi file, but it was compiling fine. I finally noticed that I had the file named: widgets.cpp but the class was widget. Watch out for missing "S"s. Ran again and the abi file appeared.


1

Here is an excellent example of how to use binary extensions: https://github.com/EOSIO/eosio.cdt/blob/ab8002109adc4f39d17c7ac38c4d8582af74190a/docs/guides/binary-extension.md I will post the full text here for the case that the link gets taken down, and also it helps with SEO: eosio::binary_extension Let's fully explain what the eosio::...


1

It says there is (likely) no file named hello.cpp in your /home/corey/eos directory. Check the previous steps in the tutorial. Find the step which was supposed to put this file there. Find out what happened instead.


Only top voted, non community-wiki answers of a minimum length are eligible