Re: Base a custom bsp on an existing one

Hi Wayne, On Fri, Jun 17, 2016 at 02:28:26PM +0100, Wayne Keenan wrote: > or perhaps I'll break up my app into parts that can be independently > included as dependencies in the pkg.deps section of pkg.yml. > > Is it possible to use 'features' to include/exclude subdirectories of > > source and

Re: Base a custom bsp on an existing one

or perhaps I'll break up my app into parts that can be independently included as dependencies in the pkg.deps section of pkg.yml. All the best Wayne On 17 June 2016 at 09:41, Wayne Keenan wrote: > Is it possible to use 'features' to include/exclude subdirectories of >

Re: Base a custom bsp on an existing one

Is it possible to use 'features' to include/exclude subdirectories of source and include under app/myapp/ ? For example, I may have an app which *can* use bluetooth if available, but I may want to have a target with a hardware platform that doesn't have bluetooth so I don't want to compile any

Re: Base a custom bsp on an existing one

Great, I'll give features a try. Thanks! On Thu, Jun 9, 2016 at 10:33 AM, Sterling Hughes wrote: > Hi Simon, > > I agree with Will’s response, the problem you have with “inherit’ing” > BSPs, at least at this stage, is that the APIs are changing, and everything > that

Re: Base a custom bsp on an existing one

Hi Simon, I agree with Will’s response, the problem you have with “inherit’ing” BSPs, at least at this stage, is that the APIs are changing, and everything that inherits the BSP will have to change as we morph APIs. However, you shouldn’t have to maintain a different BSP for every slightly