-
-
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
Add support for in-model libraries #164
Comments
The main drive for this is partially handled by #219 which no longer needs an internet connection and is easy to modify - the downside being that the package / code is not easy to distribute with the model and not easy to version. |
After we finalize the implementation of this feature, we should look into developing an importer plugin which can take an existing package as input (either location (web/local) or zip file) and generate the in-model library from it. |
Allow a new type of library which can contain
0..*
header files and0..*
source files. The library will be generated as a ROS package that can be used just like any other library, except the code will live in the model and will therefore be able to be compiled without needing an internet connection and simpler to modify as needed.The text was updated successfully, but these errors were encountered: