multiple listing files

"My project has several *.c files, and when it generates listing files it makes one *.lst file for each *.c file !"

Of course it does!

The compiler processes 1 source file at a time; it generates a LST file and an OBJ file from that source file.

The Assembler does the same.

The Linker takes all the separate OBJ files and links them together - it also produces a listing file (often called a "Map" file).
The default for BL51 is .M51; for LX51 it's .MAP

If you don't want the individual translation listings, just turn them off!

"My project has several *.c files, and when it generates listing files it makes one *.lst file for each *.c file !"

Of course it does!

The compiler processes 1 source file at a time; it generates a LST file and an OBJ file from that source file.

The Assembler does the same.

The Linker takes all the separate OBJ files and links them together - it also produces a listing file (often called a "Map" file).
The default for BL51 is .M51; for LX51 it's .MAP

If you don't want the individual translation listings, just turn them off!

Thank you all ..

I needed some file sutible for simulator.. in the case when there are multiple *.lst files and one .m51 file, and also problem with STARTUP.a51 (which is automaticly included when I select device from the list) it's hard to make parser for creating simulator...

Best regards,
Branislava

You mean you're building your own simulator?

Wouldn't it be better to use the existing Keil simulator, and its AGSI to add your extensions??

Surely, you don't need listing files anyhow - what you need is the Debug Information that's contained in the Object File?
That's what the Keil simulator uses, I'm sure!