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

Add support for in-model libraries #164

Open
finger563 opened this issue Aug 16, 2017 · 2 comments
Open

Add support for in-model libraries #164

finger563 opened this issue Aug 16, 2017 · 2 comments
Assignees
Milestone

Comments

@finger563
Copy link
Member

Allow a new type of library which can contain 0..* header files and 0..* 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.

@finger563 finger563 added this to the Version 1.2.0 milestone Oct 17, 2017
@finger563 finger563 self-assigned this Oct 17, 2017
@finger563 finger563 modified the milestones: Version 1.2.0, Version 1.3.0 Dec 1, 2017
@finger563
Copy link
Member Author

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.

@finger563
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants