Re: [riot-devel] Updates to the build system - modules definition

Hi Dan, Gaetan, I wonder, what problems are we trying to solve? Maybe we can clearly enumerate them first so that we can check later, whether an improved solution really solves these problems. Cheers, Thomas On 24/11/2017 16:47, Daniel Petry wrote: Hi Gaetan I would like to introduce

Re: [riot-devel] Updates to the build system - modules definition

On 11/24/2017 04:55 PM, Martine Lenders wrote: Hi Daniel, 2017-11-24 16:47 GMT+01:00 Daniel Petry >: […] 1) Move build information concerning a particular module into that module's Makefile 2) Make the module

Re: [riot-devel] Updates to the build system - modules definition

Hi Daniel, 2017-11-24 16:47 GMT+01:00 Daniel Petry : > […] > > 1) Move build information concerning a particular module into that > module's Makefile > 2) Make the module makefiles able to be written with purely declarative > language > 3) Retain backwards

Re: [riot-devel] Updates to the build system - modules definition

Hi Gaetan > I would like to introduce some packaging concepts around RIOT. > To consider modules like well defined distribution packages and not only > source files added to an application firmware. From what you're saying, I understand that the aim is to make modules completely

Re: [riot-devel] Updates to the build system - modules definition

Hi Gaëtan, I think most of us are happy about any more structural approach to the build system, and me personally would prefer if we can stick to GNU standard tools. So in my opinion: go ahead. Maybe - as discussed offline - also start drafting some GitHub issues, outlining the drawbacks you

[riot-devel] RIOT Code of Conduct

Hi *, as some of you might have noticed, I proposed an initial version of a Code of Conduct for the RIOT community [1]. I invite you to discuss this with us, as this effects the whole community. Kind Regards, Martine Lenders [1] https://github.com/RIOT-OS/RIOT/pull/8116