README.MAKEFILE 4.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111
  1. Description of makefile rules
  2. =============================
  3. release
  4. -------
  5. Build Tor Browser for the release channel, for all supported platforms.
  6. The resulting build can be found in directory release/$version.
  7. release-{linux-x86_64,linux-i686,windows-i686,osx-x86_64,android-armv7,
  8. android-x86,android-x86_64,android-aarch64}
  9. -----------------------------------------------------------------------
  10. Same as release, for the selected platform only.
  11. alpha
  12. -----
  13. Build Tor Browser for the alpha channel, for all supported platforms.
  14. The resulting build can be found in directory alpha/$version.
  15. alpha-{linux-x86_64,linux-i686,windows-i686,osx-x86_64,android-armv7,
  16. android-x86,android-x86_64,android-aarch64}
  17. ---------------------------------------------------------------------
  18. Same as alpha, for the selected platform only.
  19. nightly
  20. -------
  21. Build Tor Browser for the nightly channel, for all supported platforms.
  22. Many of the components will be based on the master branch. You might
  23. want to run "make fetch" before, to fetch the latest commits from all
  24. components.
  25. The resulting build can be found in directory nightly/$date
  26. nightly-{linux-x86_64,linux-i686,windows-i686,osx-x86_64,android-armv7,
  27. android-x86,android-x86_64,android-aarch64}
  28. -----------------------------------------------------------------------
  29. Same as nightly, for the selected platform only.
  30. testbuild
  31. ---------
  32. Build a Tor Browser test build. To make the build faster, only the en-US
  33. locale is created, without mar files, and without the source tarballs.
  34. By default it is based on the alpha channel, but you can change that by
  35. editing rbm.local.conf. The resulting build can be found in directory
  36. testbuild.
  37. {release,alpha,nightly,testbuild}-linux-x86_64-debug
  38. ----------------------------------------------------
  39. Create a debug build for Linux x86_64 with debug features such as ASan.
  40. {release,alpha,nightly,testbuild}-src
  41. -------------------------------------
  42. Create source tarballs for firefox, torbutton and tor-launcher.
  43. fetch
  44. -----
  45. Fetch new commits from all components. This is useful when you want to
  46. build the nightly channel.
  47. clean
  48. -----
  49. Clean files created during previous builds that are no longer used in
  50. current builds. Before using this command, you first need to configure
  51. in rbm.local.conf the channel(s) that you are building.
  52. In other software, the clean rule is used to remove all build files,
  53. but this is not the case here, where only obsolete build files are
  54. removed. It is usually not necessary to remove all build files before
  55. starting a new build as the need for rebuilding components is detected
  56. automatically. If you want to remove all build files, you can remove
  57. the out/ directory.
  58. clean-dry-run
  59. -------------
  60. Print the files that would be removed when running 'make clean'.
  61. signtag-{release,alpha}
  62. -----------------------
  63. Create a git signed tag for the selected channel, using the version and
  64. build number defined as var/torbrowser_version and var/torbrowser_build.
  65. incrementals-{release,alpha}
  66. ----------------------------
  67. Create incremental mar files for an unsigned build in the release or
  68. alpha channel. The list of versions we create incrementals from is
  69. defined as var/torbrowser_incremental_from in rbm.conf.
  70. incrementals-nightly
  71. --------------------
  72. Create incremental mar files for the current nightly build. The number
  73. of previous versions we should generate incremental mars from is defined
  74. as var/max_torbrowser_incremental_from in rbm.conf.
  75. If you want to create incremental mars for a version that is not the
  76. current one, you can define the environment variable
  77. TORBROWSER_NIGHTLY_VERSION to the version you want to generate
  78. incremental mars for.
  79. dmg2mar-{release,alpha)
  80. -----------------------
  81. Generate updated mar files for the OSX bundles, from the dmg files, then
  82. regenerate the OSX incremental mar files. You should run this after
  83. signing the OSX dmg files.
  84. update_responses-{release,alpha}
  85. --------------------------------
  86. Create update responses xml files for a signed build in the release or
  87. alpha channel. The files can be found in a tar in the directory
  88. {release,alpha}/update-responses.