This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
'enable' in 'ecos.db'
- To: "Ecos" <ecos-discuss at sourceware dot cygnus dot com>
- Subject: [ECOS] 'enable' in 'ecos.db'
- From: "Jurica Baricevic" <jura at INTESIS dot hr>
- Date: Wed, 14 Jun 2000 10:34:25 +0200
- Reply-To: "Jurica Baricevic" <jura at INTESIS dot hr>
Hi!
Which is the best way for maintaining HAL sources for very similar
platforms? By 'very similar' I meant that only a few lines of HAL code
should be changed from one platform to another. The obvious solution is to
have a HAL package for each platform, but it is very hard to keep and update
i.e. five (or more) almost the same source trees. Is there some more
'elegant' solution in eCos? I would like to have only one source tree with a
few #ifdef statements in sources and a simple mechanism for *automatic*
choosing appropriate switches by selecting particular target. I noticed
keyword 'enable' (in 'ecos.db' file) that could probably help me in my
endeavors, but it is not documented.
Thanks,
Jura