-
Notifications
You must be signed in to change notification settings - Fork 653
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix README section on adding new submodules #43
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Tried with these instructions, and it builds
@@ -396,7 +396,16 @@ to the project template. | |||
|
|||
git submodule add https://git-repository.com/yourproject.git | |||
|
|||
Then add `yourproject` to the `EXTRA_PACKAGES` variable in the Makefrag. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is still important to keep this right just so that make still tracks the dependencies. I know that SBT handles the build once it is called but I think this is good to keep right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For example, the case that I am trying to avoid is this... you make a change in your new submodule "yourproject" and try to compile without added to the MakeFrag, then make will see that there is no changed sources and the build will continue without taking into account the updated changes. This is if the firrtl file is already generated.
Other than my comment, I can also confirm that this works! LGTM |
* stop exceptions on empty conf files * emit empty verilog file | warn users * put else's on same line as closing bracket
No description provided.