Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Brownie does not generate compilation artifacts for dependencies

See original GitHub issue

Hi,

Overview

When running brownie compile, the compilation artifacts for the dependencies will not be generated in build/contracts/. This prevents third-party tools to analyze the contracts (for example https://github.com/crytic/slither/issues/638)

It would be great if all the json could be available after compilation

Issue Analytics

State:
Created 3 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

1reaction

montylycommented, Oct 26, 2020

Hi @iamdefinitelyahuman, if the files are copied into build/contracts/dependencies/[org]/[repo]@[version]/ it will work for slither.

We could make it work with ~/.brownie, but looking only into the local folder is probably a cleaner option.

0reactions

sssubikcommented, Jan 27, 2021

Hey @montyly Thanks for the response. Can I do this now manually by copying json files from .brownie folder? Like how should the build structure folder be for that??

Top Results From Across the Web

Unable to Compile Contract in Brownie (not receiving a .json ...

It says project has been compiled but I don't see the .json file anywhere. Do you have any suggestions? I think I may...

The Build Folder — Brownie 1.14.5 documentation

Brownie generates compiler artifacts for each contract within a project, which are stored in the build/contracts folder. The structure of these files are...

eth-brownie/community - Gitter

I have a problem: brownie.reverts() does not handle "base fee exceeds gas limit" ... What should I do to make brownie script work...

Brownie Documentation - Read the Docs

This will send the compiled build artifacts to MythX for analysis. By default no login is required and the analysis is.

Fixing metadata with component metadata rules

The main difference between writing rules and defining dependencies and artifacts in the build script is that component metadata rules, following the ...