rtems-bsp-builder .ini file syntax question (for epiphany)

[Joel Sherrill]

On Fri, Sep 7, 2018, 10:06 PM Chris Johns <chrisj at rtems.org> wrote:

> On 8/9/18 12:59 am, Joel Sherrill wrote:
> > On Thu, Sep 6, 2018 at 9:07 PM Chris Johns <chrisj at rtems.org
> > <mailto:chrisj at rtems.org>> wrote:
> >     On 6/9/18 9:00 am, Joel Sherrill wrote:
> >     > https://lists.rtems.org/pipermail/build/2018-September/000997.html
> still has
> >     > epiphany
> >     > failures. Not sure what else is going on. Do you see the pattern?
> >
> >     The 'debug' build is not adding '--disable-networking' as the BSP
> builder is not
> >     tracking defaults or more specifically enabled by default. The SMP
> works because
> >     the default is disabled while networking has a default of enabled.
> >
> > Yes. That's clearly the problem. Any ideas on how to address this? I can
> always
> > force networking off for epiphany in the cpukit. We were talking about
> that anyway.
> > Would it be better if exclude implied --disable?
>
> The solution is add the excluded 'no-' variant of the 'config' to the
> 'base'
> flags. The code currently removes the excluded builds from the build list,
> code
> needs to be added to update the base flags.
>

What's the syntax for that? Or am I making a new features request?

>
> A consequence of this is the need for me to handle the excludes better and
> report any errors if not correct. Currently the support is not strict to
> make
> the code simpler.
>

Glad to hear it is your fault. Lol

Just joking. Rather peeved that Internet is out at my house and so far
Monday 8-10 is their solution. My laptop connected directly to the cable
modem isn't a stable connection. Down varies and up is non-existent.

--joel

>
> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180907/14e19b4c/attachment-0002.html>