All of your contracts are located in your project's
contracts/ directory. As contracts are written in Solidity, all files containing contracts will have a file extension of
.sol. Associated Solidity libraries will also have a
You will generate a
Migrations.sol contract file for deployment by creating an empty TronBox project with the
tronbox init command. Multiple contract files will be generated if you create your project with TronBox Box.
To compile a TronBox project, change to the root of the directory where the project is located and then type the following into a terminal:
Upon the first run, all contracts will be compiled. Upon subsequent runs, TronBox will compile only the contracts that have been changed since the last compile. If you would like to override this behavior, run the above command with the
Artifacts of your compilation will be placed in the
build/contracts/ directory relative to your project root. (This directory will be created if it does not exist.)
These artifacts are integral to the inner workings of TronBox, and play a vital role in the successful deployment of your application. You should not edit these files as they will be overwritten by contract compilation and deployment.
You can declare contract dependencies using Solidity's import command. TronBox will compile contracts in the correct order and ensure all dependencies are sent to the compiler. Dependencies can be specified in two ways:
To import contracts from a separate file, add the following code to your Solidity source file:
This will make all contracts within
AnotherContract.sol available. Here,
AnotherContract.sol is relative to the path of the current contract being written.
Solidity allows other import syntaxes as well. You may see the Solidity import documentation for more information.
TronBox supports dependencies installed via
NPM. To import contracts from a dependency, use the following syntax:
somepackage represents a package installed via
SomeContract.sol represents a Solidity source file provided by that package.
For more information on how to use TronBox's package management features, please see the TronBox NPM documentation.