Closed
Bug 940603
Opened 12 years ago
Closed 11 years ago
Remove gaia build flags
Categories
(Firefox OS Graveyard :: Gaia, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: kgrandon, Unassigned)
Details
Right now we have too many build flags in gaia. Here's how I think this should be:
Device - Developers just run 'make'
B2G desktop, Simulator, GaiaFox - Developers just run 'DESKTOP=1 make'
This means removing/combining the following shims: DEBUG, DESKTOP_SHIMS, SIMULATOR.
Our extensions should be flexible enough to work anywhere, and this may mean moving some stuff into the platform.
Comment 1•12 years ago
|
||
Yey!
Though I would argue that the makefile should not have even one flag... if we need flags we are not really using a makefile as a makefile anymore. (bin/* all the things)
Comment 2•12 years ago
|
||
++
Is there a way we can make the flags transparent, ie:
`make desktop` rather than `DESKTOP=1 make`? I know we'd need to move some things around in the makefile, but having a target rather than flag has a lot of benefits, like tab completion, makefile readability, easy typing, etc.
Perhaps this is what lightsofapollo is asking for?
| Reporter | ||
Comment 3•12 years ago
|
||
Yes, it sounds like moving to targets instead of flags is a much better approach. In that case I think the ideal situation is something like:
$ make - (Default command) builds a profile for the device.
$ make desktop - Builds a profile for b2g desktop OR Firefox Nightly OR Simulator.
By knowing what the targets are, we know that we can never break those targets in any situation.
| Reporter | ||
Updated•12 years ago
|
Summary: Reduce gaia build flags → Remove gaia build flags
Comment 4•12 years ago
|
||
I don't think we can support Firefox desktop and b2g desktop/simulator with the same flag,
that's so differents...
But I agree on the fact that we should have flags (no matter which kind, env variable or targets, I don't see much differences) that would easily ensure that we are building a profile that will work for the targeted environment.
I recently added SIMULATOR=1 to easily ensure that the profile will work in the simulator.
Keep in mind, that we are working on simplifying desktop environments to only one.
https://groups.google.com/forum/#!topic/mozilla.dev.developer-tools/9Q7Gnrpe740
That's the main goal we should be targetting, it will allow to have only one unique kind of profile/shims/helpers for local development.
We are actively working on bug 935014 which aims to first merge the simulator and b2g desktop.
We will then have to figure out how to merge the new simulator/b2g-desktop with the firefox environment.
Comment 5•12 years ago
|
||
Please also keep supporting eng and user (aka production) profiles both for device and desktop.
| Reporter | ||
Comment 6•11 years ago
|
||
Bug 1112745 will remove the majority of these flags, so this is no longer needed.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•