mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions 1

docs: Move the "Packaging Tools" out of "Rebranding" chapter

Browse source
This commit is contained in:
Cheng Zhao 2016-05-30 10:37:02 +09:00
parent a176aaee01
commit 7ec467e337
1 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/tutorial/application-distribution.md
View file

@ -102,6 +102,14 @@ MyApp.app/Contents
You can rename the `electron` executable to any name you like. You can rename the `electron` executable to any name you like.
## Packaging Tools
Apart from packaging your app manually, you can also choose to use third party
packaging tools to do the work for you:
* [electron-packager](https://github.com/maxogden/electron-packager)
* [electron-builder](https://github.com/loopline-systems/electron-builder)
## Rebranding by Rebuilding Electron from Source ## Rebranding by Rebuilding Electron from Source
It is also possible to rebrand Electron by changing the product name and It is also possible to rebrand Electron by changing the product name and
@ -118,14 +126,6 @@ This task will automatically handle editing the `.gyp` file, building from
source, then rebuilding your app's native Node modules to match the new source, then rebuilding your app's native Node modules to match the new
executable name. executable name.
## Packaging Tools
Apart from packaging your app manually, you can also choose to use third party
packaging tools to do the work for you:
* [electron-packager](https://github.com/maxogden/electron-packager)
* [electron-builder](https://github.com/loopline-systems/electron-builder)
### Creating a Custom Electron Fork ### Creating a Custom Electron Fork
Creating a custom fork of Electron is almost certainly not something you will Creating a custom fork of Electron is almost certainly not something you will