[Buildroot] [PATCH] toolchain: add user defined target LDFLAGS options

[Peter Korsgaard <jacmet@uclibc.org>]

>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:

 >> Ah, that's something I hadn't considered. Thanks for the feedback. I was
 >> assuming one could pass something like "-fee -fi -fo -fum" in the text
 >> block, and this would be passed on to the wrapper.

 Baruch> Well, this string will be passed to the wrapper, but the whole
 Baruch> string will get stored in the same args[] entry. This means
 Baruch> that the compiler sees it as one long argument, not one
 Baruch> argument per word as should be.

 Baruch> A possible solution might be to split this string with strtok()
 Baruch> at run-time, but it looks inefficient, since we have all the
 Baruch> information we need at compile time.

I think it would be simpler to generate an include file containing

"arg1", "arg2", ... "argn"

instead and then simply #include that from ext-toolchain-wrapper.c
instead of passing all these options on the compiler cmdline.

This list could be created with something like:

$(patsubst %,\"%\"$(comma),$(CFLAGS))

-- 
Bye, Peter Korsgaard