This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: .mlt and .ldi files


Hi Paul

Paul D. DeRocco wrote:

I've got an .ldi file that has incorrect memory addresses in it, yet it says
that it's a generated file and not to edit. Next to it, I've got an .mlt
file with the same wrong info in it. Is the .ldi generated from the .mlt? Is
it okay to hand-edit the .mlt if it's wrong? If so, what process generates
the .ldi file? I'm using the eCos config tool, as usual. Do I have to do
anything extra in order to regenerate the .ldi?

The mlt_*.ldi and mlt_*.h files were originally generated by the eCos Configuration Tool (version 1.x) from the mlt_*.mlt files. The current eCos Configuration Tool (version 2.x) does not implement memory layout functionality but re-implementation of this functionality is still planned. For the time being, developers should generate the .ldi and .h files directly and can omit the .mlt files in new ports. The important thing is that developers should not deviate from the basic layout of the .ldi and .h files, and thus produce files which could not be re-generated by the original memory layout tool. That would cause big migration problems when the new memory layout functionality is introduced.


John Dallaway
eCosCentric Limited

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]