| Creating CDT toolchains with more then two tools skips build steps [message #139686] |
Mon, 28 February 2005 05:16  |
Eclipse User |
|
|
|
Originally posted by: emanuel.schleussinger.ner
Hi all,
i tried to extend the CDT 2.1 to allow for using my ARM-ELF-GCC
toolchain, and add a few steps to the toolchain so it would emit a
..GBA ROM dumpfile as the final result of the compilation. This is
actually not hard to do at all, just a matter of using objcopy and a
few other tools after the elf has been created by GCC ... but heres
the thing:
I cannot get a toolchain to work if it is "longer" than 2 tools. What
I mean? Simple: I am using the toolchain , to chain files from one
extension to the next on their way to the final build target.
these are the tools i set up in the toolchain.
1) I have a compiler tool, that accepts C files and emits O files.
2) I have a linker tool, that accepts O files and emits an .elf
3) I have a objcopy tool, that accepts elf, emits .gba, and converts
the elf to a "gba" file.
I have set my artifact extension (which i think is the final extension
required to build the result of the managed make process), to "gba"
,and this is what happens when i attempt to compile:
make -k all
Building file: ../main.c
arm-elf-gcc -c -omain.o ../main.c
Finished building: ../main.c
Building target: fsdfsdf.gba
arm-elf-objcopy fsdfsdf.gba main.o
c:\dka\bin\arm-elf-objcopy.exe: 'fsdfsdf.gba': No such file
make: *** [fsdfsdf.gba] Error 1
make: Target `all' not remade because of errors.
Build complete for project fsdfsdf
Thats the core of the problem. The tools are expilcitly set up so the
linker step (which is omitted by the managed make process) is the only
stpe that accepts .o files -- however, the O files are getting fed to
the tool that should really only accept an .elf file.
Have you seen an issue like this before? Clue: If i change the final
artifact extension to "elf" the linker step runs through fine and the
linker produces the elf file as it should -- so i doubt it is a
problem with the setup of the linker tool.
Or is this even an issue with the new builder model? I can hardly
imagine...
If you are willing to look at this more closely, here is my complete
plugin.xml:
http://www.ngine.de/eclipse/plugin.xml
Thank you very much for any help on the issue,
Emanuel Schleussinger
http://www.ngine.de
|
|
|
| Re: Creating CDT toolchains with more then two tools skips build steps [message #139698 is a reply to message #139686] |
Mon, 28 February 2005 05:20  |
| Eclipse User |
|
|
|
Originally posted by: emanuel.schleussinger.ner
sorry for the confusing double post . this is an earlier draft of my
other message ... sorry for the noise. Ignore this one please.
best
Emanuel
On Mon, 28 Feb 2005 11:16:33 +0100, Emanuel Schleussinger
<emanuel@schleussinger.ner> wrote:
>Hi all,
>
> i tried to extend the CDT 2.1 to allow for using my ARM-ELF-GCC
>toolchain, and add a few steps to the toolchain so it would emit a
>.GBA ROM dumpfile as the final result of the compilation. This is
>actually not hard to do at all, just a matter of using objcopy and a
>few other tools after the elf has been created by GCC ... but heres
>the thing:
>
>I cannot get a toolchain to work if it is "longer" than 2 tools. What
>I mean? Simple: I am using the toolchain , to chain files from one
>extension to the next on their way to the final build target.
>these are the tools i set up in the toolchain.
>
>1) I have a compiler tool, that accepts C files and emits O files.
>2) I have a linker tool, that accepts O files and emits an .elf
>3) I have a objcopy tool, that accepts elf, emits .gba, and converts
>the elf to a "gba" file.
>
>I have set my artifact extension (which i think is the final extension
>required to build the result of the managed make process), to "gba"
>,and this is what happens when i attempt to compile:
>
>
>make -k all
>Building file: ../main.c
>arm-elf-gcc -c -omain.o ../main.c
>Finished building: ../main.c
>
>Building target: fsdfsdf.gba
>arm-elf-objcopy fsdfsdf.gba main.o
>c:\dka\bin\arm-elf-objcopy.exe: 'fsdfsdf.gba': No such file
>make: *** [fsdfsdf.gba] Error 1
>make: Target `all' not remade because of errors.
>Build complete for project fsdfsdf
>
>Thats the core of the problem. The tools are expilcitly set up so the
>linker step (which is omitted by the managed make process) is the only
>stpe that accepts .o files -- however, the O files are getting fed to
>the tool that should really only accept an .elf file.
>
>Have you seen an issue like this before? Clue: If i change the final
>artifact extension to "elf" the linker step runs through fine and the
>linker produces the elf file as it should -- so i doubt it is a
>problem with the setup of the linker tool.
>
>Or is this even an issue with the new builder model? I can hardly
>imagine...
>
>If you are willing to look at this more closely, here is my complete
>plugin.xml:
>http://www.ngine.de/eclipse/plugin.xml
>
>Thank you very much for any help on the issue,
>Emanuel Schleussinger
>http://www.ngine.de
|
|
|
Powered by
FUDForum. Page generated in 0.10316 seconds
Home