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

File: [docs/06_how-to-guides/01_compile/01_compile-a-contract-via-cli.md](https://developers.eos.io/manuals/eosio.cdt/latest/how-to-guides/compile/compile-a-contract-via-cli) File: [docs/06_how-to-guides/01_compile/03_compiling-contracts-with-cmake.md](https://developers.eos.io/manuals/eosio.cdt/latest/how-to-guides/compile/compiling-contracts-with-cmake) - URL points to old link: https://developers.eos.io/eosio-home/docs/your-first-contract, which gets redirected (for now). (This affects both 1.7 and 1.8-rc1 versions)

documentation

## Change Description Fix the issue that `-fno-lto` cannot be passed. ``` eosio-ld: Unknown command line argument '-fno-lto-opt'. Try: '/usr/opt/eosio.cdt/1.7.0/bin/eosio-ld -help' eosio-ld: Did you mean '-fno-lto'? ``` ## API Changes...

Create a debugging platform for smart contracts. - [ ] Implementing the GDB server protocol in the WASM backend. This will be a master and slave thread model, so that...

enhancement
in progress

`eosio-cpp` tool should always return an exit code different than 0 when some problem occurred in the build, but it returns exit code 0 even when linker failed to link...

File: [docs/05_best-practices/08_abi](https://developers.eos.io/manuals/eosio.cdt/latest/best-practices/abi/index) File: [docs/05_best-practices/08_abi/01_abi-code-generator-attributes-explained.md](https://developers.eos.io/manuals/eosio.cdt/latest/best-practices/abi/abi-code-generator-attributes-explained) File: [docs/05_best-practices/08_abi/02_manually_write_an_ABI_file_explained.md](https://developers.eos.io/manuals/eosio.cdt/latest/best-practices/abi/manually_write_an_ABI_file_explained) File: [docs/09_tutorials/02_abi-variants.md](https://developers.eos.io/manuals/eosio.cdt/latest/tutorials/abi-variants) The "ABI" title on the left navigation should be all uppercase. Proposed resolution: Use `link_text` element - see [example](https://raw.githubusercontent.com/EOSIO/eosio.cdt/release/1.7.x/docs/05_best-practices/08_abi/00_understanding-abi-files.md).

documentation
staging

File: [docs/05_best-practices/08_abi/02_manually_write_an_ABI_file_explained.md](https://developers.eos.io/manuals/eosio.cdt/latest/best-practices/abi/manually_write_an_ABI_file_explained) - https://developers.eos.io/eosio-cpp/docs/how-to-write-an-abi File: [docs/05_best-practices/08_abi/01_abi-code-generator-attributes-explained.md](https://developers.eos.io/manuals/eosio.cdt/latest/best-practices/abi/abi-code-generator-attributes-explained) - https://developers.eos.io/eosio-cpp/docs/naming-conventions

documentation
staging

File: [libraries/eosiolib/core/eosio/name.hpp](https://developers.eos.io/manuals/eosio.cdt/v1.7/name_8hpp) Operator ""_n does not render in the v1.7 documentation - it does for [v1.5](https://developers.eos.io/manuals/eosio.cdt/v1.5/name_8hpp).

documentation

An important best practice when creating EOSIO accounts, smart contracts, and actions is to know how to name these appropriately to meet EOSIO name encoding requirements. There used to be...

documentation
staging

File: [docs/index.md](https://developers.eos.io/manuals/eosio.cdt/latest/index) https://developers.eos.io/manuals/eosio.cdt/CONTRIBUTING https://developers.eos.io/manuals/eosio.cdt/CONTRIBUTING#conduct https://developers.eos.io/manuals/eosio.cdt/LICENSE

documentation
staging

File: [eosio.cdt/docs/guides/basic-usage.md](https://developers.eos.io/manuals/eosio.cdt/v1.5/guides/basic-usage) https://developers.eos.io/tools/eosio-cpp.html https://developers.eos.io/tools/eosio-ld.html

documentation
staging