From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bart Veer <bartv@cygnus.co.uk>
To: alex@clockwork.freeserve.co.uk
Cc: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Re: CPU Ports for eCos
Date: Wed, 28 Apr 1999 04:17:00 -0000
Message-id: <199904281116.MAA32569@sheesh.cygnus.co.uk>
References: <00f201be90f1$50c61730$63a1883e@plath.Workgroup> <00f201be90f1$50c61730$63a1883e@plath.Workgroup>
X-SW-Source: 1999-04/msg00032.html

>>>>> "Alex" == alex  <alex@clockwork.freeserve.co.uk> writes:

    >> Since
    >> eCos makes use of some compiler facilities that are tied to ELF

    Alex> Was that a good idea ?

In the medium to long term, yes. Technically ELF is superior to older
object formats such as a.out and COFF, it makes it much easier to
implement facilities such as constructor priority ordering and
selective linking. I believe that just about every new toolchain port
involves ELF as either the only object format or the preferred one.
Older toolchains may get updated because of user demand, partly
because of eCos but also because other systems like Linux use ELF.

In the short term there will be some targets where the ELF dependency
makes an eCos port more difficult. This is unfortunate, but the long
term advantages outweigh this.

Bart Veer // eCos net maintainer