README.MAKEFILE 3.8 KB

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