This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: .ldi for target but no .mlt -- ok to edit?
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Brett Delmage <Brett at twobikes dot ottawa dot on dot ca>
- Cc: ECOS mailing list <ecos-discuss at ecos dot sourceware dot org>
- Date: Mon, 25 Sep 2006 16:27:42 -0600
- Subject: Re: [ECOS] .ldi for target but no .mlt -- ok to edit?
- References: <Pine.LNX.4.63.0609251748080.24650@pannier.canbike.ca>
Brett Delmage wrote:
For some targets (e.g. lpcmt) I see .ldi and .h files, but no .mlt
The .ldi and .h files state // This is a generated file - do not edit
Can someone please confirm my understanding that:
- this comment is an artifact of a previous generation by the memory
layout tool and not relevant
- that in the absence of a .mlt in pkgconf, it is acceptable to modify the
.ldi and .h files for the proper map, do the build, and they will not be
overwritten by anything else?
In a perfect world (and indeed past times), the .ldi and .h files
were generated from the .mlt file. We haven't had a config tool
which knew how to do that for many years :-(
So, in this environment, the .ldi and .h files (the ones that are
actually used in the build process) must be edited & kept up to
date, by hand. I try to keep the .mlt files accurate as well, in
the hope that someday the tool will return.
Don't worry about your edits being overwritten - there is no
tool at this point which will do that.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss