our lm4f code relies on a rasware repo that is located the /home directory of hal, which btw currently contains files that aren't committed. so the content of the rasware that our lm4f code depends on can't be gleaned from this igvc repo.
maybe the embedded stuff should be a submodule tracking a fork or branch of rasware, with our lm4f code in a project right next to rasdemo & rastemplate? or maybe rasware should be a submodule, separate from but depended on by our lm4f code? we just need something that has a gitish link back to rasware so that others cloning this repo can get the same version of it that we depend on.
our lm4f code relies on a rasware repo that is located the /home directory of hal, which btw currently contains files that aren't committed. so the content of the rasware that our lm4f code depends on can't be gleaned from this igvc repo.
maybe the embedded stuff should be a submodule tracking a fork or branch of rasware, with our lm4f code in a project right next to rasdemo & rastemplate? or maybe rasware should be a submodule, separate from but depended on by our lm4f code? we just need something that has a gitish link back to rasware so that others cloning this repo can get the same version of it that we depend on.