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

micromodules #538

Open
schuhschuh opened this issue Apr 17, 2016 · 0 comments
Open

micromodules #538

schuhschuh opened this issue Apr 17, 2016 · 0 comments

Comments

@schuhschuh
Copy link
Contributor

Issue by ahundt
Tuesday Jan 05, 2016 at 06:38 GMT
Originally opened as cmake-basis/legacy#538


In the project I'm developing sometimes there are single library files or executable files that add new dependencies, so they are much too small to be a full module because the source code would simply get too confusing. However it may make sense to have some sort of "micro module" concept that lets us take advantage of the module enabling and disabling functionality for that component.

These dependencies make code much harder for new users to set up, so being able to easily disable those components could be very useful. I don't have any advice of value on how to implement this yet.

What do you think of the idea of micromodules?

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

1 participant