public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Hugo Tyson <hmt@redhat.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Build->Packages WinNT eCos Config Tool Error
Date: Wed, 02 May 2001 07:00:00 -0000	[thread overview]
Message-ID: <wwt4rv3dfn3.fsf@masala.cambridge.redhat.com> (raw)
In-Reply-To: <85256A40.004A57D7.00@tormta3.tor.cel.com>


"Sergio Nunes" <snunes@Celestica.com> writes:

> I don't really want to edit these templates. What I would like to do is
> add/remove packages from an existing eCos Configuration using the eCos
> configuration tool. However, when I try to add/remove packages using the
> Build->Packages menu option I get the error message mentioned below.  Am
> I doing something wrong or is this a bug.  What's the purpose of the
> Build->Packages function if it gives you an error/warning everytime you
> try to change a package?

But it doesn't if the package is not a hardware type package.

For example, you could add or remove the uITRON compatibility package, or
the POSIX package and it would be fine.  Try it please?  If you cannot do
that, then you have indeed found a bug in the Config Tool!

But hardware packages are labelled hardware because they can only be used
on certain hardware.  It makes no sense to add the flash driver for an
EBSA285 board to a build for PowerPC PBX board, so you can't do that.

If you are working on a new platform, and you want to re-use some hardware
packages from a similar existing platform, that's easy.  For your new
platform you must have created a "target" entry in ecos.db - at the very
minimum you will have listed HAL packages for the new target there, so if
you list _all_ the hardware packages to use in the target entry, they will
be included when you select that platform as the build target.

For example

    target nano {
      alias { "nanoEngine StrongARM SA1110 board" nano nanoEngine }
      packages { CYGPKG_HAL_ARM
	  CYGPKG_HAL_ARM_SA11X0
	  CYGPKG_HAL_ARM_SA11X0_NANO
	  CYGPKG_IO_SERIAL_ARM_SA11X0
	  CYGPKG_DEVS_FLASH_NANO
	  CYGPKG_DEVS_FLASH_STRATA
	  CYGPKG_DEVICES_WATCHDOG_ARM_SA11X0
	  CYGPKG_IO_PCI
	  CYGPKG_DEVS_ETH_ARM_NANO
	  CYGPKG_DEVS_ETH_INTEL_I82559
      }
      description "
      The nanoEngine target provides the packages needed to run
      eCos on a Bright Star Engineering nanoEngine StrongARM SA1110 board."
    }

Every one of those packages listed is marked "hardware" because they are
hardware specific; it is pre-defined what targets they can work with, and
selecting one of those targets is the only way to include these packages.

Note that this does not mean that all builds for this target will be
bloated by unused code; many of these platform specific packages
(eg. CYGPKG_DEVS_FLASH_* and CYGPKG_DEVS_ETH_*) will be inactive unless the
generic device driver (CYGPKG_IO_FLASH and CYGPKG_IO_ETH_DRIVERS
respectively) are also included.  And whether to include those generic
drivers is controlled by the Build->Packages facility or the template
chosen or "ecosconfig add", and so on, like any non-hardware-specific
package.

HTH,
	- Huge


> Sergio Nunes wrote:
> >
> > I get the following error/warning message "Add and remove Hardware Packages by
> > selecting a new hardware Template" when I try to create a build package using
> > the Build->Package option under WinNT version of eCos configuration tool.

  reply	other threads:[~2001-05-02  7:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02  6:33 Sergio Nunes
2001-05-02  7:00 ` Hugo Tyson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-02  7:05 Sergio Nunes
2001-05-01 13:51 Sergio Nunes
2001-05-01 14:44 ` Jonathan Larmour

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=wwt4rv3dfn3.fsf@masala.cambridge.redhat.com \
    --to=hmt@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    /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).