Displaying 3 results from an estimated 3 matches for "lbaz".
Did you mean:
laz
2013 Jan 07
0
[LLVMdev] [lld] Linker script findings.
...archives to be searched
with GROUP, name the output file with OUTPUT, add new library path directories
with SEARCH_DIR, etc…
Also keep in mind that that linker scripts are usually "inlined" with other command line
options. For example:
ld foo.o --defsym=x=12 -Lbar -T beagle-ram.ld -lbaz bar.o
As you said, it makes sense to parse it during command line argument parsing.
--
Meador Inge
CodeSourcery / Mentor Embedded
http://www.mentor.com/embedded-software
2013 Jan 06
5
[LLVMdev] [lld] Linker script findings.
On Wed, Jan 2, 2013 at 12:04 PM, Shankar Easwaran
<shankare at codeaurora.org> wrote:
> You might want to look at the ELFLayout changes to see what functionality is
> missing from that.
>
> The ELFLayoutOptions has a hook into reading the Linker script which needs
> to be implemented.
So, looking into it a bit, I think that ELFLayoutOptions is not the
right place to parse the
2013 Jan 07
1
[LLVMdev] [lld] Linker script findings.
...GROUP, name the output file with OUTPUT, add new library path directories
> with SEARCH_DIR, etc…
>
> Also keep in mind that that linker scripts are usually "inlined" with other command line
> options. For example:
>
> ld foo.o --defsym=x=12 -Lbar -T beagle-ram.ld -lbaz bar.o
This is different. There are things in the command line which would
a) add symbols into the output
This is generic functionality which is needed by all the platforms.
The symbols could be parsed and handed over to ELF Writer to add
symbols, because types of symbols on what to add sho...