-
Notifications
You must be signed in to change notification settings - Fork 0
Building Brackets Shell
Linux Users Only These setup steps (from developer dependencies to Git setup) are automated via a one-line wget. See details in the Linux section below.
Windows XP Users Only The grunt scripts used by Brackets do not work with paths that have spaces. When building on Windows XP, it is important to clone to a folder that doesn't have spaces. The default used by GitHub, the GitHub Shell, etc... is C:\Documents and Settings\<username>\My Documents\GitHub Using this folder will cause some commands to fail during the grunt setup process.
An issue has been filed for this (https://github.com/adobe/brackets/issues/7181).
In the interim, to build on Windows XP, Create a folder to clone to in the root directory C:\GitHub\ so that there are no spaces for the build to choke on.
- Node.js
- Additional requirements are listed below for Mac and Windows
- Clone both brackets-shell and brackets repositories as siblings in the same directory. By default, Grunt tasks in both projects make this assumption.
From the brackets-shell directory, run the following set of commands to install package dependencies and Grunt
npm install -g grunt-cli
npm install
grunt setup
Running grunt --help lists all the available tasks. Those tasks are listed below:
full-build Alias for "git", "create-project", "build",
"build-branch", "build-num", "build-sha", "stage",
"package" tasks.
installer Alias for "full-build", "build-installer" tasks. (requires additional setup steps)
build Build shell executable. Run 'grunt full-build' to update
repositories, build the shell and package www files.
build-mac Build mac shell
build-win Build windows shell
git Pull specified repo branch from origin *
build-branch Write www repo branch to config property
build.build-branch
build-num Compute www repo build number and set config property
build.build-number
build-sha Write www repo SHA to config property build.build-sha
stage Stage release files
stage-mac Stage mac executable files
stage-win Stage win executable files
package Package www files
write-config Update version data in www config.json payload
build-installer Build installer
build-installer-mac Build mac installer (requires additional setup steps)
build-installer-win Build windows installer (requires additional setup steps)
set-sprint Update occurrences of sprint number for all native
installers and binaries
cef Download and setup CEF
cef-clean Removes CEF binaries and linked folders
cef-download Download CEF, see curl-dir config in Gruntfile.js
cef-extract Extract CEF zip
cef-symlinks Create symlinks for CEF
node Download Node.js binaries and setup dependencies
node-win Setup Node.js for Windows
node-mac Setup Node.js for Mac OSX and extract
node-clean Removes Node.js binaries
create-project Create Xcode/VisualStudio project
setup Alias for "cef", "node", "create-project" tasks.
jshint Validate files with JSHint. *
copy Copy files. *
clean Clean files and folders. *
curl Download files from the internet via grunt. *
curl-dir Download collections of files from the internet via
grunt. *
default Alias for "setup", "build" tasks.
Building the installer - as opposed to just the locally-executable binary - requires additional setup not covered here. See Brackets Installer for details.
##Mac
####Prerequisites
- Git command line tools
- Python (should be installed by default--enter
python --versionin a Terminal window to verify) - Xcode 4 required to build the project
- In newer versions of Xcode, you might also need to install the "Command Line Tools" in Xcode from Preferences > Downloads and then select Xcode in the "Command Line Tools" drop-down in Preferences > Locations.
- Running
xcode-select --installin a Terminal window will install the required "Command Line Tools" without starting XCode
####Setup
Open a Terminal window at the brackets-shell directory and run grunt. This will download the CEF and Node.js binaries (if needed), create symlinks for the CEF and Node.js directories, create the XCode project, then run a command line build.
You will need to run grunt setup later if new source files are added or if brackets-shell updates to a newer CEF build.
####Building in XCode Open appshell.xcodeproj in XCode and build the "Brackets" target.
####Building from the command line
Open a Terminal window at the brackets-shell directory and run grunt build.
####Running
The build output is located at xcodebuild/Release/Brackets.app (release build) or xcodebuild/Debug/Brackets.app (debug build).
When you launch this app, you will be prompted to select index.html (the main file for the Brackets HTML/JS/CSS source code). Navigate to your local copy of the brackets repo and select src/index.html. To avoid having to do this every time you launch, go to the brackets repo and run the tools/setup_for_hacking.sh script. This will add a symlink pointing from the compiled Brackets.app to the index.html file. The parameter to setup_for_hacking is the full path to Brackets.app.
##Windows
####Prerequisites
Windows XP Users must download the Junction tool from Microsoft (http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx); Once the download has completed, open the zip file and copy junction.exe to c:\windows\system32 then run it once by double clicking it in Windows Explorer or typing junction from a command prompt. This is just to get the license acceptance dialog out of the way before building brackets.
- Visual Studio 2010 (preferred) or 2012 are required to build the project. The free Visual Studio Express works fine.
- Note that if you're using VS 2010 or VS Express, you might need to install Visual Studio 2010 SP1 to avoid link errors.
- Windows Vista or later (although brackets-shell runs on Windows XP, you cannot build it on XP)
- GitBash (I used Git-1.8.0-preview20121022.exe)
- Python 2.7 (Use the Windows X86 MSI or Windows X86-64 MSI)
Add Python to your path. The default python 2.7 install directory is C:\Python27.
####Verify Prerequisites
- Start GitBash with Run as Administrator
- Enter
python --version. You should see "Python 2.7.3". - Enter
echo $VS100COMNTOOLS. You should see something like ""C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools"
####Setup
Open a GitBash shell and navigate to the brackets-shell directory. Run grunt. This will download the CEF binary (if needed), create symlinks for the CEF directories, create the Visual Studio solution file, then run a command line build.
You will need to re-run grunt setup later if new source files are added or if brackets-shell updates to a newer CEF build.
####Building in Visual Studio. Open appshell.sln in Visual Studio. NOTE: If you are using Visual Studio Express, you may get warnings that say some of the projects couldn't be loaded. These can be ignored. Build the "Brackets" target.
####Building from the command line
Open a GitBash window at the brackets-shell directory and run grunt build.
####Running
The build output is located at Release\Brackets.exe (release build) or Debug\Brackets.exe (debug build).
When you launch this executable, you will be prompted to select an index.html file (the main file for the Brackets HTML/JS/CSS source code). Navigate to your local copy of the brackets repo and select src\index.html. To avoid having to do this every time you launch, go to the brackets repo and run tools\setup_for_hacking.bat. This will add a symlink pointing from the output folder to the index.html file. The parameter to setup_for_hacking is the full path to the folder containing Brackets.exe.
####Troubleshooting If grunt fails you may need to reset
git reset #HEAD
git checkout .
Make sure to run gitbash as administrator. Otherwise the symlinks/junctions for CEF directories will be missing after grunt setup.
##Linux
Currently, the core Brackets team only supports Debian/Ubuntu as a development environment and for our binary packages. We would like to support more distributions in the future, but we've already seen other open source contributors take Brackets to Arch Linux. For more information on the current development status, visit the Linux wiki page.
In Sprint 28, we release a Preview build for Linux (Debian/Ubuntu only). We're very close to parity with Mac and Windows. See the Linux wiki page for more details.
####Prerequisites
There are 2 options for installing prerequisites: (1) a one-line wget to setup the Git repositories and install depenencies or (2) setup Git separately and install dependencies on your own.
# One-line setup (recommended)
wget https://gist.github.com/jasonsanjose/5514813/raw/6215f3b73ff41f51e20bc94a9faa3e453402ce06/setup.sh; chmod +x setup.sh; bash setup.sh; rm setup.sh
# Manual setup
# install git and dev dependencies
sudo apt-get install --assume-yes git libnss3-1d libnspr4-0d gyp gtk+-2.0
# install node and grunt
sudo apt-get install --assume-yes python-software-properties python g++ make
sudo add-apt-repository ppa:chris-lea/node.js -y
sudo apt-get update --assume-yes
sudo apt-get install --assume-yes nodejs
sudo npm install -g grunt-cli
####Setup
Open a Terminal window at the brackets-shell directory and run grunt. This will download the CEF and Node.js binaries (if needed), create symlinks for the CEF and Node.js directories, create the Makefile, then run a command line build.
You will need to run grunt setup later if new source files are added or if brackets-shell updates to a newer CEF build.
####Building from the command line
Open a Terminal window at the brackets-shell directory and run grunt build or simply make.
####Running
The build output is located at out/Release/Brackets (release build) or out/Debug/Brackets (debug build).
When you launch this app, you will be prompted to select index.html (the main file for the Brackets HTML/JS/CSS source code). Navigate to your local copy of the brackets repo and select src/index.html. To avoid having to do this every time you launch, go to the brackets repo and run the tools/setup_for_hacking.sh script. This will add a symlink pointing from the compiled app to the index.html file. The parameter to setup_for_hacking is the full path to the compiled app.