PageRenderTime 26ms CodeModel.GetById 22ms RepoModel.GetById 0ms app.codeStats 0ms

/README.md

https://gitlab.com/Smileyt/KomodoEdit
Markdown | 275 lines | 177 code | 98 blank | 0 comment | 0 complexity | 6b6d861f441449f5050512478f8ba2f6 MD5 | raw file
  1. # Komodo Edit
  2. This readme explains how to get started building, using and developing with
  3. the Komodo Edit source base.
  4. Whilst the main Komodo Edit source is hosted under this repository you may also
  5. want to check out the individual component/addon repositories under
  6. https://github.com/Komodo in case you only want to contribute to a specific
  7. component. This'll save you some time and hassle as you would not have to build
  8. the entire project.
  9. ## Table of Contents
  10. - [Screenshot](#screenshot)
  11. - [Download](#download)
  12. - [Feedback](#feedback)
  13. - [Building Komodo](#building-komodo)
  14. - [Building on Windows](#building-on-windows)
  15. - [Building on Mac & Linux](#building-on-mac-&-linux)
  16. - [Building with Docker](#building-on-docker)
  17. - [Building Complications](#building-complications)
  18. ## Screenshot
  19. ![Screenshot](screenshot.png)
  20. ## Download
  21. You can [download Komodo Edit here](http://komodoide.com).
  22. ## Feedback
  23. There are several ways to get in contact with the Komodo devs:
  24. Github: <https://github.com/Komodo/KomodoEdit>
  25. Forums: <http://forum.komodoide.com/>
  26. Bug Tracker: <https://github.com/Komodo/KomodoEdit/issues>
  27. IRC: <irc://irc.mozilla.org/#komodo>
  28. Mailing Lists: [komodo-discuss](http://code.activestate.com/lists/komodo-discuss/) & [komodo-beta](http://code.activestate.com/lists/komodo-beta/) & [komodo-announce](http://code.activestate.com/lists/komodo-announce/)
  29. ## Building Komodo
  30. Note that these are simplified steps of the building process, for a more in-depth
  31. guide check <BUILD.txt>.
  32. ### Building on Windows
  33. - [Prerequisites](#prerequisites)
  34. - [Building Steps](#building-steps)
  35. #### Prerequisites
  36. * Python >=2.7 (but not Python 3.x yet). You can [install ActivePython from here](http://downloads.activestate.com/ActivePython/releases).
  37. * Visual C++ 11.0 (aka Visual Studio 2012) and all the Platform SDKs for
  38. building Mozilla with vc11 [as described here](http://developer.mozilla.org/en/docs/Windows_Build_Prerequisites).
  39. * Install [the latest "MozillaBuild-$ver.exe"](http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/) package into *the default dir*
  40. (i.e. "C:\mozilla-build").
  41. * Install the [latest ActivePerl](http://downloads.activestate.com/ActivePerl/releases/).
  42. See <http://developer.mozilla.org/en/docs/Windows_Build_Prerequisites> for
  43. more details on Windows build prerequisites. However, following the above
  44. steps is *meant to be sufficient* to get Komodo building.
  45. #### Building Steps
  46. * Checkout Komodo Edit: `git clone https://github.com/Komodo/KomodoEdit.git`
  47. * Using the command line, enter your checkout directory and run:
  48. ```
  49. cd mozilla
  50. setenv-moz-msvc11.bat
  51. python build.py configure -k 9.10
  52. python build.py distclean all
  53. ```
  54. This will configure and build mozilla and can take anywhere from 30 minutes
  55. to several hours to complete (depending on your specs). For most modern
  56. machines it should be about an hour.
  57. * After mozilla is built successfully go back to the main repo directory and
  58. build komodo:
  59. ```
  60. cd ..
  61. set PATH=util\black;%PATH%
  62. bk configure -V 9.10.0-devel
  63. bk build
  64. ```
  65. This should take significantly less time than building Mozilla.
  66. * Once the build has completed you can simply run Komodo by executing `bk run`
  67. Upon making any modifications to the source you will again have to run `bk build`,
  68. or simply `bk build && bk run` to quickly get back into Komodo. Subsequent builds
  69. should be a lot faster as much of the compiled data is cached.
  70. ### Building on Mac & Linux
  71. - [Mac Prerequisites](#mac-prerequisites)
  72. - [Linux Prerequisites](#linux-prerequisites)
  73. - [Ubuntu](#ubuntu)
  74. - [Fedora](#fedora)
  75. - [Others](#others)
  76. - [Building Steps](#building-steps-1)
  77. #### Mac Prerequisites
  78. * Python >=2.7 (but not Python 3.x yet). You can
  79. [install ActivePython from here](http://downloads.activestate.com/ActivePython/releases).
  80. If you prefer the Python builds from python.org should be sufficient as well.
  81. * Xcode. [Install the latest one](http://developer.apple.com/tools/download/).
  82. * Xcode Command Line Tools.
  83. Open the Xcode preferences, then in the Downloads tab, select and install the
  84. Command Line Tools.
  85. * [MacPorts](http://www.macports.org/). (Note: Fink may work too but most of the
  86. build testing and instructions is done with MacPorts.)
  87. * autoconf v2.13. Once you have MacPorts installed you need just run
  88. `sudo port install autoconf213`
  89. * ensure you are using clang or gcc 4.2 (or higher)
  90. See <http://developer.mozilla.org/en/docs/Mac_OS_X_Build_Prerequisites>
  91. for more details on Mac OS X build prerequisites. However, following the
  92. above steps is *meant to be sufficient* to get Komodo building.
  93. #### Linux Prerequisites
  94. ##### Ubuntu
  95. `sudo apt-get build-dep firefox`
  96. ##### Fedora
  97. `sudo yum install gcc-c++ patch gtk2-devel libIDL-devel libcurl-devel`
  98. ##### Others
  99. * Python >=2.7 (but not Python 3.x yet). You can
  100. [install ActivePython from here](http://downloads.activestate.com/ActivePython/releases).
  101. If you prefer, your distro's Python 2.7 should be sufficient.
  102. * Everything mentioned in the
  103. [Mozilla Linux build prerequisites](http://developer.mozilla.org/en/docs/Linux_Build_Prerequisites):
  104. #### Building Steps
  105. * Checkout Komodo Edit: `git clone https://github.com/Komodo/KomodoEdit.git`
  106. * Using the terminal, enter your checkout directory and run:
  107. ```
  108. cd komodo/mozilla
  109. python build.py configure -k 9.10
  110. python build.py distclean all
  111. ```
  112. This will configure and build mozilla and can take anywhere from 30 minutes
  113. to several hours to complete (depending on your specs). For most modern
  114. machines it should be about an hour.
  115. * After mozilla is built successfully go back to the main repo directory and
  116. build komodo:
  117. ```
  118. cd ..
  119. export PATH=`pwd`/util/black:$PATH # Komodo's "bk" build tool
  120. bk configure -V 9.10.0-devel
  121. bk build
  122. ```
  123. This should take significantly less time than building Mozilla.
  124. * Once the build has completed you can simply run Komodo by executing `bk run`
  125. Upon making any modifications to the source you will again have to run `bk build`,
  126. or simply `bk build && bk run` to quickly get back into Komodo. Subsequent builds
  127. should be a lot faster as much of the compiled data is cached.
  128. ### Building with Docker
  129. The easiest way to get started is to use our Docker image, this will basically
  130. provide you with a Ubuntu 12.04 based build of Komodo.
  131. After cloning the repository simply navigate into `{repo}/util/docker` and check
  132. out `./docklet --help`
  133. To use the docker image you need to of course have Docker installed as well as
  134. have X11 forwarding enabled in your SSH client (should work by default on most
  135. linux distros).
  136. #### Prepare Docker Image
  137. * Build the docker image: `./util/docker/docklet image`
  138. * Start your container: `./util/docker/docklet start`
  139. * SSH into your container to start working: `./util/docker/docklet ssh`
  140. Your project files will be mounted at `/komodo/dev`
  141. NOTE - if you are updating from a previous version where your project files were
  142. at `/root/komodo` you will need to fix permissions on your Komodo project and
  143. profile folders. Ie:
  144. ```
  145. chown -R <my-username>:<my-group> <my-project-location>
  146. chown -R <my-username>:<my-group> ~/.komodoide
  147. ```
  148. You will also need to redo your build (distclean mozilla and komodo).
  149. #### Building Steps
  150. Once your image is prepared you can follow the building steps for linux as
  151. described below. You will be running these from the docker container, so ssh into
  152. it using the command above and then run the commands from `/komodo/dev`
  153. #### Running
  154. Once your build is complete you exit out of the container (`exit`) and can then
  155. run Komodo with
  156. `./util/docker/docklet run`
  157. To rebuild Komodo (after making changes) and run it again you can use
  158. `./util/docker/docklet build run`
  159. If your changes are not being reflected you may need to clean your build, to do
  160. this use
  161. `./util/docker/docklet clean`
  162. Or to do it all at once (clean, build and run)
  163. `./util/docker/docklet clean build run`
  164. ### Building Complications
  165. If any errors occur during your first built-time and it is not obvious how to fix
  166. the issue on your own please refer to the Feedback section on how to get in contact
  167. with us.
  168. Note that if building complications arise after you updated your repo with the latest
  169. changes you might need to clear your local cache as it might be conflicting with the
  170. new changes, to do this run `bk distclean` before running your build steps.
  171. ### Pro-Tips
  172. **Build a single piece**
  173. Sometimes ```bk build``` is too much and ```bk build quick``` isn't enough. If ```bk build quick``` doesn't appear to pickup your changes, try pointing ```bk build``` at the piece in question.
  174. **Example**
  175. ```bk build build/release/modules/places #this will build the places module only```
  176. **NOTE**: Do not rely on this method as ```bk build quick``` is faster and in some cases does some steps that the above example won't perform. Use it as a last ditch effort before you try ```bk distclean && bk build```.
  177. ---