NatPDeveloper
commented
2 years ago Hello @Dewald928, I'm glad you like it. With the fix below, it works fine for me.
You will either need to update zeus to the latest version (as I patched this recently) or you will need to update the compiler version for eth in ./atomictokenpeg/truffle-config.js to 0.8.13 and you can compile ETH specifically with zeus compile --phase eth.
Please share what version of the CDT you are using as well as the complete error message.
I'm also unaware of any existing CDT issues outside of the vCPU compilation issues which block one never addressed.
Commands I'm using:
``` mkdir atomictokenpeg cd atomictokenpeg zeus box create zeus unbox atomictokenpeg zeus compile zeus test atomictokenpeg --enable-features --services="ipfs,cron,sign,oracle" --single-chain ```
Output from unbox command:
``` zeus test atomictokenpeg -c --enable-features --services="ipfs,cron,sign,oracle" --single-chain ⚗️ Generating ./contracts/eos/dappservices/auth.hpp auth ⚗️ Generating ./contracts/eos/dappservices/cron.hpp cron ⚗️ Generating ./contracts/eos/dappservices/_dns_impl.hpp dns ⚗️ Generating ./contracts/eos/dappservices/history.hpp history ⚗️ Generating ./contracts/eos/dappservices/ipfs.hpp ipfs ⚗️ Generating ./contracts/eos/dappservices/log.hpp log ⚗️ Generating ./contracts/eos/dappservices/oracle.hpp oracle ⚗️ Generating ./contracts/eos/dappservices/readfn.hpp readfn ⚗️ Generating ./contracts/eos/dappservices/sign.hpp sign ⚗️ Generating ./contracts/eos/dappservices/_storage_impl.hpp storage ⚗️ Generating ./contracts/eos/dappservices/vaccounts.hpp vaccounts ⚗️ Generating ./contracts/eos/dappservices/_vcpu_impl.hpp vcpu ⚗️ Generating ./zeus_boxes/dns-dapp-service/services/dns-dapp-service-node/index.js dns ⚗️ Generating ./zeus_boxes/storage-dapp-service/services/storage-dapp-service-node/index.js storage ⚗️ Generating ./zeus_boxes/vcpu-dapp-service/services/vcpu-dapp-service-node/index.js vcpu ⚗️ Generating ./contracts/eos/dappservices/dns.hpp dns ⚗️ Generating ./contracts/eos/dappservices/storage.hpp storage ⚗️ Generating ./contracts/eos/dappservices/vcpu.hpp vcpu ⚡ EOSIO CONTRACT COMPILING -- Setting up Eosio Wasm Toolchain 1.8.0 at /usr -- Configuring done -- Generating done -- Build files have been written to: /home/ubuntu/environment/atomictokenpeg/contracts/eos ⚫ Scanning dependencies of target atomictokenpeg ◼️ [ 0%] Performing build step for 'atomictokenpeg' ⚫ Scanning dependencies of target atomictokenpeg ◼️ [ 50%] Building CXX object CMakeFiles/atomictokenpeg.dir/atomictokenpeg.cpp.obj Warning, action
Updated Truffle Config File:
``` /** * Use this file to configure your truffle project. It's seeded with some * common settings for different networks and features like migrations, * compilation and testing. Uncomment the ones you need or modify * them to suit your project as necessary. * * More information about configuration can be found at: * * truffleframework.com/docs/advanced/configuration * * To deploy via Infura you'll need a wallet provider (like truffle-hdwallet-provider) * to sign your transactions before they're sent to a remote public node. Infura accounts * are available for free at: infura.io/register. * * You'll also need a mnemonic - the twelve word phrase the wallet uses to generate * public/private key pairs. If you're publishing your code to GitHub make sure you load this * phrase from a file you've .gitignored so it doesn't accidentally become public. * */ // const HDWalletProvider = require('truffle-hdwallet-provider'); // const infuraKey = "fj4jll3k....."; // // const fs = require('fs'); // const mnemonic = fs.readFileSync(".secret").toString().trim(); module.exports = { /** * Networks define how you connect to your ethereum client and let you set the * defaults web3 uses to send transactions. If you don't specify one truffle * will spin up a development blockchain for you on port 9545 when you * run `develop` or `test`. You can ask a truffle command to use a specific * network from the command line, e.g * * $ truffle test --network
Additional Details:
Zeus Version:
``` zeus --version 2.1.7962 ```
OS Version:
``` lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.6 LTS Release: 18.04 Codename: bionic ```
NPM Version:
``` npm -v 8.5.0 ```
NodeJS Version:
``` node -v v16.14.2 ```
Nodeos Version:
``` nodeos -v v2.1.0 ```
CDT Version:
``` eosio-cpp -v clang version 9.0.1 (https://github.com/eosio/clang.git 65c99a019ef4cffed9c5f68bdfd8079ab35f4289) (https://github.com/eosio/llvm 423a4ac7a7074e139c4f4c2f786d6b71d1b0965e) Target: x86_64-unknown-linux-gnu Thread model: posix InstalledDir: /home/ubuntu/environment Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7.5.0 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/8 Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7.5.0 Candidate multilib: .;@m64 Selected multilib: .;@m64 ``` i.e. eosio.cdt_1.8.0-1-ubuntu-18.04_amd64.deb
Dewald928
I'm trying to test out the eosio <> evm nft bridge, namely atomictokenpeg
But when I try to compile it, the cdt is giving issues. Have the CDT issues still not been fixed? It's such a good service, I'd love to use it.
Any ideas of how to fix it? Will this be fixed in the future?