-
-
Notifications
You must be signed in to change notification settings - Fork 7
-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Need to add non-binary/non-generated deployment files to meta-model #16
Comments
Should these be assets? How should they be stored, and how do we know where they go or how to manage them? I.e. are they always zip files that we always extract into the deployment directory? |
This is related to the #89 issue regarding configuration files for simulators. There may be an arbitrary number of files that are required for the deployed binary (component or simulator) and they may need to go into specific directories. Easiest way to handle this is to store a single asset of a |
Files such as
camera.yml
which is required for theimageProcessor
aruco
code needs to be captured in the meta-model/model and must be deployed and managed with the binaries.The text was updated successfully, but these errors were encountered: