41
edits
WebExtensions/Contribution Onramp: Difference between revisions
Jump to navigation
Jump to search
WebExtensions/Contribution Onramp (view source)
Revision as of 09:34, 23 October 2020
, 23 October 2020→Setting Up Developer Environment: add link to firefox-sources setup doc page and updated MDN links that have been moved to firefox-sources docs
(--log-mach-verbose is not really documented anywhere (https://bugzilla.mozilla.org/show_bug.cgi?id=1656513 ). Add it here, along with other tips for testing.) |
(→Setting Up Developer Environment: add link to firefox-sources setup doc page and updated MDN links that have been moved to firefox-sources docs) |
||
| Line 15: | Line 15: | ||
* Run unit tests to verify that your environment works as expected, preferably tests related to the bug that you want to work on. | * Run unit tests to verify that your environment works as expected, preferably tests related to the bug that you want to work on. | ||
== Setting Up Developer Environment == | == Setting Up Developer Environment == | ||
'''For a detailed overview, see [https://firefox-source-docs.mozilla.org/setup/index.html Getting Set Up To Work On The Firefox Codebase]'''. | |||
In short: | |||
* Now, you need to set up your development environment by [https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html#clone-the-sources cloning the source] with mercurial or [https://github.com/glandium/git-cinnabar/wiki/Mozilla:-A-git-workflow-for-Gecko-development with Git]. | * Now, you need to set up your development environment by [https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html#clone-the-sources cloning the source] with mercurial or [https://github.com/glandium/git-cinnabar/wiki/Mozilla:-A-git-workflow-for-Gecko-development with Git]. | ||
* Then you need to install dependencies with <code>mach bootstrap</code> for building Firefox. There are two ways to do this: | * Then you need to install dependencies with <code>mach bootstrap</code> for building Firefox. There are two ways to do this: | ||
** [recommended] Build Firefox using [https:// | ** [recommended] Build Firefox using [https://firefox-source-docs.mozilla.org/contributing/build/artifact_builds.html Firefox Artifact builds]. If the issue only requires changes to privileged JavaScript code, we recommend you use this method. Artifact builds saves time because it downloads a pre-built version of Firefox sources and applies your local changes on it, instead of rebuilding all of the C++ and Rust pieces from scratch. | ||
*** To build Firefox for Android, see the [https://firefox-source-docs.mozilla.org/mobile/android/geckoview/contributor/geckoview-quick-start.html GeckoView Contributor guide]. For a faster local development experience, we recommend to use the Artifact builds and the Android x86 target (which is especially useful to run the tests locally). | *** To build Firefox for Android, see the [https://firefox-source-docs.mozilla.org/mobile/android/geckoview/contributor/geckoview-quick-start.html GeckoView Contributor guide]. For a faster local development experience, we recommend to use the Artifact builds and the Android x86 target (which is especially useful to run the tests locally). | ||
** [default] Build Firefox from scratch, by running <code>mach build</code> without [https:// | ** [default] Build Firefox from scratch, by running <code>mach build</code> without [https://firefox-source-docs.mozilla.org/setup/configuring_build_options.html .mozconfig]. Note: doing this can take some time. | ||
* Next, use [https://searchfox.org Searchfox] to find the code associated with your bug. | * Next, use [https://searchfox.org Searchfox] to find the code associated with your bug. | ||