Closed travs closed 6 years ago
Have found a workaround for this.
By passing extra arguments in the .doxityrc
src
field, we can actually add compiler options.
If we do something like:
"src": "--overwrite $(echo $(dapp remappings)) $(find ./src -type f -name '*.sol' -not -name '*.t.sol') ="
then the --overwrite $(echo $(dapp remappings))
part will give the compiler the correct paths to search for dappsys packages. The remaining commands just discover solidity files that are not testfiles.
Might be helpful if there is an added comipler-args
field in .doxityrc
specifically for these things, but as it stands this issue is resolved I think
We are using dappsys to develop our smart contracts.
The way it works is with git submodules, which contain smart contracts we like to depend on. These dependency contracts are in
./lib
, and the contract we actually develop are in./src
.When I try to run
doxity compile
, I get errors like these:In our
.doxityrc
,src
is mapped to our contracts (basically boils down to$(find src -name '*.sol')
).Is there a way to compile without using doxity, and feed doxity the result? Or maybe there is a way to resolve these dependencies within doxity that I don't see yet.