Skip to content

Latest commit

 

History

History
73 lines (55 loc) · 2.71 KB

linux.md

File metadata and controls

73 lines (55 loc) · 2.71 KB
Raw

Linux

Ubuntu LTS 12.04 64-bit is the recommended platform.

Requirements

  • OS with 64-bit or 32-bit architecture
  • C++ toolchain
    • on Ubuntu/Debian: sudo apt-get install build-essential
    • on Fedora: sudo yum --assumeyes install make gcc gcc-c++ glibc-devel
  • node.js v0.10.x
  • npm v1.4.x
    • npm comes with node.js so no explicit installation is needed here.
    • You can check npm 1.4 or above is installed by running npm -v.
  • libgnome-keyring-dev
    • on Ubuntu/Debian: sudo apt-get install libgnome-keyring-dev
    • on Fedora: sudo yum --assumeyes install libgnome-keyring-devel
    • on other distributions refer to the manual on how to install packages
  • npm config set python /usr/bin/python2 -g to ensure that gyp uses Python 2
    • This command may require sudo depending on how you have configured npm.
  • Git
    • on Ubuntu/Debian: sudo apt-get install git
    • on Fedora: sudo yum install git-core

Instructions

git clone https://github.com/atom/atom
cd atom
script/build # Creates application at $TMPDIR/atom-build/Atom
sudo script/grunt install # Installs command to /usr/local/bin/atom
script/grunt mkdeb # Generates a .deb package at $TMPDIR/atom-build

Troubleshooting

Exception: "TypeError: Unable to watch path"

If you get following error with a big traceback right after Atom starts:

TypeError: Unable to watch path

you have to increase number of watched files by inotify. For testing if this is the reason for this error you can issue

sudo sysctl fs.inotify.max_user_watches=32768

and restart Atom. If Atom now works fine, you can make this setting permanent:

echo 32768 > /proc/sys/fs/inotify/max_user_watches

See also atom#2082.

/usr/bin/env: node: No such file or directory

If you get this notice when attempting to script/build, you either do not have nodejs installed, or node isn't identified as nodejs on your machine. If it's the latter, entering sudo ln -s /usr/bin/nodejs /usr/bin/node into your terminal may fix the issue.

Linux build error reports in atom/atom

  • Use this search to get a list of reports about build errors on Linux.