Template:Paths

"Command not found" errors
If the  or   binary file is installed on your computer, but you see a " " type of error when entering your command into the terminal, the problem may be that the   directory (or whichever directory contains the binary) is not in the "path of execution" for your terminal session. This means that your computer doesn't know where exactly the binary is located.

The solution to this is to add the directory containing the binary to your PATH.

Linux/OS X
On most Linux/OS X systems using the Bourne Again Shell (bash), you can do the following:


 * 1) Edit the "hidden" (starting with a period) file   -- If your version of Linux supports the   editor, simply type
 * 2) Next, add this line to the bottom:     (Change to the actual path to the SDK's   directory. For example:   )
 * 3) Save the file. Then open a new Terminal. The   command should now be available.

Windows
On Windows systems you can do the following:
 * 1) Righ-click on My Computer and select Properties.
 * 2) Choose Advanced, and click on the Environment Variables button.
 * 3) Navigate to System Variables and double click on Path to edit.
 * 4) Enter the full path to your tools folder.