Build artifacts/ARCHV/TARGET instead of artifacts/ARCHV/T.#45
Conversation
Signed-off-by: Bryan Bayerdorffer <bryanb@qti.qualcomm.com>
|
We can close #43 if we merge this. |
|
Is there even T any more? Can we get rid of it if it's confusing? |
Yeah, there's T. we might be able to get rid of it, but right now it selects which of the opt: or ref: targets from the top-level makefiles get built (with the particular parameters of the given target). Removing T means either sucking those huge stanzas into the TARGET, er, targets (admittedly most of that stuff could go into a separate target that depends on the TARGET) and refactoring so that we don't have {opt|ref}_install in the kernel makefile and so on. We'd have to pass those makefiles a flag that says which of opt or ref to build...kind of like $(T)... |
Now that I think about it, it's really the top-level opt: and ref: targets that get in the way of sanity here. We should just pass $(T) to all the submakes -- it's actually already exported. I think we want 'make opt' and 'makeTARGET=opt' to do the same thing, and right now they don't necessarily have to. I'll try it out and make a new PR. |
No description provided.