On 30/09/15 10:34, Justin Cormack wrote:
On 30 Sep 2015 11:21 am, "Antti Kantee" <[email protected]> wrote:
On 30/09/15 09:42, Justin Cormack wrote:
Or you could have a rumplinkconfig tool that just output the linker args.
I have trouble imagining how it would be convenient for the users. Can
you produce a working mockup of the build process with such a tool? (i.e.
no need to write the tool, just hardcode the output)
rumpbake myfile $(rumplinkconfig qemu exterminate ext2)
Oh you still planned to keep rumpbake?
I think Krishna's comparison to pkg-config is appropriate, and also
exposes the problem.
pkg-config produces output that cc(1) doesn't know about, nor is the
output required for every execution of cc(1).
Your proposed rumplinkconfig produces output that rumpbake requires for
every single successful link.
As always, we'll follow the "separate normal case and worst case" principle.
