| Problems with my custom toolchain [CDT 1.2.1] [message #113799] |
Wed, 04 August 2004 12:41 |
Eclipse User |
|
|
|
Originally posted by: Han . Hoekstra . WirelessValue . Nl
Hello all,
I run into a bit of a problem and hope someone can help me.
I'm using CDT 1.2.1 and Eclipse 2.1.3 (I haven't switch to the new versions
yet, because I don't have the time yet to make the switch)
I have created a custom toolchain so that I can use the arm-elf compiler and
linker for my managed make project and this all works fine, the project
compiles and links perfectly.
But for our flash programmer I need an intel hex format file, so I have to
convert the ELF output file into intel hex, this is no problem,
arm-elf-objcopy can do this without a problem. When I do it manually on the
command line it works fine. But now I want to integrate it into my custom
toolchain and here is where I run into problems.
My toolchain is setup as follows :
"arm-elf-g++ -c" is the compiler and has .cpp as its input and .o as its
output.
"arm-elf-gcc" is the linker and has .o as its input and .elf as its output.
Now I have added the "arm-elf-objcopy" tool with the .elf as its input and
..out. But this does not do what I had expected.
I had expected that the linker would automatically be called because the
objcopy tools needs an .elf file as it's input, but the linker never gets
called. And also there is another small problem, the objcopy tool expects
first the input file and then the output file, but managed make generates
the call to objcopy with first the output file name and then the input file
name.
Does anyone know how to solve these problems ?
Greetings,
Han
|
|
|
Powered by
FUDForum. Page generated in 0.02989 seconds
] 
Search
Help
Register
Login
Home
