Building EOS

Words
213
Reading
1 min
Listen
Play
9y

Screen Shot 2017-05-30 at 1.04.08 AM.png
Yes it's true, the EOS code is available for all to clone/fork.

Here's a couple of quick notes on things I stumbled getting this first round to build. Note, I am assuming you have a basic understanding of how to use git, cmake, etc.

  1. Remember to fetch submodules, this is your 1-2 punch before doing anything else :
    git clone https://github.com/EOSIO/eos.git
    git submodule update --init --recursive

  2. I am using a mac to build, so initially I tried cmake -G Xcode but ran into too many issues so I switched to cmake -G "Unix Makefiles" in a separate workspace.

  3. This could be Xcode related but I couldn't use OpenSSL 1.1.0f, I had to revert to OpenSSL 1.0.2.

  4. there are several directories currently flagged as [incomplete][no build]. These may
    contain non-compiling code. Use "make -k" or whatever "keep compiling after an error" option is available for your build environment.

  5. the latest code is in the "refactor" branch.

  6. Nothing runs yet, so refrain from pelting dantheman@dantheman and modprobe@modprobe with complaints about non-running code. Be happy dantheman@dantheman elected to pull back the curtain so early on to allow the world to watch and contribute as EOS is made.

Finally, a nod to modprobe@modprobe for creating the #qwoa "quick word of advice" tag. This may not be as life changing as debugging your space with a flashlight, but it is a qwoa!

Cheers!
-Phil

Building EOS | Ecency