Subject: |
which manual describes command-line options of vxWorks gnu Compiler |
From: |
王林 <[email protected]> |
To: |
[email protected] |
Date: |
Sat, 15 Jan 2011 00:05:55 +0800 (CST) |
Hi All,
For a compiling for EPICS example application like this,
/home/wanglin/Tornado2.2/host/x86-linux/bin/ccppc -c -D_POSIX_SOURCE -DCPU=PPC604 -DvxWorks -include /home/wanglin/Tornado2.2/target/h/vxWorks.h -ansi -O3 -Wall -mcpu=604 -mstrict-align -mlongcall -fno-builtin -I. -I.. -I../../../include/os/vxWorks -I../../../include -I/home/wanglin/base-3.14.8.2/include/os/vxWorks -I/home/wanglin/base-3.14.8.2/include -I/home/wanglin/Tornado2.2/target/h ../xxxRecord.c
I don't understand some options like -D_POSIX_SOURCE, -mstrict-align, -mlongcall, -fno-builtin, so I need a manual for this, but in my Tornado directory D:\Tornado2.2\SETUP\DOCS, there is a diab_compiler_for_powerpc_users_guide_5.0 file rather than a gnu one.
Can you tell me which manual describes command-line options of vxWorks gnu Compiler?
Thanks,
Lin Wang
- Replies:
- RE: which manual describes command-line options of vxWorks gnu Compiler Jeff Hill
- Navigate by Date:
- Prev:
VMEbus ACFAIL* glitch causes OMS VME58 reboot Ron Sluiter
- Next:
RE: which manual describes command-line options of vxWorks gnu Compiler Jeff Hill
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
VMEbus ACFAIL* glitch causes OMS VME58 reboot Ron Sluiter
- Next:
RE: which manual describes command-line options of vxWorks gnu Compiler Jeff Hill
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|