You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: