------- Additional Comments From sebastian dot huber at embedded-brains dot de 2008-11-18 09:15 ------- Hi Nick,
we could of course use the C pre-processor or a billion other tools to generate a linker command file, but the linker should do its job without the need of external tools. The linker has already the capability to gather its linker command file from various files via the INCLUDE function. So I guess that someone had in mind that you should be able to split the hole stuff into general and specific parts. One point against your single project solution is that this feature might be useful for other projects too. Lets consider a practical example for the PowerPC architecture: The MPC8313E RDB has a huge RAM of 128 MB and the MPC5566 EVB has only a small RAM of 128 kB but it can execute its code from a ROM. The only difference (except RAM and ROM dimensions) in the linker command files of these two boards is that in the first case the code section goes into the RAM region and in the second case it goes into the ROM region. With the current linker command file facilities you cannot provide a general part that may be used for both boards. So now you have the choice to generate it via external tools or enhance the linker command file facilities. The above example illustrates an every day problem for the linker if you work with various boards. So from my point of view we should enhance the linker. Have a nice day! -- http://sourceware.org/bugzilla/show_bug.cgi?id=7031 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
