---

** [tickets:#2084] build: Refactor the directory structure and build system**

**Status:** assigned
**Milestone:** 5.2.FC
**Created:** Thu Sep 29, 2016 02:15 PM UTC by Anders Widell
**Last Updated:** Thu Sep 29, 2016 02:15 PM UTC
**Owner:** Anders Widell


Improve the OpenSAF directory structure and build system. The exact details of 
what and how to improve them is yet to be worked out, but below are some ideas:

* In order to support better modularity of the different OpenSAF services, we 
should collect all files belonging to a particular OpenSAF service under a 
separate subdirectory per service. Today, files belonging to one single service 
(source code, library code, header files, tests, command-line tools) are 
scattered in many places.
* Rename directories where appropriate. For example remove the "sv" suffix, 
e.g. clmsv -> clm.
* Look at "standards" to see what kind of directory structure is commonly used 
by other projects. For example, maybe put the source code in a directory called 
"src".
* Reduce the depth of the directory hierarchy. Some levels of the directory 
structure can be removed, for example the separate "include" directory that 
some services (but not all) currently use for their header files. Header files 
ought to into the same directory as source files. Another example is that we 
don't really need to divide services into "saf" and "infrastructure" and thus 
remove this level in the tree.
* Improve parallelism of the build. I have a feeling that much more could be 
built in parallel than is possible today when you type "make -j".
* Possibly look at alternatives to autotools, to see if we can also support 
something else (e.g. cmake) in addition to autotools.


---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to