./docs/setup/linux_build.rst improve instructions
Categories
(Developer Infrastructure :: Firefox Source Docs: Content, enhancement)
Tracking
(Not tracked)
People
(Reporter: reg-1, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/119.0
Steps to reproduce:
Follow intructions on build section
'''
3. Build
cd mozilla-unified
hg up -C central
./mach build
./mach run
'''
Actual results:
-
When you check out package, it would like to ask you if you want to rename the folder path you want to put in, if you name anything, it won't be "mozilla-unified" folder.
-
If you are trying to compile for another computer, "./mach run" won't work, you need "./mach package"
Expected results:
Suggest to following source code changes (the following might not be the best wording, welcome to modify it.
####################################
- Build
Now that your system is bootstrapped, you should be able to build!
.. code-block:: shell
cd /path/to/where-you check-out-source-code
hg up -C central
./mach build
default path is mozilla-unified, but if you renamed it during python3 bootstrap.py, please go to the folder you specific during bootstrap process.
🎉 Congratulations! You've built your own home-grown Firefox!
Now if you want to run your code on your own machine, please run:
.. code-block:: shell
./mach run
If you are compiling this for another machine for the same platform, please run:
.. code-block:: shell
./mach package
The output package should be in /path/to/where-you check-out-source-code/obj-*/dist/ path, named firefox-*.*.tar.bz2
If you want to compile for another machine for another platform, please see cross-compile instructions <https://firefox-source-docs.mozilla.org/build/buildsystem/cross-compile.html> before you run ./mach build
##################
|
||
Comment 1•1 years ago
|
||
Sorry but the rendering of your bug report is making it hard to understand
could you please submit a patch to improve the doc directly?
thanks
Sorry for late reply, I was busy during normal life last week.
Sorry for the confusions I made (my 1st time trying to do this). My main point is trying to point out if people want to compile and make a package for another machine (not directly install on compiling machine), what command they should use.
You said "submit a patch" do you mean I make the change, and use "hg commit" to update it into this bug report? I might could do this during my next break, due to busy daily life.
Thanks for your time!
Description
•