Eos: fatal error: 'eosiolib/eosio.hpp' file not found

[MessyComposer]

I've been trying to get the development environment working for the past three days but keep getting this error when generating wast and abi for my code using eosiocpp
fatal error: 'eosiolib/eosio.hpp' file not found #include <eosiolib/eosio.hpp>

I've tried all the solutions I could find, including modifying eosiocpp, sudo make install, etc.
I have also tried using master branch, v1.0.5, v1.0.9 and v1.1.0

I'm completely stuck, what to do now?

[andriantolie]

Try v1.1.0, build it and install it (./eosio_build.sh && cd build && sudo make install). You will see that your eosiocpp will be installed inside /usr/local/eosio/bin and your eosiolib will be installed inside /usr/local/eosio/include. This way, if you are compiling using /usr/local/eosio/bin/eosiocpp, your eosiocpp should be able to detect files inside /usr/local/eosio/include as it is already added to your include path by eosiocpp. Make sure you revert all the change you have made to eosiocpp previously to prevent unintended side effect. Let me know if you still encounter the problem.

[MessyComposer]

Same thing happens, don't just frantically close the issue.

I can get it kind of working by modifying eosiocpp but then I get errors about missing boost library files.

EOS 1.1.0 is scuffed.

[andriantolie]

Apologize for being too rush. I oversimplified the problem and thought it was the same case as previous issues. Indeed, I also encountered the same problem before and the above solution solves my problem.

That's quite strange since I don't think eosiocpp boost include directory got changed recently. Can you share the error message that you saw and the modification you did?

[williamleecn]

must build and make install the eos

[cppfuns]

https://www.bcskill.com/index.php/archives/304.html

[MessyComposer]

I managed to get it working by making a fresh install of ubuntu.

After close inspection, it seems that build script dependency installation didn't take into account which version of boost I had, and skipped it, leading into missing files.

eosiocpp still doesn't work as expected, but with minor path tinkering I got it working.