我正在为ARM构建一个简单的程序。 GPRbuild输出以下内容:
gprbuild -p -P avocado_test.gpr (in directory: /home/rodeo/Projects/AvocadoTest)
Bind
[gprbind] run_avocado_test.bexch
[Ada] run_avocado_test.ali
Link
[link] run_avocado_test.adb
/opt/GNAT/arm-elf/bin/arm-eabi-ld: unrecognised emulation mode: cpu=cortex-m3
Supported emulations: armelf
gprbuild: link of run_avocado_test.adb failed
Compilation failed.
从我在网上找到的,ld
有一个开关-m
,它指定了一个仿真模式。但是,我没有在我的项目的链接器中使用此开关。我在编译器中使用-mcpu=cortex-m3
开关,看起来好像GPRbuild也将此开关传递给链接器。这是我的.gpr
文件:
project Avocado_Test is
for Source_Dirs use ("source");
for Object_Dir use "build";
for Main use ("source/run_avocado_test.adb");
for Target use "arm-eabi";
for Runtime ("Ada") use "ravenscar-sfp-sam3x8e";
package Builder is
for Executable_Suffix use ".elf";
for Switches ("Ada") use ("-j0");
end Builder;
package Compiler is
for Driver ("Ada") use "arm-eabi-gcc";
for Switches ("Ada") use (
"-mthumb",
"-mcpu=cortex-m3",
"-O2");
end Compiler;
package Binder is
for Driver ("Ada") use "arm-eabi-gnatbind";
end Binder;
package Linker is
for Driver use "arm-eabi-ld";
end Linker;
end Avocado_Test;
为什么链接器会从编译器中切换?我该如何防止这种情况?
在任何GPR包中我都不会使用Driver
。一旦gprbuild
看到for Target use "arm-eabi";
它知道将arm-eabi-
添加到每个工具。
没有理由避免将编译器开关传递给默认的链接器驱动程序,即gcc
(在本例中为arm-eabi-gcc
),因为它知道它们中的哪一个传递给链接器。
你可能会从我的cortex-gnat-rts项目中找到这些有趣的东西:runtime.xml(但请注意,细节可能与AdaCore的运行时不同),testbed.gpr。