[RTEMS Project] #4213: libbsd: Reduce footprint of minimal buildset

[RTEMS trac]

#4213: libbsd: Reduce footprint of minimal buildset
--------------------------------+---------------------------------
 Reporter:  Christian Mauderer  |       Owner:  Christian Mauderer
     Type:  project             |      Status:  assigned
 Priority:  normal              |   Milestone:  Indefinite
Component:  network/libbsd      |     Version:
 Severity:  normal              |  Resolution:
 Keywords:  SoC libbsd          |  Blocked By:
 Blocking:                      |
--------------------------------+---------------------------------

Comment (by Christian Mauderer):

 My intention for this project are compile time parameters and similar that
 map to "modules" in libbsd (like IPv6 or IPSEC) and have an influence on
 code size. Run time parameters that are controlled for example via sysctl
 are something different and I don't think that mixing them is a good idea
 (*).

 Identifying modules that are not always necessary and disabling them in
 the minimal configuration allows a user to create a buildset that is in
 between minimal and default. But like Chris already pointed out: We can't
 test every configuration. So that will always be a "hope it works"
 configuration. The official buildsets should only provide some useful and
 maintainable subsets. Currently we have:
 - minimal -> As small as possible but still a network and (currently) USB
 stack. I would be happy if it is reduced to the functionality of the
 legacy stack. Later we might discuss whether some additional features
 should be switched off.
 - default -> what most users want if they don't have a size problem
 - everything -> everything that the stack can offer
 - umass -> only USB mass storage support

 (*) Also note: Documenting parameters while having something other as main
 task is most likely hard for a student because we currently don't have a
 basic frame for libbsd. Maybe just playing with different features and
 writing documentation could be a separate project? Can we have a GSoC
 project with no code but documentation as target?

--
Ticket URL: <http://devel.rtems.org/ticket/4213#comment:11>
RTEMS Project <http://www.rtems.org/>
RTEMS Project