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

Integrate C code library distribution #5

Closed
ricopicone opened this issue Jan 27, 2022 · 1 comment
Closed

Integrate C code library distribution #5

ricopicone opened this issue Jan 27, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@ricopicone
Copy link
Contributor

Integrate the C code library distribution https://github.com/rtc-book/rtcbook-myrio-lib

Is there an advantage to having the library in a separate repository? When I created it separately, I thought it made sense so we could separate the C library from the rest of the dev environment. But the library can only have separate utility if we put out multiple myRIO-based environments. I suppose that is possible, even likely.

Ok, I have convinced myself this is the correct structure. Let's integrate the library as a submodule.

How? Submodule. Try to mitigate the complications this involves, if possible.

@ricopicone ricopicone self-assigned this Jan 27, 2022
@ricopicone ricopicone added the enhancement New feature or request label Jan 29, 2022
@ricopicone
Copy link
Contributor Author

ricopicone commented Jan 30, 2022

There are levels in distribution:

  • VM (this repo)
    • workspace
      • .metadata
      • library distribution (rtcbook-myrio-lib repo)
      • stub lab projects

In development, it's similar:

  • VM
    • workspace
      • .metadata
      • library distribution (rtcbook-myrio-lib-source repo)
      • full lab projects

We need a rational structure of repos that's not cumbersome but flexible enough to share code across them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant