зеркало из https://github.com/mozilla/gecko-dev.git
1843095b29
The intent is for the build system to soon require Node.js to build Firefox. But we aren't ready to make Node.js a build requirement just yet. The goal of this commit is to implement configure detection for Node.js so that we can a) work out detection bugs b) give people a means to validate system compatibility *before* we throw the switch to require Node.js. This commit introduces configure logic for finding a Node.js executable, resolving its version, and validating its suitability. By default, if Node.js cannot be found or there is an error resolving its version, we print some warning messages and move on. If --enable-nodejs is used (not the default), errors are raised if Node.js cannot be found or its version isn't suitable. Once we require Node.js, the added code can likely be simplified. When writing the code, I went out of my way to make failures as non-fatal as possible. e.g. normally we'd say that failures to run `node --version` would be fatal. I'm purposefully trying to not have this configure check break anyone's environment, even if failure occurs. Again, the goal is to introduce the configure checks first in a non-fatal way such that we can debug failures so the flag day transition is simpler. Differential Revision: https://phabricator.services.mozilla.com/D1818 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| .flake8 | ||
| android-ndk.configure | ||
| checks.configure | ||
| compile-checks.configure | ||
| compilers-util.configure | ||
| flags.configure | ||
| headers.configure | ||
| init.configure | ||
| java.configure | ||
| keyfiles.configure | ||
| memory.configure | ||
| node.configure | ||
| old.configure | ||
| pkg.configure | ||
| rust.configure | ||
| toolchain.configure | ||
| tup.configure | ||
| util.configure | ||
| warnings.configure | ||
| windows.configure | ||