Add more context to the console output during the build #96
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ration so we can tell which contracts are currently being built.
MitchPierias
approved these changes
Oct 8, 2019
dallasjohnson
deleted the
feature/Add-more-context-to-console-logging-during-build
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a small PR to dip my toe in the water for contributing to an NPM project. I have a few more changes coming through using the lamington code locally on my projects for which I will open separate PRs so as to provide more atomic changes into the project if you guys see them to be valuable changes.
When building Lamington on a project with multiple contracts it is difficult to know which contracts are being built during the build/type generation steps and therefore which if any files should be excluded in the
.lamingtonrcfile to help speed up the build process.This change adds more details of which cpp files are being built and which are being type generated to help with this problem and where the output files are being placed.