DUNES support: Added compiler option to setup script

[n13]

setup compiler local and setup compiler docker

The docker option copies CMakeLists files for DUNEs and the dune tool and Antelope Leap 4.x

Many more utility scripts added - need to automate all of this, so we can just have a single command that

• pulls repo from GH
• configures for prod / compiler docker setup.sh prod setup.sh compiler docker
• installs ninja-build if needed
• runs cmake with ninja parameters: run_make.sh cmake -S . -B "$BUILD_DIR" -G Ninja
• runs ninja to build the wasm
• installs wasm-opt if needed
• runs wasm-opt on dao.wasm
• has a simple deploy script to deploy on EOS mainnet (and others) - set_contract.sh

[n13]

I think one problem with this simple approach is now any changes to the CmakeLists need to be reflected in all templates.

[Gerard097]

@n13 I downloaded DUNES on my machine and tested it, everything seems to be working fine. Can you please just check why the build action is failing? Probably missing a ./setup because I see that default CMakeList is for DUNES but the github action works with regular flow (cdt 1.8)

[n13]

Yeah for sure I don't even know where to fix the GH build...

On Aug 18, 2023, at 00:45, Gerardo Hernandez @.***> wrote:

@n13 https://github.com/n13 I downloaded DUNES on my machine and tested it, everything seems to be working fine. Can you please just check why the build action is failing? Probably missing a ./setup because I see that default CMakeList is for DUNES but the github action works with regular flow (cdt 1.8)

— Reply to this email directly, view it on GitHub https://github.com/hypha-dao/dao-contracts/pull/355#issuecomment-1682710123, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAP7BHACDZ6WPEPNE25BO3XVZKCNANCNFSM6AAAAAA3C45EZA. You are receiving this because you were mentioned.

[n13]

Closing

[n13]

Not using DUNES