[ECOS] Can I also generate other outputs of gcc when build?
wang cui
iucgnaw@msn.com
Fri Sep 22 05:04:00 GMT 2006
As eCos Configuration Tool generate ".o" file for each source file
defaultly.
Manytimes I need to check the preprocessed output(sometimes compiled
assembly output) of source file.
By now, I have to manually call gcc, in a bash shell, with a additional "-E
-o xxx.i" option to generate the preprocessed output for check.
For example:
arm-elf-gcc -c
-I/ecos-c/cygwin/opt/development/project/cpu_4c_lib/lib_install/include
-I/opt/development/ecos/packages/devs/serial/generic/16x5x/current
-I/opt/development/ecos/packages/devs/serial/generic/16x5x/current/src
-I/opt/development/ecos/packages/devs/serial/generic/16x5x/current/tests
-I. -I/opt/development/ecos/packages/devs/serial/generic/16x5x/current/src/
-finline-limit=7000 -mcpu=arm7tdmi -mno-short-load-words -Wall
-Wpointer-arith -Wstrict-prototypes -Winline -Wundef -g -O0
-ffunction-sections -fdata-sections -fno-exceptions
-Wp,-MD,src/ser_16x5x.tmp -E -o src/devs_serial_generic_16x5x_ser_16x5x.i
/opt/development/ecos/packages/devs/serial/generic/16x5x/current/src/ser_16x5x.c
So I am asking can I do something to let eCos Configuration Tool generate
NOT ONLY ".o", BUT ALSO other outputs(.i, .s, etc.)?
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
More information about the Ecos-discuss
mailing list