Better way to split software in different modules
-
Hello,
I want to create marketing project management software with several modules in C ++ / QtApplication/
-Researsh
-BlocNote
-Planing
-Statistics
-.....And I have questions without answers:
1-Do we have to separate them in the library for each module?
2-Can a dynamic library contain a graphical interface with it .ui?
3-If the dynamic library itself needs another library. for example the blocknote module needs a corrector and a dictionary (hunspell) which requires for commercial software that the library is dynamically linked. So what should I do about this kind of situation?
-Application / lib / blocknote / lib / hunspell (load in the lib blocknote)
or
-Application / lib / blocknote
-Application / lib / hunspell (load the blocknote separately in the app with a sethunspell ())You think this is the method that big software uses to split the software into several modules or there is another way.
-
Hello,
I want to create marketing project management software with several modules in C ++ / QtApplication/
-Researsh
-BlocNote
-Planing
-Statistics
-.....And I have questions without answers:
1-Do we have to separate them in the library for each module?
2-Can a dynamic library contain a graphical interface with it .ui?
3-If the dynamic library itself needs another library. for example the blocknote module needs a corrector and a dictionary (hunspell) which requires for commercial software that the library is dynamically linked. So what should I do about this kind of situation?
-Application / lib / blocknote / lib / hunspell (load in the lib blocknote)
or
-Application / lib / blocknote
-Application / lib / hunspell (load the blocknote separately in the app with a sethunspell ())You think this is the method that big software uses to split the software into several modules or there is another way.
@GeminiMan
1 - no, this is just an option
2 - yes
3 - not clear what you mean. Do you mean additional dependencies? A lib can depend on other libs."You think this is the method that big software uses to split the software into several modules" - yes, it is common to split bigger projects into modules and build those as shared libraries.
-
all right the questions 1 & 2 is clear for me. what do you mean by additional dependencies
@GeminiMan said in Better way to split software in different modules:
what do you mean by additional dependencies
Libraries you app (or libraries used by your app) depends on. I mean libraries not written by you, but used in your application.
