-
Notifications
You must be signed in to change notification settings - Fork 3
Everest/chargesom: Revision of development chapter #55
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
Everest/chargesom: Revision of development chapter #55
Conversation
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
|
Should be mostly the same changes as in #53 |
docs/source/development.rst
Outdated
| └── toolchain.cmake | ||
| #. Run the following command inside to configure the build. | ||
| #. Create a new :code:`build_tarragon` directory in the EVerest project directory (e.g. within your own EVerest |
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.
build_tarragon is not an obvious choice for a Charge SOM build dir. 😉
(Four occurrences)
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.
How about naming it build_cross ?
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.
The problem we encounter is that some of us build for both Tarragon and Charge SOM. In general though, that's okay.
- fix file transfer protocol - adapt build directory to Charge SOM - fix manifest filename Signed-off-by: Stefan Wahren <stefan.wahren@chargebyte.com>
barsnick
left a comment
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.
Looks good.
No description provided.