Testing Pritam's Linux build
There has been a lot of interest in the Brackets Community around getting Brackets running on Linux. The Linux Version thread in the brackets-dev forum got so large and hard to follow that I created this wiki page to summarize the info so far, and also as a collecting point for more info. The following info was copied from the post by Pritam Baral for his Linux build.
With reasonable confidence I can say Brackets for Linux is ready for testing. Two builds (32 and 64 bit respectively) have been posted: pritambaral/brackets-shell/downloads. The core brackets code from Sprint 16 has also been packaged and posted on the same page. A tester may chose to build it for himself, or download the brackets-shell-[64,32] and brackets-sprint-16 builds and run it.
Both brackets-shell and brackets are packaged up as brackets-shell-[32,64]-bit.tar.bz2 and brackets-sprint-16.tar.bz2 respectively on the downloads page. Download both and extract to the proper directory. The folders www/ and samples/ being in the same folder as the Brackets binary is preferable, but you extract anywhere and manually choose the location of www/index.html on start-up.
[Note from Randy Edmunds: it wouldn't work for me on OpenSuse 12.1 when I put these folders side-by-side, but it did work when I put the www/ and samples/ being in the same folder as the Brackets executable. Opened issue #4.]
Or, if you want to test the building process, the linux branches on both pritambaral/brackets and pritambaral/brackets-shell are the ones to use.
Instructions on how to build Brackets for Linux are provided
We want to get an idea of how complete and stable this build is. Note that this is a Sprint 16 Build, so, if you have access to a Mac 10.6+ or Windows XP+ system, compare behavior against Sprint 16 Installer build (download).
Open Brackets Unit Tests window using: Debug > Run Tests. Note that Unit Tests are disabled if you use the www folder download. Run all Unit and Extension tests.
Also run Brackets Smoke Tests for both Client and Server, if possible.
To help us get an idea of what testing has been done, please update this table after you have completed some testing:
| Contact info | OS/version | Unit Tests pass? | Smoke tests pass? | Comments |
|---|---|---|---|---|
| Randy Edmunds, github.com/redmunds | OpenSUSE 12.1 | Partial success {2} | In progress... | |
| Pablo Botta, github.com/p4bl1t0 | LMDE Up to date | Unable to run it {1} | In progress | Using Pritam's 32 bits builds "Show Extension Folder" - Don't open extension folder |
| Ryan Stewart | Ubuntu 11.10 | Runs with a few issues. | ||
| Pedro Mendes, @pmgmendes | Linux Mint 14, 64 bit, Cinnamon 1.6.7 | Unable to run it. Same as {1} | Didn't run | Using Pritam's 64 bits builds, "Show Extension Folder" doesn't open the extension's folder |
| Eric Dykstra | Debian Squeeze 6.0.1, 64 bit, Gnome 2.30.2 | Unable to run. {3} | Unable to run. {3} | Using Pritam's 64 bit build. |
{1} I have copied test folder to the executable's folder and that enabled "Run Tests". But when I click on it and go to the test window nothing happened there. The tests don't run. Maybe I'm missing something. [Randy: see {2}]
{2} I opened issue #4 about enabling Unit Test window. See note at bottom about a way to hack around it for now.
{3} My development servers are remote and I mount via SSHFS to see them locally. This works fine for other editors. However, I am unable to open SSHFS folders using Brackets.
Use pritambaral/brackets/issues for logging issues.
Grab issues from pritambaral/brackets/issues.