-
- Downloads
Bug 1725125 - Make a hybrid build system combining non-unified with unified. CLOSED TREE
By hybrid unified system we understand a system that encapsulates modules that are built in the unified mode but also other modules, like `dom/Animation`, as an example, in the non unified environment. This approach is desirable since we already have most of the modules transitioned to the non unified system but there are still some that are not yet compatible, but in the long term this will be done by each module owner and can be also tested locally using the build system. If a module can't be built outside the unified method it's `moz.build` config file needs to have `REQUIRES_UNIFIED_BUILD = False` To also enable this we need to have a flag from `mozconfig`, like: ``` ac_add_options --disable-unified-build ``` Differential Revision: https://phabricator.services.mozilla.com/D122328
Showing
- browser/config/mozconfigs/linux64/hybrid 4 additions, 0 deletionsbrowser/config/mozconfigs/linux64/hybrid
- browser/config/mozconfigs/macosx64/hybrid 4 additions, 0 deletionsbrowser/config/mozconfigs/macosx64/hybrid
- browser/config/mozconfigs/win64/hybrid 4 additions, 0 deletionsbrowser/config/mozconfigs/win64/hybrid
- build/docs/unified-builds.rst 16 additions, 0 deletionsbuild/docs/unified-builds.rst
- moz.configure 11 additions, 0 deletionsmoz.configure
- python/mozbuild/mozbuild/frontend/emitter.py 9 additions, 1 deletionpython/mozbuild/mozbuild/frontend/emitter.py
- taskcluster/ci/build/linux.yml 42 additions, 0 deletionstaskcluster/ci/build/linux.yml
- taskcluster/ci/build/macosx.yml 29 additions, 0 deletionstaskcluster/ci/build/macosx.yml
- taskcluster/ci/build/windows.yml 52 additions, 0 deletionstaskcluster/ci/build/windows.yml
Loading
Please register or sign in to comment