-
Notifications
You must be signed in to change notification settings - Fork 90
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
generic_fss checkout applications #380
Labels
Feature
New Feature
Comments
kevincbruce
added a commit
to nasa-itc/generic_fss
that referenced
this issue
Dec 11, 2024
…g, and editing the FSS Device Code into the shared folder, and adapting the sample checkout code to work for FSS.
kevincbruce
added a commit
that referenced
this issue
Dec 11, 2024
…ple Checkout files to work for FSS
kevincbruce
added a commit
to nasa-itc/generic_adcs
that referenced
this issue
Dec 11, 2024
kevincbruce
added a commit
to nasa-itc/generic_fss
that referenced
this issue
Dec 11, 2024
kevincbruce
added a commit
that referenced
this issue
Dec 11, 2024
…ted generic_adcs includes paths in cmake to include the new shared directory for the fss device
jlucas9
added a commit
to nasa-itc/generic_fss
that referenced
this issue
Dec 18, 2024
…a .gitignore, and using the extra debug flags;
jlucas9
added a commit
that referenced
this issue
Dec 18, 2024
…d folders, added a sim_truth_interface to the configuration, and setup environment for quick testing of the FSS checkout for others to review;
kevincbruce
added a commit
to nasa-itc/generic_fss
that referenced
this issue
Dec 18, 2024
[nasa/nos3#380] fss checkout application
kevincbruce
added a commit
to nasa-itc/generic_adcs
that referenced
this issue
Dec 18, 2024
[nasa/nos3#380] fss checkout application
kevincbruce
added a commit
that referenced
this issue
Dec 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue will require creating a support folder inside of the generic_fss component in the same way that the sample has one.
The text was updated successfully, but these errors were encountered: