public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Luqman Munawar" <haqim1@gmx.de>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] enabling/disabling options
Date: Mon, 18 Feb 2008 11:23:00 -0000	[thread overview]
Message-ID: <20080218112307.195840@gmx.net> (raw)
In-Reply-To: <20080215153652.GC23858@lunn.ch>

Wel, my idea is to take away possibility of mangling with options in case this would end up in a corrupt build.

I know that the system warns in case of most conflicts but there are also cases when you can create a corrupt build without seeing any warning.


For my board, a derivative of freescale mx31 board, I am going to do following:

1) The option should never be enabled: Create an 

"active_if !CYGPKG_HAL_ARM_MX31_MYBOARD" 

for this option.

2) The option should always be enabled:
Create a "requires OPTION_NAME" in the cdl script for my board package as follows:

cdl_package CYGPKG_HAL_ARM_MX31_MYBOARD {
requires OPTION_NAME

}



Is this the way how it is intended in eCos?



Regards,

Luqman Munawar



-------- Original-Nachricht --------
> Datum: Fri, 15 Feb 2008 16:36:52 +0100
> Von: Andrew Lunn <andrew@lunn.ch>
> An: Luqman Munawar <haqim1@gmx.de>
> CC: ecos-discuss@ecos.sourceware.org
> Betreff: Re: [ECOS] difference between active / enabled components?

> On Fri, Feb 15, 2008 at 03:48:26PM +0100, Luqman Munawar wrote:
> > hello,
> > 
> > I have a general question regarding the difference between an active and
> enabled option/components.
> > 
> > I have checked that there is a define for every option that is both
> active and enabled otherwise no define is created in the headers.
> > 
> > So what is the use of having both of them? 
> 
> Active and enabled are two different concepts in CDL.  See
> 
> http://ecos.sourceware.org/docs-latest/cdl-guide/language.properties.html
> 
> Basically, the active property indicates if the option can be
> used. i.e. all the requirements of the option/package are fulfilled
> and all its parents in the hierarchy are enabled. If the property is
> active, you can then enable/disable it.
> 
>         Andrew
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2008-02-18 11:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 14:48 [ECOS] difference between active / enabled components? Luqman Munawar
2008-02-15 14:53 ` Gary Thomas
2008-02-15 15:20   ` Luqman Munawar
2008-02-15 15:37 ` Andrew Lunn
2008-02-18 11:23   ` Luqman Munawar [this message]
2008-02-18 11:31     ` [ECOS] enabling/disabling options Gary Thomas
2008-02-18 13:05       ` Luqman Munawar
2008-02-18 13:21         ` Bart Veer
2008-02-18 13:10 ` [ECOS] difference between active / enabled components? Bart Veer
2008-02-18 15:58   ` Luqman Munawar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080218112307.195840@gmx.net \
    --to=haqim1@gmx.de \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).