mozilla
/
gecko-dev
зеркало из https://github.com/mozilla/gecko-dev.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
gecko-dev/build/mozconfig.no-compile

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

33 строки
625 B
Plaintext
Исходник Обычный вид История

Bug 1373150 - Disable compile environment on l10n builds. r=Callek --HG-- extra : rebase_source : d28920594023bfdd956d0bbdf385e8d1fafb0656
2017-06-15 09:06:45 +03:00
ac_add_options --disable-compile-environment
Bug 1382502 - Include mozconfig.cache in most cases. r=ted We want most builds to be actually using sccache, so we include mozconfig.cache from mozconfig.common. However, since the --with-ccache configure option doesn't exist on non-compile jobs (e.g. artifact builds), we move to using the CCACHE environment variable instead, which allows us to unset it in mozconfig.no-compile. And since mozconfig.no-compile is always included where no_sccache is set, we can remove that variable. --HG-- extra : rebase_source : a8c743de1fd7a3c0fbc53f7c233df36585897767
2017-07-20 05:07:53 +03:00
# In case mozconfig.cache was already included
unset CCACHE
Bug 1384786 - Fix try artifact builds after bug 1382502. r=gps --HG-- extra : rebase_source : e5a79afdb0d7b060ed50a17b2650b5d20babb854
2017-07-27 08:02:39 +03:00
unset SCCACHE_VERBOSE_STATS
Bug 1382502 - Include mozconfig.cache in most cases. r=ted We want most builds to be actually using sccache, so we include mozconfig.cache from mozconfig.common. However, since the --with-ccache configure option doesn't exist on non-compile jobs (e.g. artifact builds), we move to using the CCACHE environment variable instead, which allows us to unset it in mozconfig.no-compile. And since mozconfig.no-compile is always included where no_sccache is set, we can remove that variable. --HG-- extra : rebase_source : a8c743de1fd7a3c0fbc53f7c233df36585897767
2017-07-20 05:07:53 +03:00
# In case it wasn't
NO_CACHE=1
Bug 1373150 - Disable compile environment on l10n builds. r=Callek --HG-- extra : rebase_source : d28920594023bfdd956d0bbdf385e8d1fafb0656
2017-06-15 09:06:45 +03:00
# Override any toolchain defines we've inherited from other mozconfigs.
unset CC
unset CXX
unset HOST_CC
unset HOST_CXX
Bug 1464161 - unset LINKER in mozconfig.no-compile. r=nalexander --HG-- extra : rebase_source : 75913c32de26e0aa4f7bbcf79f29ad5d7f5fcb32
2018-05-29 22:37:49 +03:00
unset LINKER
Bug 1373150 - Disable compile environment on l10n builds. r=Callek --HG-- extra : rebase_source : d28920594023bfdd956d0bbdf385e8d1fafb0656
2017-06-15 09:06:45 +03:00
unset RUSTC
unset CARGO
Bug 1457524 followup - Unset RUSTDOC for no-compile environment and add it to mozconfigs. --HG-- extra : rebase_source : 811e48c193f593332ace7ed0108693373dafecaf extra : amend_source : 4bb21acd6d3def08917dc00c2264f1ddb1b1ede8
2018-05-05 04:04:07 +03:00
unset RUSTDOC
Bug 1471486 part 1 - Detect rustfmt like other rust executables. r=froydnj MozReview-Commit-ID: 8LMdpdqbrFS --HG-- extra : rebase_source : e23b7e467993963eb1a69637dacdabb7cbff3e90
2018-06-27 08:27:43 +03:00
unset RUSTFMT
Bug 1478813 - Auto-generate ServoStyleConsts. r=xidorn,ted Differential Revision: https://phabricator.services.mozilla.com/D2447
2018-08-17 19:43:06 +03:00
unset CBINDGEN
Bug 1373150 - Disable compile environment on l10n builds. r=Callek --HG-- extra : rebase_source : d28920594023bfdd956d0bbdf385e8d1fafb0656
2017-06-15 09:06:45 +03:00
unset MAKECAB
unset TOOLCHAIN_PREFIX
Bug 1380130 - Unset BINDGEN_CFLAGS during artifact builds on try. r=rillian MozReview-Commit-ID: ErfrmJMV1EQ --HG-- extra : rebase_source : 289ce1237e8af0bebfd886ff388aa6a10f4b9254
2017-07-11 23:39:08 +03:00
unset BINDGEN_CFLAGS
Bug 1382525 - Move LLVM_CONFIG out of mozconfig.common. r=chmanchester LLVM_CONFIG, per the contents of toolkit/moz.configure, is tied to --enable-stylo, but it currently is set on all types of builds. It currently happens to work, but it's actually not meant to, and sure enough, the fix for bug 1374727 exacerbates that. So we create a new mozconfig.stylo file that enables stylo and sets LLVM_CONFIG, such that only build types that do enable stylo have LLVM_CONFIG set. --HG-- extra : rebase_source : 01277a79951888046c0b8e29c61cfc3b049ee0f0
2017-07-20 08:06:23 +03:00
unset LLVM_CONFIG
Bug 1481721 - Switch Linux nightlies and PGO builds to clang r=froydnj And enable LTO on CI builds using clang + PGO. Differential Revision: https://phabricator.services.mozilla.com/D4991 --HG-- extra : moz-landing-system : lando
2018-09-12 01:52:29 +03:00
unset LLVM_PROFDATA
Bug 1429947 - Unset WIN64_LINK and WIN64_LIB in in-tree mozconfigs during an artifact build. r=nalexander MozReview-Commit-ID: 9mIaxs0xroN --HG-- extra : rebase_source : 623f50f4186722d6a0da9f01bd6d57b072068bd7
2018-01-27 01:53:44 +03:00
unset WIN64_LINK
unset WIN64_LIB
Bug 1486654 - Enable static analysis on all Linux CI builds. r=ted And turn off separate static analysis build tasks.
2018-08-24 16:16:28 +03:00
unset ENABLE_CLANG_PLUGIN
Bug 1515604 - Fix artifact builds after bug 1513798. r=nalexander Differential Revision: https://phabricator.services.mozilla.com/D15079 --HG-- extra : moz-landing-system : lando
2018-12-20 21:50:04 +03:00
unset MACOS_SDK_DIR
unset MACOS_PRIVATE_FRAMEWORKS_DIR
Bug 1426555 - Move --enable-stdcxx-compat to python configure. r=chmanchester At the same time, we make it actually do something on spidermonkey builds. We also add an environment variable alternative, that we use in mozconfig.stdcxx, allowing for mozconfig.no-compile to override it and avoid configure failures on e.g. artifact builds. --HG-- extra : rebase_source : b68d362025e0c99f9184a03391c652ec2c9357ad
2017-12-21 05:13:08 +03:00
unset MOZ_STDCXX_COMPAT
Bug 1079662 - Always enable PIE. r=froydnj Last attempt, a few years ago, blatantly failed because nautilus (the GNOME file manager) can't start PIE executables, which look like shared libraries, and that it thus considers not being executables. Downstreams don't actually have the problem, because users won't be launching Firefox from a file manager, but for mozilla.org builds, it is a problem because users would download, then extract, and then likely try to run the Firefox executable from a file manager. So for mozilla.org builds, we still need to find a way around the nautilus problem. A .desktop file could be a solution, but .desktop files have not actually been designed for this use case, which leads to: - having to use an awful one-liner shell wrapper to derive the path to the executable from that of the .desktop file, - not even being able to associate an icon, - the .desktop file not being copiable to a location where .desktop files would normally go, because it would then fail to find the executable. Another possibility is to go back to using a shell wrapper, but that's not entirely appealing. What we chose here is similar, where we have a small `firefox` wrapper that launches the real `firefox-bin` (which is still leftover from those old times where we had a shell wrapper, for reasons). The small `firefox` wrapper is a minimalist C executable that just finds the path to the `firefox-bin` executable and executes it with the same args it was called with. The wrapper is only enabled when the MOZ_NO_PIE_COMPAT environment variable is set, which we only take into account on Linux. The variable is only really meant to be used for mozilla.org builds, for the nautilus problem. Downstreams will just pick the default, which is changed to build PIE. On other platforms, PIE was already enabled by default, so we just remove the --enable-pie configure flag. Differential Revision: https://phabricator.services.mozilla.com/D5109
2018-09-06 07:27:49 +03:00
unset MOZ_NO_PIE_COMPAT