Gaia/Build/NewBuildSystem: Difference between revisions

Jump to navigation Jump to search
Line 12: Line 12:


* '''Deliverable:''' A new Makefile target to trigger configure.js modules should be landed in Gaia code base. The configure.js can generate a Makefile and produce a same PROFILE_DIR as usual.
* '''Deliverable:''' A new Makefile target to trigger configure.js modules should be landed in Gaia code base. The configure.js can generate a Makefile and produce a same PROFILE_DIR as usual.
* '''Expected schedule:''' 4 week
* '''Expected schedule:''' 4 weeks
* '''Breakdowns:'''
* '''Breakdowns:'''
** New config step: adding configure.js to generate strong dependency makefile and execute it.
** New config step: adding configure.js to generate strong dependency makefile and execute it.
** New re-run step: in 2nd make, new build will check the change files and ENV to decide whether to regenerate makefile or not, and then execute it.
** New re-run step: in 2nd make, new build will check the change files and ENV to decide whether to regenerate makefile or not, and then execute it.
** Refactoring webapp-shared.js and copyToStage: based on new build system architecture, we'll refactor webapp-shared module and copyToStage into config and execute task in order to save time when re-run make and check if any possible risk before Milestone 2 (refactoring all build modules and app/build.js) .
** Refactoring webapp-shared.js and copyToStage: based on new build system architecture, we'll refactor webapp-shared module and copyToStage into config and execute task in order to save time when re-run make and check if any possible risk before Milestone 2 (refactoring all build modules and app/build.js).


== Milestone 2 ==
== Milestone 2 ==
Confirmed users
429

edits

Navigation menu