Re: (should have been v2 libbsd: Make modules configurable via ini files.)

2018-04-10 Thread Christian Mauderer
Am 10.04.2018 um 02:07 schrieb Chris Johns: > On 09/04/2018 23:58, Christian Mauderer wrote: >> Sorry, missed the subject line in git send-email. This description is to >> the v2-patch-set for the libbsd waf changes. >> >> Am 09.04.2018 um 15:53 schrieb Christian Mauderer: >>> Hello, >>> >>> this v

Re: (should have been v2 libbsd: Make modules configurable via ini files.)

2018-04-09 Thread Chris Johns
On 09/04/2018 23:58, Christian Mauderer wrote: > Sorry, missed the subject line in git send-email. This description is to > the v2-patch-set for the libbsd waf changes. > > Am 09.04.2018 um 15:53 schrieb Christian Mauderer: >> Hello, >> >> this version now contains some changes like discussed with

Re: (should have been v2 libbsd: Make modules configurable via ini files.)

2018-04-09 Thread Christian Mauderer
Sorry, missed the subject line in git send-email. This description is to the v2-patch-set for the libbsd waf changes. Am 09.04.2018 um 15:53 schrieb Christian Mauderer: > Hello, > > this version now contains some changes like discussed with Chris Johns: > > - I moved the fragment composers to bu

libbsd: Make modules configurable via ini files.

2018-04-06 Thread Christian Mauderer
Hello, also I had really bad luck with some patches today, I'll post these for feedback: This is a part of the changes that I plan in the context of https://devel.rtems.org/ticket/3351 The current version already allows to enable or disable modules in the libbsd using a configuration file in the