Skip to content

Conversation

@FaHaGit
Copy link
Contributor

@FaHaGit FaHaGit commented Jun 20, 2025

No description provided.

Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
@FaHaGit FaHaGit requested a review from barsnick June 20, 2025 09:25
@FaHaGit
Copy link
Contributor Author

FaHaGit commented Jun 20, 2025

Should be mostly the same changes as in #53

@FaHaGit FaHaGit requested a review from lategoodbye June 20, 2025 10:27
└── 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
Copy link
Contributor

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)

Copy link
Member

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 ?

Copy link
Contributor

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>
@lategoodbye lategoodbye requested a review from barsnick June 23, 2025 14:22
Copy link
Contributor

@barsnick barsnick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@lategoodbye lategoodbye merged commit 6d4f470 into everest/charge_som Jun 24, 2025
1 check passed
@lategoodbye lategoodbye deleted the everest/chargesom-revision-of-development-chapter branch June 25, 2025 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants