Custom compiler configuration file

If the files do not yet exist, add a reference to the files. Create a custom build tool for parser. This command runs the lexical analyzer on parser. When you build the project, the build system compares the timestamps of parser. If parser. Since parser. Common macros for build commands and properties Troubleshooting Build Customizations. Skip to main content.

This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No.

Any additional feedback? Submit and view feedback for This product This page. In order to enable its output, you need to set outputHumanReadableAbi to true in your config file:. Waffle supports typechain artifacts generation. To enable typed artifacts generation you should set typechainEnabled property to true. You are also able to define target folder for your artifacts by defining typechainOutputDir property, which is set to. Property typechainOutputDir is a path relative to outputDirectory.

This is a powerful feature if you want to asynchronously load different compliation configurations in different environments. For example, you can use native solc in CI for faster compilation, while deciding the exact solc-js version locally based on the contract versions being used. See compilerVersion. See compilerOptions. To compile contracts to work with KLAB one must:. Set appropriate output type. We support two types: one default generates a single file for each contract and the other KLAB friendly generates one file Combined-Json.

The latter type does not meet in contrary to the first one all official solidity standards since KLAB requirements are slightly modified. Set the output in the config file:. If you would like to have code coverage for some file, wallaby. This means that wallaby. Any other dialects or languages that you would like to get code coverage for need to be compiled to JavaScript before the instrumentation phase. To allow for compilation from anything to JavaScript ES6 or earlier , wallaby.

When a custom compiler is configured successfully, your code is resolved correctly and all code assistance actions work as expected. To double-check that your custom compiler is set up properly, do the following:. Load your CMake , Makefile , or compilation database project.

If everything is okay, you will see the compiler type and name as defined in your config file, as well as the list of compiler predefined macros:.

To get schema-specific verification, code completion, quick documentation, and other actions, switch to the Custom Compiler Definition schema.