Hot answers tagged

1

You can pass variant_object to initialize the other variant_object. For example, auto fa_obj = mvo()("first", "apk")("second", 1); REQUIRE_MATCHING_OBJECT(notary, mvo()("account", "ins")("first_approve", fa_obj)...


1

Your CMakeLists file in the base folder should not be changed. But rather in the src folder CMakeList you should add the following line: target_include_directories( mycontract PUBLIC "$ENV{BOOST_DIR}/include" ) Where BOOST_DIR is an environmental variable pointing to your boost folder. On my computer it is: /home/eosio/1.8/src/boost_1_70_0


1

./eosio_build.sh # no sudo for build sudo ./eosio_install.sh I had similar problems with WSL 16.04. Using the 18.04 image brought up better results. Note that I finally did not manage to stabilize the eos-tests on WSL, and switched to a VirtualBox 18.04. WSL is currently unsupported by the team.


1

Used Thomas5577's instructions but created an opt directory in /usr/ and then a boost directory within opt. Then I installed the boost library, but I changed the bootstrap setup command to ./bootstrap.sh --prefix=/usr/opt/boost, and the eosio build worked.


1

You will probably be better off installing boot manually. That is what I had to do https://www.boost.org/: Install the required packages sudo apt-get update sudo apt-get install build-essential g++ python-dev autotools-dev libicu-dev build-essential libbz2-dev Install the Boost libraries wget -O boost.tar.gz https://dl.bintray.com/boostorg/release/1.67....


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