I’m currently working on a project that involves stripping atom of many of its core features and adding a few customizations. I essentially want to code and distribute a minimal version of atom with a few non-standard features and a slightly modified GUI.
I’ve forked and cloned the atom repo, run
script/bootstrap to install dependencies. At this point atom is not installed and I am not able to run atom in any form (if that’s incorrect, please let me know). I can run
script/build to build the source code which outputs a bunch of files into the
/out directory: (
app atom-1.29.0-dev-ba96165-amd64 atom-amd64.deb startup.js symbols). In order to create an executable file I have to add the
--create-debian-package flag to
script/build. Once I’ve built the source code and the installable file, I can install atom (
dpkg -i atom-amd64.deb) and see the modifications I’ve made to the source code.
This workflow - modify source code, rebuild, and reinstall - seems overly cumbersome and in fact, there’s a section in the atom docs titled ‘Hacking on Atom Core’ which says that if I run atom in dev mode and point it to the directory where I’m storing atom’s source code, I should be able to make modifications to that source code and see them in atom without running the build script.
Some background - I’m a web developer with limited knowledge of building native code from source so if I’m way off base about any of my ideas, please let me know.