rvct3.1可以按照在win7上吗

1. 双击\RVDS3.1目录下setup.exe., 出现界面选项都选择默认,一直单击下一个,直到出现ARM License Wizard界面,

执行如下步骤:

选择 Diagnose license management probl,

单击下一步,

点击 Run Diagnostics,等待运行完成,

单击下一步,选择 是, 点击完成.

按照提示关闭其他窗口,完成安装

2. 把rvds4.crack目录下全部内容复制到C:\Program Files\ARM 目录下, 运行crack.bat. 运行完成后,License被重新写到rvds.dat.

3. 在C:\Program Files\ARM目录下新建licenses目录,把C:\Program Files\ARM目录下rvds.dat复制到中,把rvds.dat改名为license.dat.

4. 打开license.dat, 找到HOSTID=C80AA94F06E1,替换文件中HOSTID所有值为自己网卡的mac地址.保存退出.

5. 打开 开始à所有程序àarmàLicense Wizard V4.1 ,选择下一步,选择 Install License,点击下一步,点击 下一步,出现如下截图,选择

使用的是别人的静态库吧？使用别人提供的 .a库链接时候出现L6242E错误。

L6242E: Cannot link object <objname>as its attributes are incompatible with the image attributes

There are three common reasons for this error message:

1) Error: L6242E: Cannot link object foo.o as its attributes are incompatible with the image attributes.

... require 4-byte alignment of 8-byte datatypes clashes with require 8-byte alignment of 8-byte datatypes.

This can occur when linking RVCT objects with legacy objects built with ADS or RVCT 1.2. The Application Binary Interface (ABI) was changed between ADS and RVCT 2.0. In ADS and RVCT 1.2, "double" and "long long" data types were 4-byte aligned (unless -Oldrd or __align were used). In RVCT 2.0 onwards, "double" and "long long" data types are now 8-byte aligned, according to the new EABI.

These changes mean that legacy ADS/RVCT1.2 objects and libraries using "double" or "long long" data types are not directly compatible with RVCT 2.x/3.x objects/libraries, and so the linker will report an attribute clash.

Some compatibility is made possible, with some restrictions, by way of the --apcs /adsabi switch in RVCT 2.x/3.0. To allow RVCT 2.x/3.0 C objects to be used with legacy ADS C objects, compile the RVCT 2.x/3.0 C code with --apcs /adsabi (--apcs /adsabi was deprecated in RVCT 2.2 and removed from RVCT 3.1).

2) Error: L6242E: Cannot link object foo.o as its attributes are incompatible with the image attributes.

... pure-endian double clashes with mixed-endian double.

This can occur when linking RVCT or ADS objects with legacy SDT objects or objects built using --fpu softfpa or --fpu fpa. SDT uses a non standard format for little-endian 'double' and big-endian 'long long'. However ADS and RVCT use industry-standard 'double' and 'long long' types, except for when the --fpu softfpa and --fpu fpa are used. If you attempt to link object files that use the different formats for little-endian 'double' and big-endian 'long long' then the linker will report this error.

The recommended solution is to rebuild your entire project with RVCT. If you do not have the source code for an object or library, then try recompiling your RVCT code with --fpu softfpa (only supported in RVCT 2.1 and earlier).

3) Error: L6242E: Cannot link object foo.o as its attributes are incompatible with the image attributes.

... FPA clashes with VFP.

This error typically occurs when attempting to link objects built with different --fpu options. The recommended solution is to rebuild your entire project with RVCT, with the same --fpu options.

sansiloudeyu However ADS and RVCT use industry-standard 'double' and 'long long' types, except for when the --fpu softfpa and --fpu fpa are used 关键在这里，都是用ads编，有的enable了--fpu softfpa --fpu fpa 有的没有

sansiloudeyu /swst 支持stack-checked /nonswst 不支持stack-checked 关于stack-checked 可以到http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0234b/CDCCEIFG.html 搜索到，大概是用来支持stack 信息的如果这两项选项不一致会爆出： stack-checked clashes with not-stack-checked.

---