eosio.cdt icon indicating copy to clipboard operation
eosio.cdt copied to clipboard

EOSIO.CDT (Contract Development Toolkit) is a suite of tools used to build EOSIO contracts

Results 86 eosio.cdt issues
Sort by recently updated
recently updated
newest added

-- Setting up Eosio Wasm Toolchain 1.7.0 at /usr CMake Warning at CMakeLists.txt:6 (find_package): By not providing "Findeosio.cdt.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration...

After installing the CDT, i.e. to `/opt/eosio-cdt`, the CMake modules in the installed path still contain references to the toolchain in the build root. For example, look in `/opt/eosio-cdt/lib/cmake/eosio.cdt/EosioWasmToolchain.cmake`, and...

I'm trying to add ECDSA signature verification to my contract. However, using the example ECDSA from 3 years ago doesn't seem to work anymore. There are tons of errors I'm...

track-in-jira

brew tap eosio/eosio.cdt - this command runs fine brew install eosio.cdt - this command errors with the following message: eosio.cdt: The intel architecture is required for this software. What can...

I want to link an external library to my contract. I did not find examples on how to do this. All examples are very basic and do not include external...

I used eosio-init to generate the demo project on Ubuntu but am unable to compile it. I am using eosio-cpp version 1.8.1 INPUT: ``` cd build cmake .. ``` OUTPUT:...

Repo for contract code: https://github.com/maxifom/cdt-signed-unsigned-int compiling with cdt 1.8.1 error ``` test33333/src/test33333.cpp:7:3: error: unknown type name 'messages_table'; did you mean 'messages_base'? messages_table _messages(get_self(), get_self().value); ^~~~~~~~~~~~~~ messages_base /usr/local/Cellar/eosio.cdt/1.8.1/opt/eosio.cdt/bin/../include/libcxx/locale:3498:24: note: 'messages_base' declared...

OS X 11.0 - Big Sur I did the manual build steps as per the instructions since I have never gotten the brew install to work correctly This used to...

Need to correct them on the following page. https://developers.eos.io/manuals/eosio.cdt/latest/structeosio_1_1name#variable-value

I'm trying to follow [this](https://developers.eos.io/welcome/v2.2/tools/history-tools/creating-wasms/#building) documentation on how to deployer server WASM which may be called by `initialize` and `run_querry`. When compiling a contract and adding the following: ``` //...

track-in-jira