Open Bug 1164937 Opened 5 years ago Updated 2 years ago

Move much of package-name.mk to python and use it to generate test archive dependencies

Categories

(Firefox Build System :: General, defect)

defect
Not set

Tracking

(Not tracked)

People

(Reporter: chmanchester, Unassigned)

References

(Depends on 1 open bug)

Details

The manifest of test archives we're generating in bug 917999 would be appropriate to write out during backend generation, but from there we don't really have access to the parts of package-name.mk we're using. The proposal there is to move package-name.mk to python for this purpose.
I was thinking something like (in moz.build):

BACKEND_VARIABLES['MOZ_PKG_PLATFORM'] = '{TARGET_OS}-{TARGET_CPU}'.format(CONFIG)

...and then having that write out a .mk file in the objdir that we could include instead of package-name.mk, and also exposing it in the Emitter data in a way that we could use it to generate the test package manifest.

The only thing I got a little hung up on was I couldn't tell how we deal with the "pretty names" stuff nowadays--it doesn't seem to get set in mozconfigs, and I can't tell if we have builds that try to build both pretty and non-pretty named package bits. If so that makes it harder. If nothing actually needs that then we can just stick a pretty names thing in mozconfigs and it's all fairly straightforward.
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.