Skip to content
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

Create a GitHub PR that completes the Blink and Hardware commands tutorials. #7

Open
3 tasks
Tracked by #1
elsevers opened this issue Apr 1, 2024 · 0 comments
Open
3 tasks
Tracked by #1

Comments

@elsevers
Copy link
Contributor

elsevers commented Apr 1, 2024

Abstract

Create a GitHub PR that completes the Blink and Hardware commands tutorials.

Approach

Your PR should:

  • Set up the AMDC development environment following the Private User Applications workflow outlined here (Blink tutorial). This will involve adding the AMDC-Firmware as a git submodule, creating gitignore files, etc. Be sure to review the links about git submodules and think about what it means to be adding
  • Be configured to close this issue
  • Provide a professional PR description (using markdown headings, bulleted lists, etc.) that explains what changes the PR is making to the repository to implement this issue. Keep the description reasonably brief. Examples of effective PRs include this and this. In your PR description please also answer the questions:
    1. What is a Git submodule?
    2. Why are you asked to add AMDC-Firmware as a submodule instead of committing the source files of this code into your repo?

Think Carefully About the Hard Drive Location You Use

For many of you, it will be useful to be able to work on your AMDC project from multiple computers (i.e., a lab PC and your laptop). To make this work smoothly, you are going to want to clone your repo to the same location on your hard disk for both computers prior to completing the Blink Tutorial. See this note in Building and Running Firmware (part of the Blink tutorial):

image

If you absolutely need to use different hard disk locations on each computer, you can adopt relative paths as outlined in this discussion post.

@elsevers elsevers mentioned this issue Apr 1, 2024
8 tasks
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

No branches or pull requests

1 participant