_Hi :wave: This issue is an informational issue about the state of running Atom on computers with ARM processors (like those in Raspberry Pis and some Chromebooks)._
Atom does not _effectively_ work on ARM (July 9th, 2015)
It does, however, now _build_ and _launch_ on ARM (see image above from ARM Chromebook). This is due to the fact that Electron, as of v0.29.0 now builds an ARM compatible distribution :sparkles: (as an aside, this is really, really great news for future applications and tinkerers). But the latest versions of Electron use a newer version of Chrome and have not been tested against Atom which currently uses v.22.3 of Electron (at this time Electron was still named Atom-Shell). Typing and clicking don't work at all and/or trigger lots of exception notifications and render the application pretty useless. This could be because of the new Electron compatibility issues, but we can't be quite sure as we don't really know yet what those issues are.
What will it take to get there?
These errors will have to be sorted out and fixed. This is not on any roadmap right now and could be a lot of work (patches welcome! :raised_hands:). Getting Atom upgraded to the latest Electron will help answer this question but it's not there just yet (https://github.com/atom/atom/pull/6877).
It's worth noting that even if Atom were on the latest Electron, you will still need to build it yourself because it requires some other adjustments (see below).
Want to try it out?
Maybe it will _just work_ on your machine! I have a gist with the steps to build. It involves using forks of both apm (Atom's package manager) and Atom so that you can build apm with io.js instead of Node.js since the later does not support ARM.
jlord
All 121 comments
:link: Cross linking to relevant issues:
jlord
on 10 Jul 2015
@jlord Are you using Samsung ARM Chromebook?
zohead
on 22 Jul 2015
@zohead No, I have an 11" Asus C201.
jlord
on 23 Jul 2015
@zohead I am.
henrywright
on 25 Aug 2015
Anyone tried again since https://github.com/atom/atom/pull/7877 landed? I dont have my arm box here
jacobrosenthal
on 10 Sep 2015
@jacobrosenthal I started to try, but got hung up on getting apm going. I have the fork of it so that it can use an ARM version of node and it _had_ been working, but I started my system over from scratch and now it's not... I was thinking I would go ahead and make a branch to try and get atom/apm on the latest version of node, 4.0.0, which now has an ARM version.
jlord
on 10 Sep 2015
I think that might be tough. My understanding is Node 4 is nan2 and electron v0.30.6 was purposely selected as the last nan1 release to dodge nan2 upgrades.
jacobrosenthal
on 11 Sep 2015
@jacobrosenthal I just built apm with this branch: https://github.com/atom/apm/pull/430
I had a bit of trouble on a couple modules but at least one was resolved and then the other maybe disappeared (ha).
I just built Atom from this branch. I then move the apm I built to atom/apm/node_modules/ and rename it atom-package-manager. Then I run script/build within /atom.
This works... Atom launches and there aren't errors, only opening a file as large (which is not in fact large) as package.json freezes the app basically and you get an application not responding dialog.
jlord
on 11 Sep 2015
Took a shot today, patching out the apm and electron download
https://github.com/jacobrosenthal/apm/tree/arm
https://github.com/jacobrosenthal/atom/tree/arm
I think I tried on 4.1.1 first and spellcheck and symbols failed, but when I tried again on 4.1.2 everything built, and it loads but to a chrome dev tools window with no tabs that I cant type into and in the console:
jacob@gaia:~/Downloads$ /tmp/atom-build/Atom/atom
[11304:1013/052008:ERROR:browser_main_loop.cc(173)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[11304:1013/052012:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[11304:1013/052012:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[11304:1013/052012:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[11304:1013/052012:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[11332:1013/052012:INFO:renderer_main.cc(200)] Renderer process started
App load time: 3024ms
[11350:1013/052016:INFO:renderer_main.cc(200)] Renderer process started
[11304:1013/052016:INFO:CONSOLE(56)] "Error: Cannot find module '../build/Release/keyboard-layout-observer.node'
at Module._resolveFilename (module.js:334:15)
at Function.Module._resolveFilename (/tmp/atom-build/Atom/resources/app.asar/src/module-cache.js:383:52)
at Function.Module._load (module.js:284:25)
at Module.require (module.js:363:17)
at require (module.js:382:17)
at Object.<anonymous> (/tmp/atom-build/Atom/resources/app.asar/node_modules/atom-keymap/node_modules/keyboard-layout/lib/keyboard-layout.js:6:28)
at Object.<anonymous> (/tmp/atom-build/Atom/resources/app.asar/node_modules/atom-keymap/node_modules/keyboard-layout/lib/keyboard-layout.js:50:4)
at Module._compile (module.js:428:26)
at Object.defineProperty.value [as .js] (/tmp/atom-build/Atom/resources/app.asar/src/compile-cache.js:169:21)
at Module.load (module.js:353:32)", source: file:///tmp/atom-build/Atom/resources/app.asar/static/index.js (56)
I looked at the current mac installer and indeed, app.asar.unpacked/node_modules/atom-keymap doesnt exist
jacobrosenthal
on 13 Oct 2015
apm merged node 4.2.1 support into master so trying again
Node: v4.2.1
npm: v2.14.7
Same process as @jlord above, but to repeat
- apm comment out node download https://github.com/jacobrosenthal/apm/tree/arm
- build apm as per directions
- rename it as atom/apm/node_modules/atom-package-manager
- atom comment out apm download, https://github.com/jacobrosenthal/atom/tree/arm
- build atom as per directions
It builds and 'works' but continuously spawns
Atom Version: 1.2.0-dev-6495f1a
System: Debian GNU/Linux
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Cannot read property 'replace' of undefined
At /home/jacob/Downloads/atom/buildir/Atom/resources/app.asar/src/lines-tile-component.js:265
TypeError: Cannot read property 'replace' of undefined
at LinesTileComponent.module.exports.LinesTileComponent.setLineInnerNodes (/home/jacob/Downloads/atom/buildir/Atom/resources/app.asar/src/lines-tile-component.js:265:72)
at LinesTileComponent.module.exports.LinesTileComponent.buildLineNode (/home/jacob/Downloads/atom/buildir/Atom/resources/app.asar/src/lines-tile-component.js:198:14)
at LinesTileComponent.module.exports.LinesTileComponent.updateLineNodes (/home/jacob/Downloads/atom/buildir/Atom/resources/app.asar/src/lines-tile-component.js:141:34)
at LinesTileComponent.module.exports.LinesTileComponent.updateSync (/home/jacob/Downloads/atom/buildir/Atom/resources/app.asar/src/lines-tile-component.js:98:12)
at LinesComponent.module.exports.TiledComponent.updateTileNodes (/home/jacob/Downloads/atom/buildir/Atom/resources/app.asar/src/tiled-component.js:67:19)
at LinesComponent.module.exports.TiledComponent.updateSync (/home/jacob/Downloads/atom/buildir/Atom/resources/app.asar/src/tiled-component.js:30:12)
at LinesYardstick.module.exports.LinesYardstick.prepareScreenRowsForMeasurement (/home/jacob/Downloads/atom/buildir/Atom/resources/app.asar/src/lines-yardstick.js:26:37)
at TextEditorPresenter.module.exports.TextEditorPresenter.getState (/home/jacob/Downloads/atom/buildir/Atom/resources/app.asar/src/text-editor-presenter.js:183:27)
at TextEditorComponent.module.exports.TextEditorComponent.updateSync (/home/jacob/Downloads/atom/buildir/Atom/resources/app.asar/src/text-editor-component.js:199:38)
at /home/jacob/Downloads/atom/buildir/Atom/resources/app.asar/src/text-editor-component.js:302:28
at ViewRegistry.module.exports.ViewRegistry.performDocumentUpdate (/home/jacob/Downloads/atom/buildir/Atom/resources/app.asar/src/view-registry.js:177:9)
at /home/jacob/Downloads/atom/buildir/Atom/resources/app.asar/src/view-registry.js:3:61
Commands
Config
{}
Installed Packages
# User
No installed packages
# Dev
No dev packages
/cc @as-cii
50Wliu
on 17 Oct 2015
It seems like the GrammarRegistry isn't able to find a scope (scopeForId) and, therefore, it returns null. Not sure what the exact issue could be there, but it seems to point out towards first-mate not working correctly.
as-cii
on 20 Oct 2015
I just tried the build aproach described by jlord with atom 1.4.0-beta3 and it still works.
(npm test showed no errors for the atom and the apm directory, and opening some files worked using odroid-xu4 with ubuntu preinstalled emmc card)
I had to tweak the apm start script to remove the harmony-collectins flag tough...
UPDATE While atom started over ssh -Y and looked promissing in the beginning, It is crashing and lacking responisitivity. This may be due to ssh -Y. I plan to try with a monitor....
thanks,
Franz
franzhaas
on 25 Dec 2015
I tried to compile atom on raspberry pi 3 with the new ubuntu mate build for pi3. But it failed:
sudo apt-get install build-essential git libgnome-keyring-dev fakeroot
sudo apt-get install nodejs npm gcc g++ make
sudo npm config set python /usr/bin/python2 -g
sudo update-alternatives --install /usr/bin/node node /usr/bin/nodejs 10
git clone https://github.com/atom/atom
cd atom/
git fetch -p
git checkout $(git describe --tags `git rev-list --tags --max-count=1`)
script/build
pi@raspberrypi3:~/hackallthethings/atom$ script/build
Node: v0.10.25
npm: v1.4.21
Installing build modules...
=> Took 731845ms.
Installing apm...
download not found: http://nodejs.org/dist/v0.10.40/node-v0.10.40-linux-arm.tar.gz
npm ERR! Linux 4.1.18-v7+
npm ERR! argv "node" "/home/pi/hackallthethings/atom/build/node_modules/.bin/npm" "--userconfig=/home/pi/hackallthethings/atom/build/.npmrc" "--target=0.10.35" "install" "--loglevel" "error"
npm ERR! node v0.10.25
npm ERR! npm v2.13.3
npm ERR! code ELIFECYCLE
npm ERR! [email protected] install: `node ./script/download-node.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node ./script/download-node.js'.
npm ERR! This is most likely a problem with the atom-package-manager package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node ./script/download-node.js
npm ERR! You can get their info via:
npm ERR! npm owner ls atom-package-manager
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/pi/hackallthethings/atom/apm/npm-debug.log
It seems like a download is missing. Any ideas how to fix this?
NicoHood
on 29 Feb 2016
@NicoHood There's currently no ARM support out of the box (as described above). Main point of contention is the fact that older versions of Node.js (as used by Atom right now) does not support ARM.
Even though it is outdated at this point, the guide created by @jlord should serve well as a starting point for you if you want to venture down this road, but as far as I know, nobody has yet gotten a fully working Atom running on ARM architecture without problems. Also note that the guide mentions io.js, that is one aspect which is dated (since io.js and Node.js have merged).
Best of luck!
thomasjo
on 29 Feb 2016
@NicoHood If my information is correct you shouldn't need to build it for arm on the new raspberry pi as it switched over to 32 bit type architecture.
NoahVlncrt
on 29 Feb 2016
@thomasjo I literally dusted off my Chromebook to pick this back up again. Do you recall what the offline discussion was here around apm: https://github.com/atom/apm/pull/456#issuecomment-149920790
gjtorikian
on 1 Mar 2016
@NoahVlncrt what? Raspberry pi used 32bit all the time. The new Pi3 is 64 bit though. But it is still arm and not intel. Or am I wrong?
Getting arm builds (in general for programs and especially for atom) is a very nice thing, cause more and more device with arm come up now. And they are powerful enough to use them as desktop like PC now.
NicoHood
on 1 Mar 2016
@gjtorikian I don't recall exactly, but it was specific to a build issue we had with Node.js v4.x which we (at least some of us) thought was caused by Node+npm mismatch between Atom and apm. Turns out that wasn't the root cause of the issues we saw, hence closing that PR.
We still need to upgrade apm's node though. There's an open PR, but it's a bit stale at this point. Let me know if you need a hand, or have more questions.
thomasjo
on 1 Mar 2016
atom/apm#457 seems pretty legit to me. If it were merged in, it'd be easy to extend @jlord's ARM check logic when downloading the appropriate Node version. It wouldn't necessarily make things easier, but it'd mean dealing with less forked versions. :grin:
gjtorikian
on 1 Mar 2016
So what is the best way to get atom running on raspberry pi 3?
If it would help I would be happy to get adafruit to send one to a dev.
https://www.adafruit.com/products/3055
sebe
on 27 Mar 2016
Would absolutely love this running on my pi3.
crewshin
on 6 Apr 2016
I tried again, stumbled across some errors and will report (and edit this post) what my current state is.
I just followed the official build instructions (using pi3 with the latest raspbian image).
I used (as quick solution, be aware of untrusted sources) node 0.10.40 from here (arm6 for rpi1 compatibility)
http://conoroneill.net/node-v01040-and-v0127-for-arm-v7-raspberry-pi-2-banana-pi-odroid-c1-available/
# Get node 0.10.40
mkdir nodetemp
cd nodetemp
wget http://conoroneill.net.s3.amazonaws.com/wp-content/uploads/2015/07/node-v0.10.40-linux-arm-v6.tar.gz
tar -zxvf node-v0.10.40-linux-arm-v6.tar.gz
cd node-0.10.40/usr/local/
sudo cp -R * /usr/local/
sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get install build-essential git libgnome-keyring-dev fakeroot
# Reboot is very important!
sudo reboot
node --version
sudo apt-get install npm
npm -v
git clone https://github.com/atom/atom.git
cd atom/
# Get a stable release (optional, normally does not work)
git fetch -p
git checkout $(git describe --tags `git rev-list --tags --max-count=1`)
sudo npm config set python /usr/bin/python2 -g
script/clean
# try to compile apm for arm first (manually to include node 0.10.40 binary)
# use official compile instructions (used directory hackallthethings/apm)
# Warning: untrusted sources!!
https://github.com/atom/apm/compare/master...NicoHood:arm?expand=1
# Disable the gui when compiling. You need a lot of ram for compiling apm which will fail with a gui started, even on rpi2/3.
# It worked so far, but i have to figure out where to place the file exactly
# All info i got is from here: https://gist.github.com/jlord/7ffaf94d041982346934
mkdir -p apm/node_modules/
cp ../apm/ ./apm/node_modules/ -r
mv apm/node_modules/apm/ apm/node_modules/atom-package-manager
rm apm/node_modules/atom-package-manager/.git -rf
#Then I also applied this patch: https://github.com/atom/atom/commit/1233d51f075ae8970a6864e1dfd13abc41c8199c
# Apply this patch as well:
# https://github.com/atom/atom/pull/11401/commits/b0dd8408395acf160ef7a98f4683ad4f0c00a467
# Compile atom finally (takes a very looong time on rpi3)
script/build (I had an `b7858868-tom-npm-lodash-2-4-2-package-tgz.lock` error, rerun the script again)
Edit: Status: Currently rebuilding...
NicoHood
on 6 Apr 2016
Hi @NicoHood, the auto-updater error should be fixed in Atom 1.7.0 if you want to try building that version.
50Wliu
on 7 Apr 2016
Okay going to try this tomorrow. Do I also have to rebuild apm?
However I got a very weird display when I stared atom. It looked like a javascript/css debug console. I guess this is unrelated to the issue above? I will take a screenshot (and recompile) tomorrow.
NicoHood
on 7 Apr 2016
However I got a very weird display when I stared atom. It looked like a javascript/css debug console.
Yes, that happens when a fatal error is thrown on startup.
50Wliu
on 7 Apr 2016
I ran script/build again with the master branch (without cleaning, is this a problem?).
And this is the error i meant:
NicoHood
on 8 Apr 2016
Can you click on the red "x" and copy/paste the error here?
50Wliu
on 8 Apr 2016
Error: Cannot find module '../build/Debug/nodegit.node'
at Module._resolveFilename (module.js:338:15)
at Function.Module._resolveFilename (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/module-cache.js:383:52)
at Function.Module._load (module.js:289:25)
at Module.require (module.js:366:17)
at require (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/native-compile-cache.js:50:27)
at Object.<anonymous> (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/node_modules/nodegit/lib/nodegit.js:17:12)
at Module._compile (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/native-compile-cache.js:103:30)
at Object.defineProperty.value [as .js] (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/compile-cache.js:208:21)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:313:12)
at Module.require (module.js:366:17)
at require (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/native-compile-cache.js:50:27)
at Object.<anonymous> (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/git-repository-async.js:25:16)
at Module._compile (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/native-compile-cache.js:103:30)
at Object.defineProperty.value [as .js] (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/compile-cache.js:208:21)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:313:12)
at Module.require (module.js:366:17)
at require (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/native-compile-cache.js:50:27)
at Object.<anonymous> (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/git-repository.js:12:24)
at Object.<anonymous> (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/git-repository.js:422:4)
at Module._compile (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/native-compile-cache.js:103:30)
at Object.defineProperty.value [as .js] (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/compile-cache.js:208:21)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:313:12)
at Module.require (module.js:366:17)
at require (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/native-compile-cache.js:50:27)
at Object.<anonymous> (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/git-repository-provider.js:8:19)
at Object.<anonymous> (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/git-repository-provider.js:83:4)
at Module._compile (/home/pi/hackallthethings/atom/out/Atom/resources/app.asar/src/native-compile-cache.js:103:30)
Ok @NicoHood , that will be fixed in #11401.
50Wliu
on 8 Apr 2016
I applied this patch and rebuild. Rebuilding was fast, as it skipped some parts of the build process. The error was still the same. So I guess it did not update this submodule. So I ran the clean script. But this gave me this error. However I am rebuilding once more, with the hope it will be fixed after a clean.
pi@raspberrypi:~/hackallthethings/atom $ script/clean
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
at WriteStream.addListener (events.js:160:15)
at WriteStream.Readable.on (_stream_readable.js:708:33)
at Socket.Stream.pipe (stream.js:65:8)
at Object.exports.safeExec (/home/pi/hackallthethings/atom/script/utils/child-process-wrapper.js:23:16)
at removePath (/home/pi/hackallthethings/atom/script/clean:48:18)
at /home/pi/hackallthethings/atom/script/clean:40:5
at Array.forEach (native)
at Object.<anonymous> (/home/pi/hackallthethings/atom/script/clean:38:15)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
at WriteStream.addListener (events.js:160:15)
at WriteStream.Readable.on (_stream_readable.js:708:33)
at Socket.Stream.pipe (stream.js:99:8)
at Object.exports.safeExec (/home/pi/hackallthethings/atom/script/utils/child-process-wrapper.js:23:16)
at removePath (/home/pi/hackallthethings/atom/script/clean:48:18)
at /home/pi/hackallthethings/atom/script/clean:40:5
at Array.forEach (native)
at Object.<anonymous> (/home/pi/hackallthethings/atom/script/clean:38:15)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
at WriteStream.addListener (events.js:160:15)
at WriteStream.Readable.on (_stream_readable.js:708:33)
at Socket.Stream.pipe (stream.js:121:8)
at Object.exports.safeExec (/home/pi/hackallthethings/atom/script/utils/child-process-wrapper.js:23:16)
at removePath (/home/pi/hackallthethings/atom/script/clean:48:18)
at /home/pi/hackallthethings/atom/script/clean:40:5
at Array.forEach (native)
at Object.<anonymous> (/home/pi/hackallthethings/atom/script/clean:38:15)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
at WriteStream.addListener (events.js:160:15)
at WriteStream.Readable.on (_stream_readable.js:708:33)
at Socket.Stream.pipe (stream.js:65:8)
at Object.exports.safeExec (/home/pi/hackallthethings/atom/script/utils/child-process-wrapper.js:25:18)
at removePath (/home/pi/hackallthethings/atom/script/clean:48:18)
at /home/pi/hackallthethings/atom/script/clean:40:5
at Array.forEach (native)
at Object.<anonymous> (/home/pi/hackallthethings/atom/script/clean:38:15)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
at WriteStream.addListener (events.js:160:15)
at WriteStream.Readable.on (_stream_readable.js:708:33)
at Socket.Stream.pipe (stream.js:99:8)
at Object.exports.safeExec (/home/pi/hackallthethings/atom/script/utils/child-process-wrapper.js:25:18)
at removePath (/home/pi/hackallthethings/atom/script/clean:48:18)
at /home/pi/hackallthethings/atom/script/clean:40:5
at Array.forEach (native)
at Object.<anonymous> (/home/pi/hackallthethings/atom/script/clean:38:15)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
at WriteStream.addListener (events.js:160:15)
at WriteStream.Readable.on (_stream_readable.js:708:33)
at Socket.Stream.pipe (stream.js:121:8)
at Object.exports.safeExec (/home/pi/hackallthethings/atom/script/utils/child-process-wrapper.js:25:18)
at removePath (/home/pi/hackallthethings/atom/script/clean:48:18)
at /home/pi/hackallthethings/atom/script/clean:40:5
at Array.forEach (native)
at Object.<anonymous> (/home/pi/hackallthethings/atom/script/clean:38:15)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
Now I get this error (i guess it is only temporary):
Edit: downloads now. Weird.
pi@raspberrypi:~/hackallthethings/atom $ script/build
Node: v0.10.40
npm: v1.4.28
Installing build modules...
=> Took 738335ms.
Deleting old packages...
=> Took 2973ms.
Installing modules ✓
Installing [email protected] ✓
Installing [email protected] ✓
Installing [email protected] ✓
Installing [email protected] ✓
Installing [email protected] ✓
Installing [email protected] ✓
Installing [email protected] ✗
Unable to download https://www.atom.io/api/packages/one-dark-ui/versions/1.3.1/tarball: 503
I still get the same error with the patch.
diff --git a/package.json b/package.json
index b087667..87d547f 100644
--- a/package.json
+++ b/package.json
@@ -37,7 +37,7 @@
"less-cache": "0.23",
"line-top-index": "0.2.0",
"marked": "^0.3.4",
- "nodegit": "0.12.1",
+ "nodegit": "0.12.2",
"normalize-package-data": "^2.0.0",
"nslog": "^3",
"oniguruma": "^5",
diff --git a/script/bootstrap b/script/bootstrap
index 83ec712..5aeeefe 100755
--- a/script/bootstrap
+++ b/script/bootstrap
@@ -118,11 +118,6 @@ function bootstrap() {
options: buildInstallOptions
},
{
- command: apmInstallCommand,
- message: 'Installing apm...',
- options: apmInstallOptions
- },
- {
command: apmPath + ' clean' + apmFlags,
message: 'Deleting old packages...',
options: moduleInstallOptions
So what now? I did not try 1.7.1 (cause I don't have equipment atm) but I guess thats a bug I cannot simply fix?
NicoHood
on 16 Apr 2016
It's been reported that Atom 1.8.0 beta should fix the ../build/nodegit issue. You may need to script/clean before running script/build again.
50Wliu
on 16 Apr 2016
I tried again today, it does not work. Same error. I used a 100% clean image (cause I lost the old).
NicoHood
on 4 May 2016
I'm thrilled to report that with @BinaryMuse's changes in upgrading apm's Node, Atom installs on my ARM Chromebook with very little fuss. 🎉
To get it installed, I:
- Cloned
atom/atom. - Used this PR which upgrades
apm. - Ran
script/buildand waiting for something like two hours for everything to finish.
I had to make two small changes to the apm/node_modules/atom-package-manager files (https://github.com/atom/apm/issues/568, https://github.com/atom/apm/issues/569). But after that, Atom launched. :metal:
It's pretty slow, and there's an apparent error with the NodeGit package, but this is definitely progress!
gjtorikian
on 5 Jun 2016
@gjtorikian @all why do you think it's slow? Is it because the chromebook has a crappy CPU, or some software is not compiled to run on ARM properly?
Sometimes hidden errors can be the cause of slowness. You might find that under the hood there are errors are occurring constantly, causing the slowness?
Perhaps the next step would be to somehow run a profiler on it and see what's slowing it down?
lope
on 5 Jun 2016
My instinct says it's probably the CPU in the machine, but I have no proof. Personally I'm going to try to look into the NodeGit issue before profiling as it still occurs in the latest dev.
gjtorikian
on 5 Jun 2016
NodeGit was definitely: https://github.com/atom/atom/pull/11897#issuecomment-223843393
Rebuilding again grabbed 0.13.1 and all is well.
gjtorikian
on 6 Jun 2016
@gjtorikian "all is well" Do you mean the slowness issue is gone? Thanks for your work on this :+1:
lope
on 6 Jun 2016
No, just that it launched without error, heh.
gjtorikian
on 6 Jun 2016
Have you published your fork which compiles? That'd be the fastest way for me to retry. I will test for archlinux and possibly raspbian on rpi3.
NicoHood
on 6 Jun 2016
@NicoHood I placed all my steps three posts up: https://github.com/atom/atom/issues/7822#issuecomment-223787470
There's no fork necessary, just grab the branch off of atom/atom.
gjtorikian
on 6 Jun 2016
You said you edited some files. Before or after compiling? I will try that out now.
NicoHood
on 7 Jun 2016
I tried, but I see no out folder. It seems like it has not finished building properly.
[alarm@alarmpi atom]$ git merge remotes/origin/mkt-use-apm-with-npm3-and-node-4
Merge made by the 'recursive' strategy.
apm/package.json | 2 +-
build/package.json | 2 +-
script/bootstrap | 7 +------
3 files changed, 3 insertions(+), 8 deletions(-)
[alarm@alarmpi atom]$ script/build
Node: v6.2.1
npm: v2.13.3
Installing build modules...
(node:1616) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:1616) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:1616) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:1616) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:1616) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:1616) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:1616) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:1616) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:1616) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
=> Took 51068ms.
Installing apm...
[alarm@alarmpi atom]$ ls
CHANGELOG.md CONTRIBUTING.md ISSUE_TEMPLATE.md README.md appveyor.yml build coffeelint.json dot-atom keymaps package.json script src vendor
CODE_OF_CONDUCT.md Dockerfile LICENSE.md apm atom.sh circle.yml docs exports menus resources spec static
Ran into the same problem as you. Have you found a fix? @NicoHood
NoahVlncrt
on 10 Jun 2016
Nope. Do you also use arch linux (alarm) or raspbian?
NicoHood
on 10 Jun 2016
Neither I'm running it on my Chromebook ARMv7. I tried a few times yesterday I'm giving it another shot today. I'm thinking it's outputting to some where else. There is something else weird going on, I run it and unless I go into the apm folder specifically and run npm install it doesn't install the the node module. It's very weird and I'm going to give it another shot today.
NoahVlncrt
on 10 Jun 2016
These are the errors i'm running into right now
script/build
Node: v4.4.5
npm: v2.15.5
Installing build modules...
=> Took 339218ms.
Installing apm...
download not found: http://nodejs.org/dist/v4.4.5/node-v4.4.5-linux-arm.tar.gz
=> Took 296262ms.
/home/noah/atom/apm/node_modules/atom-package-manager/bin/apm: line 35: /home/noah/atom/apm/node_modules/atom-package-manager/bin/node: No such file or directory
The no such file or directory one I think I know how to fix but the download not found one is driving me nuts I can't figure out how to get it to fetch a version of node that exists. Anyone have any ideas? Do you know anything @gjtorikian I did what you said I cloned it then merged the pull request and this is the error i'm getting :/
NoahVlncrt
on 10 Jun 2016
Ah yeah super sorry, I did edit one file: https://github.com/atom/apm/pull/570
gjtorikian
on 10 Jun 2016
I now tried again.
I pulled the latest atom git and the latest apm git. I (still) applied the atom patch and also the apm patch. I had to disable lightdm (gui) to compile apm, as it required a lot ram when downloading. Otherwise everything will crash on rpi3 with 1gb ram. I then copied the apm files to the atom folder again and compiled atom.
My instructions above a a bit outdated, and i did not patch node (as i am using arch linux now), but it should give you some guide:
https://github.com/atom/atom/issues/7822#issuecomment-206433940
Compiling now seems to work but takes forever. I will update my results, probably via edit.
Edit: I think it crashed because no cpu activity is there for a long time now. Those were the last lines:
Running "build" task
Running "babel:dist" (babel) task
Running "coffee:glob_to_multiple" (coffee) task
>> 341 files created.
Running "prebuild-less:src" (prebuild-less) task
(node:15018) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
However it is still running fine with only 67mb ram usage. So I guess there must be still some errors.
Edit: it might be me, because i unplugged the ethernet cable (even though it should be connected via wlan).
Edit: Compilation finished it seems, the app starts. But i still get this nodegit error again. So nothing has improved from the user side.
NicoHood
on 11 Jun 2016
I ran script/build a little bit ago and it's still compiling. It's been 2 1/2 hours so far. I'm heading out to the store so i'm hoping this is all finished then.
Edit: Welp. . . nothing seemed to happen after around 4 hours. I'll try again later. It just stalled and didn't move.
NoahVlncrt
on 11 Jun 2016
I compiled atom with the changes from Use [email protected] with Node v4 and apm v3 o/ #11897 .
Compiled with out errors but don't start properly due to Error: Cannot find module '../build/Debug/nodegit.node'....
This is the log:
Error: Cannot find module '../build/Debug/nodegit.node'
at Module._resolveFilename (module.js:339:15)
at Function.Module._resolveFilename (/home/acruz/bin/atom-v1.10.0-dev/share/
atom/resources/app.asar/src/module-cache.js:383:52)
at Function.Module._load (module.js:290:25)
at Module.require (module.js:367:17)
at require (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/s
rc/native-compile-cache.js:50:27)
at Object.
/app.asar/node_modules/nodegit/dist/nodegit.js:18:12)
at Module._compile (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/ap
p.asar/src/native-compile-cache.js:103:30)
at Object.defineProperty.value as .js
at Module.load (module.js:357:32)
at Function.Module._load (module.js:314:12)
at Module.require (module.js:367:17)
at require (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/s
rc/native-compile-cache.js:50:27)
at Object.
/app.asar/node_modules/ohnogit/build/lib/repository.js:67:11)
at Module._compile (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/native-compile-cache.js:103:30)
at Object.defineProperty.value as .js
at Module.load (module.js:357:32)
at Function.Module._load (module.js:314:12)
at Module.require (module.js:367:17)
at require (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/native-compile-cache.js:50:27)
at Object.
.js:3:20)
at Module._compile (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/native-compile-cache.js:103:30)
at Object.defineProperty.value as .js
at Module.load (module.js:357:32)
at Function.Module._load (module.js:314:12)
at Module.require (module.js:367:17)
at require (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/native-compile-cache.js:50:27)
at Object.
at Module._compile (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/native-compile-cache.js:103:30)
at Object.defineProperty.value as .js
at Module.load (module.js:357:32)
My platform is : Linux chrubuntu 3.10.18 #1 SMP Fri Jun 3 23:55:49 EDT 2016 armv7l armv7l armv7l GNU/Linux
Acer cb5-311 chromebook (tegra jetson k1)
Any one knows how to solve this error???
Thanks
acruzpr
on 15 Jun 2016
Solved the problem of nodegit by installing missing dependencies necessary to build nodegit since there is not binary available for arm:
sudo apt-get install openssl libssl-dev
Then script/clean, script/build and then install. It open the interface, is a llitle slow but I think that is due to an error:
[Enter steps to reproduce below:]
- ...
- ...
Atom Version: 1.10.0-dev-21d3b67
System: Ubuntu 14.04.4
Thrown From: Atom Core
Stack Trace
Uncaught IndexSizeError: Failed to execute 'setEnd' on 'Range': The offset 1 is larger than or equal to the node's length (0).
At /home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/lines-yardstick.js:161
Error: Failed to execute 'setEnd' on 'Range': The offset 1 is larger than or equal to the node's length (0).
at Error (native)
at LinesYardstick.module.exports.LinesYardstick.clientRectForRange (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/lines-yardstick.js:161:32)
at LinesYardstick.module.exports.LinesYardstick.leftPixelPositionForScreenPosition (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/lines-yardstick.js:143:36)
at LinesYardstick.module.exports.LinesYardstick.pixelPositionForScreenPosition (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/lines-yardstick.js:108:19)
at TextEditorPresenter.module.exports.TextEditorPresenter.pixelPositionForScreenPosition (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/text-editor-presenter.js:1297:38)
at TextEditorPresenter.module.exports.TextEditorPresenter.updateHorizontalDimensions (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/text-editor-presenter.js:879:34)
at TextEditorPresenter.module.exports.TextEditorPresenter.getPostMeasurementState (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/text-editor-presenter.js:134:12)
at TextEditorComponent.module.exports.TextEditorComponent.updateSync (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/text-editor-component.js:209:38)
at TextEditorComponent.module.exports.TextEditorComponent.becameVisible (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/text-editor-component.js:304:21)
at TextEditorComponent.module.exports.TextEditorComponent.checkForVisibilityChange (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/text-editor-component.js:1027:16)
at TextEditorComponent.module.exports.TextEditorComponent.pollDOM (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/text-editor-component.js:1014:17)
at /home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/text-editor-component.js:3:61
at ViewRegistry.module.exports.ViewRegistry.performDocumentPoll (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/view-registry.js:265:9)
at ViewRegistry.<anonymous> (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/node_modules/underscore/underscore.js:701:23)
at ViewRegistry.module.exports.ViewRegistry.requestDocumentPoll (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/view-registry.js:256:21)
at MutationObserver.<anonymous> (/home/acruz/bin/atom-v1.10.0-dev/share/atom/resources/app.asar/src/view-registry.js:3:61)
Commands
Config
{}
Installed Packages
# User
minimap, v4.24.6 (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.1.0 (inactive)
base16-tomorrow-light-theme, v1.1.1 (inactive)
one-dark-ui, v1.3.3 (active)
one-light-ui, v1.3.3 (inactive)
one-dark-syntax, v1.2.0 (active)
one-light-syntax, v1.2.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.5.2 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.2 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.0 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.0 (active)
bookmarks, v0.41.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.38.1 (active)
find-and-replace, v0.200.0 (inactive)
fuzzy-finder, v1.2.0 (active)
git-diff, v1.0.1 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.1 (active)
image-view, v0.58.1 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v0.53.1 (active)
notifications, v0.64.1 (active)
open-on-github, v1.1.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.238.0 (active)
snippets, v1.0.2 (active)
spell-check, v0.67.1 (active)
status-bar, v1.3.1 (active)
styleguide, v0.46.0 (active)
symbols-view, v0.113.0 (inactive)
tabs, v0.99.0 (active)
timecop, v0.33.1 (active)
tree-view, v0.208.0 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.34.0 (active)
whitespace, v0.32.2 (active)
wrap-guide, v0.38.1 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.0 (active)
language-csharp, v0.12.1 (active)
language-css, v0.36.2 (active)
language-gfm, v0.87.0 (active)
language-git, v0.13.0 (active)
language-go, v0.42.0 (active)
language-html, v0.44.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.23.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.0 (active)
language-less, v0.29.3 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.0 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.68.5 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.54.0 (active)
language-shellscript, v0.22.4 (active)
language-source, v0.9.0 (active)
language-sql, v0.21.1 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.8 (active)
language-yaml, v0.26.0 (active)
# Dev
No dev packages
How to solve this problem?
Thanks!!
acruzpr
on 15 Jun 2016
On my device I can't seem to compile it like I just had it running for 6 hours. I believe i'm doing something wrong. Would anyone mind posting there working branch on github so I could give it a try?
NoahVlncrt
on 18 Jun 2016
Sorry for the delay...
Try this: https://github.com/acruzpr/atom.git
acruzpr
on 1 Jul 2016
I cloned your repo and got (archlinux on raspberry pi3, arm7):
[alarm@alarmpi3 atom]$ script/build
/home/alarm/hackallthethings/atom_arm/atom/script/bootstrap:100
if (process.argv.indexOf('--no-quiet') === -1) || process.env.ATOM_NOISY_BUILD) {
^^
SyntaxError: Unexpected token ||
at Object.exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:513:28)
at Object.Module._extensions..js (module.js:550:10)
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
at Function.Module.runMain (module.js:575:10)
at startup (node.js:160:18)
at node.js:456:3
There is one bracket too much (or too less), I removed one. Now building. Editing this post on updates...
NicoHood
on 2 Jul 2016
Sorry!!!
I made the changes by hand and forgot to remove the ")" after the -1...
the line should be :
if (process.argv.indexOf('--no-quiet') === -1 || process.env.ATOM_NOISY_BUILD) {
Thanks!
Fixing it in my fork...
acruzpr
on 2 Jul 2016
Do you need to manually compile apm? All I did now was to clone you repo (fix this minor issue myself) and compile the code. Its stuck at
Node: v6.2.1
npm: v3.9.5
Installing build modules...
But It might need some more time...
Edit: It took just a lot of time. I will edit if the final build works. This will take one more hour I assume.
NicoHood
on 2 Jul 2016
No... I used the files from the repo...
The first and second part take few minutes and you dont see any output.
The third step take some time but, at least there is some output ...
acruzpr
on 2 Jul 2016
This is the first time that the editor seems to run on ARM. It takes some time since all tabs are loaded at startup. But I still get those errors (inside the gui in red):
/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/src/lines-yardstick.js:161
Uncaught IndexSizeError: Failed to execute 'setEnd' on 'Range': The
offset 1 is larger than or equal to the node's length (0).
Error: Failed to execute 'setEnd' on 'Range': The offset 1 is larger
than or equal to the node's length (0).
at Error (native)
at LinesYardstick.module.exports.LinesYardstick.clientRectForRange
(/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/src/lines-yardstick.js:161:32)
at
LinesYardstick.module.exports.LinesYardstick.leftPixelPositionForScreenPosition
(/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/src/lines-yardstick.js:143:36)
at
LinesYardstick.module.exports.LinesYardstick.pixelPositionForScreenPosition
(/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/src/lines-yardstick.js:108:19)
at
TextEditorPresenter.module.exports.TextEditorPresenter.pixelPositionForScreenPosition
(/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/src/text-editor-presenter.js:1297:38)
at
TextEditorPresenter.module.exports.TextEditorPresenter.updateHorizontalDimensions
(/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/src/text-editor-presenter.js:879:34)
at
TextEditorPresenter.module.exports.TextEditorPresenter.getPostMeasurementState
(/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/src/text-editor-presenter.js:134:12)
at TextEditorComponent.module.exports.TextEditorComponent.updateSync
(/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/src/text-editor-component.js:209:38)
at
TextEditorComponent.module.exports.TextEditorComponent.becameVisible
(/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/src/text-editor-component.js:304:21)
at
TextEditorComponent.module.exports.TextEditorComponent.checkForVisibilityChange
(/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/src/text-editor-component.js:1027:16)
at TextEditorComponent.module.exports.TextEditorComponent.pollDOM
(/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/src/text-editor-component.js:1014:17)
at
/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/src/text-editor-component.js:3:61
at ViewRegistry.module.exports.ViewRegistry.performDocumentPoll
(/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/src/view-registry.js:265:9)
at ViewRegistry.<anonymous>
(/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/node_modules/underscore/underscore.js:701:23)
at ViewRegistry.module.exports.ViewRegistry.requestDocumentPoll
(/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/src/view-registry.js:256:21)
at MutationObserver.<anonymous>
(/home/alarm/hackallthethings/atom_arm/atom/out/Atom/resources/app.asar/src/view-registry.js:3:61)
This error reappears if I click in the gui.
NicoHood
on 3 Jul 2016
I have the same problem... If you find out how to solve this error please let me know...
acruzpr
on 3 Jul 2016
I'm busy compiling right now on my Raspberry Pi 2 running Raspbian Jessie. I will edit later if I fix any issues.
superwhiskers
on 6 Jul 2016
@gjtorikian did you had the same problem as @NicoHood ???
acruzpr
on 13 Jul 2016
Yep.
I haven't been able to look into a fix, because of time constraints. But I intend to!
gjtorikian
on 13 Jul 2016
As an aside, Visual Studio Code will work on the Raspberry Pi.
internalfx
on 3 Oct 2016
So there is still no any update.
incyi
on 9 Oct 2016
it looks good for me until i start searching....
I use atom 1.10.2
[Enter steps to reproduce below:]
- open text file
- ctr+F search
Atom Version: 1.10.2
Electron Version: 0.37.8
System: Ubuntu 16.04.1
Thrown From: Atom Core
Stack Trace
Uncaught IndexSizeError: Failed to execute 'setEnd' on 'Range': The offset
1 is larger than or equal to the node's length (0).
At /usr/local/share/atom/resources/app.asar/src/lines-yardstick.js:161
Error: Failed to execute 'setEnd' on 'Range': The offset 1 is larger than
or equal to the node's length (0).
at Error (native)
at LinesYardstick.module.exports.LinesYardstick.clientRectForRange
(/usr/local/share/atom/resources/app.asar/src/lines-yardstick.js:161:32)
at
LinesYardstick.module.exports.LinesYardstick.leftPixelPositionForScreenPosition
(/usr/local/share/atom/resources/app.asar/src/lines-yardstick.js:143:36)
at
LinesYardstick.module.exports.LinesYardstick.pixelPositionForScreenPosition
(/usr/local/share/atom/resources/app.asar/src/lines-yardstick.js:108:19)
at
TextEditorPresenter.module.exports.TextEditorPresenter.pixelPositionForScreenPosition
(/usr/local/share/atom/resources/app.asar/src/text-editor-presenter.js:1328:38)
at
TextEditorPresenter.module.exports.TextEditorPresenter.updateHorizontalDimensions
(/usr/local/share/atom/resources/app.asar/src/text-editor-presenter.js:897:34)
at
TextEditorPresenter.module.exports.TextEditorPresenter.getPostMeasurementState
(/usr/local/share/atom/resources/app.asar/src/text-editor-presenter.js:135:12)
at TextEditorComponent.module.exports.TextEditorComponent.updateSync
(/usr/local/share/atom/resources/app.asar/src/text-editor-component.js:211:38)
at TextEditorComponent.module.exports.TextEditorComponent.becameVisible
(/usr/local/share/atom/resources/app.asar/src/text-editor-component.js:314:21)
at
TextEditorComponent.module.exports.TextEditorComponent.checkForVisibilityChange
(/usr/local/share/atom/resources/app.asar/src/text-editor-component.js:1040:16)
at TextEditorComponent.module.exports.TextEditorComponent.pollDOM
(/usr/local/share/atom/resources/app.asar/src/text-editor-component.js:1026:17)
at
/usr/local/share/atom/resources/app.asar/src/text-editor-component.js:3:61
at ViewRegistry.module.exports.ViewRegistry.performDocumentPoll
(/usr/local/share/atom/resources/app.asar/src/view-registry.js:265:9)
at ViewRegistry.module.exports.ViewRegistry.performDocumentUpdate
(/usr/local/share/atom/resources/app.asar/src/view-registry.js:228:14)
at /usr/local/share/atom/resources/app.asar/src/view-registry.js:3:61
Commands
4x -1:34.5.0 editor:move-to-beginning-of-word
(atom-text-editor.editor.is-focused)
-1:32.4.0 editor:move-to-first-character-of-line
(atom-text-editor.editor.is-focused)
10x -1:30.8.0 editor:move-to-end-of-word
(atom-text-editor.editor.is-focused)
-1:28.6.0 editor:move-to-beginning-of-word
(atom-text-editor.editor.is-focused)
12x -1:27.9.0 editor:select-to-end-of-word
(atom-text-editor.editor.is-focused)
-1:24.4.0 editor:select-to-beginning-of-word
(atom-text-editor.editor.is-focused)
10x -1:15 core:backspace (atom-text-editor.editor.is-focused)
2x -0:50.5.0 editor:move-to-beginning-of-word
(atom-text-editor.editor.is-focused)
2x -0:49.5.0 editor:move-to-end-of-word
(atom-text-editor.editor.is-focused)
11x -0:42.9.0 core:backspace (atom-text-editor.editor.is-focused)
2x -0:11.9.0 core:move-right (atom-text-editor.editor.is-focused)
-0:11.2.0 core:move-left (atom-text-editor.editor.is-focused)
-0:10.9.0 core:move-right (atom-text-editor.editor.is-focused)
-0:10.6.0 editor:select-to-beginning-of-word
(atom-text-editor.editor.is-focused)
6x -0:06.2.0 core:backspace (atom-text-editor.editor.is-focused)
-0:00.5.0 find-and-replace:show (atom-text-editor.editor.is-focused)
Config
{}
Installed Packages
# User
git-blame, v0.4.11 (inactive)
git-plus, v5.18.0 (active)
Hydrogen, v0.14.0 (inactive)
language-tex, v0.4.0 (active)
latex, v0.37.1 (active)
minimap, v4.25.0 (active)
split-diff, v1.0.5 (inactive)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.1.0 (inactive)
base16-tomorrow-light-theme, v1.1.1 (inactive)
one-dark-ui, v1.5.0 (active)
one-light-ui, v1.5.0 (inactive)
one-dark-syntax, v1.3.0 (active)
one-light-syntax, v1.3.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.5.3 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.2 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.41.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.39.0 (active)
find-and-replace, v0.201.0 (active)
fuzzy-finder, v1.3.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.1 (active)
image-view, v0.58.2 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v0.53.1 (active)
notifications, v0.65.0 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.242.2 (active)
snippets, v1.0.2 (active)
spell-check, v0.67.1 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.0 (active)
symbols-view, v0.113.0 (inactive)
tabs, v0.100.2 (active)
timecop, v0.33.2 (active)
tree-view, v0.208.2 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.34.0 (active)
whitespace, v0.33.0 (active)
wrap-guide, v0.38.1 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.2 (active)
language-csharp, v0.12.1 (active)
language-css, v0.37.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.42.1 (active)
language-html, v0.45.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.23.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.2 (active)
language-less, v0.29.5 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.2 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.69.0 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.56.0 (active)
language-shellscript, v0.22.4 (active)
language-source, v0.9.0 (active)
language-sql, v0.23.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.9 (active)
language-yaml, v0.26.0 (active)
# Dev
No dev packages
2016-10-09 19:43 GMT+00:00 Yigit [email protected]:
So there is still no any update.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/7822#issuecomment-252507730, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK8goeWvyr9uemAg8nHXO3EnjSpIX3PRks5qyUPqgaJpZM4FVtS_
.
franzhaas
on 10 Oct 2016
Compile fail on Ubuntu Mate 16.04 64-bit for ODroid C2:
Node: v6.7.0
Npm: v3.10.5
Installing script dependencies
../deps/breakpad/src/common/linux/memory_mapped_file.cc: In member function ‘bool google_breakpad::MemoryMappedFile::Map(const char_, size_t)’:
../deps/breakpad/src/common/linux/memory_mapped_file.cc:60:38: error: ‘sys_open’ was not declared in this scope
int fd = sys_open(path, O_RDONLY, 0);
^
../deps/breakpad/src/common/linux/memory_mapped_file.cc:66:22: error: aggregate ‘google_breakpad::MemoryMappedFile::Map(const char_, size_t)::kernel_stat st’ has incomplete type and cannot be defined
struct kernel_stat st;
^
../deps/breakpad/src/common/linux/memory_mapped_file.cc:67:24: error: ‘sys_fstat’ was not declared in this scope
if (sys_fstat(fd, &st) == -1 || st.st_size < 0) {
^
../deps/breakpad/src/common/linux/memory_mapped_file.cc:72:17: error: ‘sys_close’ was not declared in this scope
sys_close(fd);
^
../deps/breakpad/src/common/linux/memory_mapped_file.cc:82:17: error: ‘sys_close’ was not declared in this scope
sys_close(fd);
^
../deps/breakpad/src/common/linux/memory_mapped_file.cc:87:75: error: ‘sys_mmap’ was not declared in this scope
void* data = sys_mmap(NULL, file_len, PROT_READ, MAP_PRIVATE, fd, offset);
^
../deps/breakpad/src/common/linux/memory_mapped_file.cc:97:15: error: ‘sys_close’ was not declared in this scope
sys_close(fd);
^
../deps/breakpad/src/common/linux/memory_mapped_file.cc: In member function ‘void google_breakpad::MemoryMappedFile::Unmap()’:
../deps/breakpad/src/common/linux/memory_mapped_file.cc:108:72: error: ‘sys_munmap’ was not declared in this scope
sys_munmap(const_cast
^
make: *** [Release/obj.target/dump_syms/deps/breakpad/src/common/linux/memory_mapped_file.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/home/doctor/Documents/workspace/atom/script/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack at emitTwo (events.js:106:13)
gyp ERR! stack at ChildProcess.emit (events.js:191:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Linux 3.14.79-89
gyp ERR! command "/usr/local/bin/node" "/home/doctor/Documents/workspace/atom/script/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/doctor/Documents/workspace/atom/script/node_modules/minidump
gyp ERR! node -v v6.7.0
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
npm ERR! Linux 3.14.79-89
npm ERR! argv "/usr/local/bin/node" "/home/doctor/Documents/workspace/atom/script/node_modules/.bin/npm" "--loglevel=error" "install"
npm ERR! node v6.7.0
npm ERR! npm v3.10.5
npm ERR! code ELIFECYCLE
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the minidump package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs minidump
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls minidump
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/doctor/Documents/workspace/atom/script/npm-debug.log
child_process.js:506
throw err;
^
Error: Command failed: /home/doctor/Documents/workspace/atom/script/node_modules/.bin/npm --loglevel=error install
../deps/breakpad/src/common/linux/memory_mapped_file.cc: In member function ‘bool google_breakpad::MemoryMappedFile::Map(const char_, size_t)’:
../deps/breakpad/src/common/linux/memory_mapped_file.cc:60:38: error: ‘sys_open’ was not declared in this scope
int fd = sys_open(path, O_RDONLY, 0);
^
../deps/breakpad/src/common/linux/memory_mapped_file.cc:66:22: error: aggregate ‘google_breakpad::MemoryMappedFile::Map(const char_, size_t)::kernel_stat st’ has incomplete type and cannot be defined
struct kernel_stat st;
^
../deps/breakpad/src/common/linux/memory_mapped_file.cc:67:24: error: ‘sys_fstat’ was not declared in this scope
if (sys_fstat(fd, &st) == -1 || st.st_size < 0) {
^
../deps/breakpad/src/common/linux/memory_mapped_file.cc:72:17: error: ‘sys_close’ was not declared in this scope
sys_close(fd);
^
../deps/breakpad/src/common/linux/memory_mapped_file.cc:82:17: error: ‘sys_close’ was not declared in this scope
sys_close(fd);
^
../deps/breakpad/src/common/linux/memory_mapped_file.cc:87:75: error: ‘sys_mmap’ was not declared in this scope
void* data = sys_mmap(NULL, file_len, PROT_READ, MAP_PRIVATE, fd, offset);
^
../deps/breakpad/src/common/linux/memory_mapped_file.cc:97:15: error: ‘sys_close’ was not declared in this scope
sys_close(fd);
^
../deps/breakpad/src/common/linux/memory_mapped_file.cc: In member function ‘void google_breakpad::MemoryMappedFile::Unmap()’:
../deps/breakpad/src/common/linux/memory_mapped_file.cc:108:72: error: ‘sys_munmap’ was not declared in this scope
sys_munmap(const_cast
^
make: *** [Release/obj.target/dump_syms/deps/breakpad/src/common/linux/memory_mapped_file.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/home/doctor/Documents/workspace/atom/script/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack at emitTwo (events.js:106:13)
gyp ERR! stack at ChildProcess.emit (events.js:191:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Linux 3.14.79-89
gyp ERR! command "/usr/local/bin/node" "/home/doctor/Documents/workspace/atom/script/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/doctor/Documents/workspace/atom/script/node_modules/minidump
gyp ERR! node -v v6.7.0
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
npm ERR! Linux 3.14.79-89
npm ERR! argv "/usr/local/bin/node" "/home/doctor/Documents/workspace/atom/script/node_modules/.bin/npm" "--loglevel=error" "install"
npm ERR! node v6.7.0
npm ERR! npm v3.10.5
npm ERR! code ELIFECYCLE
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the minidump package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs minidump
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls minidump
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/doctor/Documents/workspace/atom/script/npm-debug.log
at checkExecSyncError (child_process.js:483:13)
at Object.execFileSync (child_process.js:503:13)
at module.exports (/home/doctor/Documents/workspace/atom/script/lib/install-script-dependencies.js:10:16)
at Object.<anonymous> (/home/doctor/Documents/workspace/atom/script/bootstrap:26:1)
at Module._compile (module.js:556:32)
at Object.Module._extensions..js (module.js:565:10)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
at Module.require (module.js:483:17)
thedocbwarren
on 14 Oct 2016
Hey,
I just wanted to quickly share my current state, maybe you have some hints for me:
script/build --create-debian-package went well up to this point:
Installing [email protected] ✓
Wrote Dependencies Fingerprint: /home/maru/atom/node_modules/.dependencies-fingerprint 44caa49ec45323b3d14d0f7872194037bc45daaf
Copying assets to /home/maru/atom/out/app
Transpiling Babel paths in /home/maru/atom/out/app
Transpiling CoffeeScript paths in /home/maru/atom/out/app
Transpiling CSON paths in /home/maru/atom/out/app
Transpiling PEG.js paths in /home/maru/atom/out/app
Generating module cache for /home/maru/atom/out/app
Generating pre-built less cache in /home/maru/atom/out/app/less-compile-cache
Generating metadata for /home/maru/atom/out/app/package.json
Generating API docs at /home/maru/atom/docs/output/atom-api.json
Skipping Chromedriver download because it is used only on macOS
Dumping symbols in /home/maru/atom/out/symbols
Running electron-packager on /home/maru/atom/out/app with app name "atom"
Error: Unsupported arch arm; must be one of: ia32, x64
at packager (/home/maru/atom/script/node_modules/electron-packager/index.js:193:40)
at Promise (/home/maru/atom/script/lib/package-application.js:141:5)
at runPackager (/home/maru/atom/script/lib/package-application.js:140:10)
at module.exports (/home/maru/atom/script/lib/package-application.js:17:10)
As far as I know, electron has pushed some ARM support... is maybe electron-packager not yet referencing a ARM compatible version of electron?
Could it be possible, that this is an issue due to the --create-debian-package flag?
I'll have another try with --install.
Help and hints appreciated 😅
System I'm working on:
Nexus 5 with MaruOS 0.3 (Debian Jessie).
Regaddi
on 5 Nov 2016
Does electron require X11 or can the apps be invoked from raspberrypi command line ?
eddywebs
on 16 Nov 2016
I get the same error on a chromebook:
Running electron-packager on /home/cristi/atom/out/app with app name "atom"
Error: Unsupported arch arm; must be one of: ia32, x64
at packager (/home/cristi/atom/script/node_modules/electron-packager/index.js:193:40)
at /home/cristi/atom/script/lib/package-application.js:136:5
at runPackager (/home/cristi/atom/script/lib/package-application.js:135:10)
at module.exports (/home/cristi/atom/script/lib/package-application.js:17:10)
The error appears no matter what flags I use.
cristifalcas
on 20 Nov 2016
I gave it another shot, it is very easy to get it compiled, I used 1.13.0 to start, and changed:
--- a/script/lib/package-application.js
+++ b/script/lib/package-application.js
@@ -20,7 +20,7 @@ module.exports = function () {
'app-version': CONFIG.appMetadata.version,
'arch': (() => {
if (process.platform === 'linux') {
- return process.arch
+ return 'armv7l'
} else {
return process.platform === 'win32' ? 'ia32' : 'x64'
}})(),
diff --git a/script/package.json b/script/package.json
index 1f4cf78..d91499a 100644
--- a/script/package.json
+++ b/script/package.json
@@ -8,7 +8,7 @@
"colors": "1.1.2",
"csslint": "1.0.2",
"donna": "1.0.13",
- "electron-packager": "7.3.0",
+ "electron-packager": "8.5.0",
"electron-winstaller": "2.3.4",
"fs-extra": "0.30.0",
"glob": "7.0.3",
--- a/script/lib/package-application.js
+++ b/script/lib/package-application.js
@@ -20,7 +20,7 @@ module.exports = function () {
'app-version': CONFIG.appMetadata.version,
'arch': (() => {
if (process.platform === 'linux') {
- return process.arch
+ return 'armv7l'
} else {
return process.platform === 'win32' ? 'ia32' : 'x64'
}})(),
diff --git a/script/package.json b/script/package.json
index 1f4cf78..d91499a 100644
--- a/script/package.json
+++ b/script/package.json
@@ -8,7 +8,7 @@
"colors": "1.1.2",
"csslint": "1.0.2",
"donna": "1.0.13",
- "electron-packager": "7.3.0",
+ "electron-packager": "8.5.0",
"electron-winstaller": "2.3.4",
"fs-extra": "0.30.0",
"glob": "7.0.3",
new electron-packager versions support armv7l, process.arch unfortunately gives arm, i applied a quick and dirty override, it compiles then.
it starts however find and packages (the menu buttons) do not work work and I get the warnings:
[27972:0114/121332:ERROR:browser_main_loop.cc(231)] Running without the SUID sandbox! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the sandbox on.
[27972:0114/121411:WARNING:x11_util.cc(1406)] X error received: serial 18554, error_code 3 (BadWindow (invalid Window parameter)), request_code 3, minor_code 0 (X_GetWindowAttributes)
[27972:0114/121411:WARNING:x11_util.cc(1406)] X error received: serial 18582, error_code 3 (BadWindow (invalid Window parameter)), request_code 3, minor_code 0 (X_GetWindowAttributes)
[27972:0114/121411:WARNING:x11_util.cc(1406)] X error received: serial 18611, error_code 3 (BadWindow (invalid Window parameter)), request_code 3, minor_code 0 (X_GetWindowAttributes)
This is interesting. Would love to install atom on GNURoot Debian on my phone so I can do some emergency hacking wherever I am.
Redsandro
on 1 Feb 2017
@Redsandro same, atom.io if my favourite ide on my pc but i would love to be able to use it on GNUroot debian too with x server
Can sombody compile a .deb for armhf please
wsngamerz
on 17 Mar 2017
Atom 1.15.0 armv7l prebuilt:
_URL removed by @thomasjo_
I'm not guarantee that it will works fine on all devices.
After downloading run atom executable (it will create ~/.atom for packages), then run atom.firstboot.sh (it will install all default packages). After downloading & installing packages you can remove atom.firstboot.sh. Good luck!
ghost
on 9 Apr 2017
@hypersad I removed the URL you shared because we do not allow linking to unofficial, custom binary distributions of Atom.
thomasjo
on 9 Apr 2017
Since this issue does not represent anything that is directly actionable, I'm closing it.
/cc @atom/maintainers
thomasjo
on 9 Apr 2017
@thomasjo I'm interested in getting atom running on the raspberry pi, is there a package I can download and try it ? I'm willing to help test it out.
djaramil
on 9 Apr 2017
@hypersad Can you send me your fork so I can compile it?
acruzpr
on 9 Apr 2017
@thomasjo Are you providing an official arm distribution???
acruzpr
on 9 Apr 2017
@djaramil @acruzpr There are currently no concrete plans to provide official ARM support. If someone wants to open a PR that puts into place all the necessary changes, etc, go ahead. If said PR does not negatively impact current platforms, and is well-behaved, I'm sure we're more than happy to hit the merge button.
I _highly_ recommend basing such a PR on #12696.
NOTE: The only major issue that might prevent us from merging said PR, is lack of CI support. One possibility is to investigate https://resin.io/ as part of the PR.
thomasjo
on 9 Apr 2017
@djaramil and @acruzpr you can contact with me by email [email protected] and I can share with some advices of building Atom on ARM.
ghost
on 9 Apr 2017
Or, I think, I should start a fork for ARM.
ghost
on 9 Apr 2017
+1
On Sun, Apr 9, 2017 at 2:01 PM hypersad notifications@github.com wrote:
Or, I think, I should start a fork for ARM.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/7822#issuecomment-292805323, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAQtkWIUGQF7MUpPEHUxGTNtV83L2uL_ks5ruSsHgaJpZM4FVtS_
.>
~~~~ Gene Crucean m: 951.551.2369 Please excuse the brevity
and any typos. This transmission was sent from my mobile command center.
crewshin
on 9 Apr 2017
@hypersad I think starting an armed branch would be the smart idea. I think having a completed working set of code laid out would help people out more. I'm also sure that the community on the raspberry pi and arm Chromebooks will flock to it and help contribute. I know I will.
NoahVlncrt
on 9 Apr 2017
I quickly made a little fork of Atom 1.15.0 (you can read in README.md why not newest version), wrote armv7l installation guide and made some fixes of incorrect detecting armv7l. I ask you to try to build it this night and report bugs. Additional, fix grammar mistakes in README.md, my knowledge of english is poor.
ghost
on 9 Apr 2017
@NoahVlncrt You are absolutely right. A bunch of us that are strong users of Atom on the desktop and we are now doing some work on RaspberryPi with TJBot project and I'm dying without Atom on there. @hypersad this is awesome that you are moving forward with this. I'll be happy to try it and report back any issues and will be happy to correct any grammar issues in the README.md. :-) Can you provide me with a link to your branch, and build. Thank you so much.
djarami
on 10 Apr 2017
@djarami hypersad/atom, read me in this folder contains guide.
ghost
on 10 Apr 2017
Is there anyone who tried to build from my fork? Any results?
ghost
on 10 Apr 2017
hypersad commented 11 days ago
Is there anyone who tried to build from my fork? Any results?
I would like to try out your ARM version, where can I get it and how do I install it?
ArmandoHerra
on 22 Apr 2017
@SekethThoth visit @hypersad/atom and build from there
wsngamerz
on 22 Apr 2017
For everyone, builds from this fork have been working for several ARM devices: https://github.com/hypersad/atom
curiousercreative
on 22 Apr 2017
@Reggadi, not sure if you ever for Atom working, but I'm also on a Nexus 5 and MaruOS and this formed repo will build and run pretty flawlessly for me! https://github.com/hypersad/atom
curiousercreative
on 22 Apr 2017
@hypersad :1st_place_medal: Thank you for all the time and effort dedicated to make this a reality. I can confirm that it work like a charm!!! I just compile it in my chrubuntu acer chromebook CB5-311 with TEGRA K1. Now I can do some cuda programing directly on this machine. Thanks!!!
System information:
uname -a :
Linux chrubuntu 3.10.18 #1 SMP Fri Jun 3 23:55:49 EDT 2016 armv7l armv7l armv7l GNU/Linux)
/etc/os-release:
NAME="Ubuntu"
VERSION="14.04.5 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.5 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
acruzpr
on 22 Apr 2017
Thanks guys! Tomorrow I'll check it out on my RPi.
ArmandoHerra
on 23 Apr 2017
@hypersad I built it successfully on my Raspberry Pi 3 but when I first ran it it looked like this:
And after I ran your "first boot" script it looked like this:
None of the menu entries do anything except for "toggle developer tools".
Linux Raspi3 4.9.23-v7+ #989 SMP Wed Apr 19 15:29:25 BST 2017 armv7l armv7l armv7l GNU/Linux, Ubuntu Mate 16.04
Is there any more information I can collect to help find the issue?
nonnymoose
on 24 Apr 2017
@nonnymoose That happened to me too. It took some time to load the interface the second time. Probably due to the small amount of memory in the Rpi3 you will need to wait longer in order to see the interface. Try to load it and give it some time to load the interface. My machine is 4 core 2.1 Ghz and 4 GB of RAM and I had to wait like 1 min, you probably will need to wait longer.
acruzpr
on 24 Apr 2017
Thank you so much! I have now successfully compiled and ran on the
Raspberry Pi 3! It's PERFECT!!!
I'll upload screenshots tomorrow.
On Apr 23, 2017 19:46, "Nonny Moose" moosenonny10@gmail.com wrote:
Oh, thanks, let me try that.
On Apr 23, 2017 19:26, "Anthony Cruz" notifications@github.com wrote:
@nonnymoose https://github.com/nonnymoose That happened to me too. It
took some time to load the interface the second time. Probably due to the
small amount of memory in the Rpi3 you will need to wait longer in order to
see the interface. Try to load it and give it some time to load the
interface. My machine is 4 core 2.1 Ghz and 4 GB of RAM and I had to wait
like 1 min, you probably will need to wait longer.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/7822#issuecomment-296500012, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AS8L0FuDwYRguXbjKrJzQsyV_Ffq1pASks5ry-xIgaJpZM4FVtS_
.
nonnymoose
on 24 Apr 2017
@nonnymoose try creating the install file and it will install on the menus.
see issue: https://github.com/hypersad/atom/issues/5
djarami
on 24 Apr 2017
Please, create issues at my repository if you have troubles with building or working. Thanks! Glad to see that my fork works.
ghost
on 24 Apr 2017
I would like I'm really hoping to see Atom officially releasing an ARM version soon.
daylightbrightledlight
on 8 Sep 2017
Look what I've got!
ghost
on 30 Dec 2017
@hypersad You're amazing!
nonnymoose
on 30 Dec 2017
3:30 AM (GMT+3) and I've finally made stable building way for it. Hope I'll upload a repository with patches and instructions today, but now I should take some sleep :^)
ghost
on 31 Dec 2017
Successfully built it on my Raspberry Pi 3, can someone else test it?
ghost
on 31 Dec 2017
@hypersad I will as soon as I can get a fan set up to keep it from overheating. :)
nonnymoose
on 31 Dec 2017
@noonymouse on my RPi 3 temperature during building was up to 65C° without fan which is good for it, because normal working temperature for them - up to 80C°.
ghost
on 31 Dec 2017
@hypersad I was able to build your repo on my Chromebook, running mksnapshot on an x86_64 system. I can open the Atom editor by executing ./out/atom-1.23.2-armv7l/atom. Yay!
mathuin
on 1 Jan 2018
@mathuin is it works as expected? Could you provide screenshot, please?
ghost
on 1 Jan 2018
@hypersad Very cool work! How's the performance?
rdagger
on 1 Jan 2018
@rdagger on my Raspberry Pi 3 I've noticed:
- Lags when working on a Markdown files with live preview, so you better disable it and enable sometimes to check is your work looks as expected.
You can't delete files directly in Atom, because there is no
gvfs-trashin Raspbian repositories and Raspbian probably using something else to work with trash.
Update on this:gvfs-trashis deprecated, in latest versions ofElectrongiois used to work with trash, and it is supported in Raspbian.Installing packages take little more time.
ghost
on 2 Jan 2018
@hypersad Build on my pi failed :(
I created the issue hypersad/atom-armv7l#1
nonnymoose
on 4 Jan 2018
Hi, does anyone happen to have a fork/anything of the arm version of @hypersad? The account has been deleted :(
danieltroger
on 13 May 2018
Yeah, no idea, but I'd really appreciate it if anybody has a copy.
Hope she is fine, because hypersad sounds.... quite sad.
danieltroger
on 13 May 2018
@nonnymoose @danieltroger Electron has been upgraded to 2.0.0 recently, now it has native working mksnapshot binaries for armv7l. Node.JS started working on armv7l binaries and I hope they'll release properly compiled binaries soon (if they didn't). I think my work is done and there is no use of me anymore. If Atom team want to make armv7l support, they realize it soon.
Also I'm male and I have no idea who is on my profile picture.
ghost
on 16 May 2018
@hypersad Thanks for all the time an effort that you dedicated to this and make it a reality. I hope that the Atom team adds support for the armv7l platform soon. In the meantime, @nonnymoose @danieltroger there is an alternative out there that is easy to compile on armv7l.
acruzpr
on 20 May 2018
I've just tried to build Atom on the Raspberry Pi but I still get the following error:
Running electron-packager on /home/pi/atom/out/app with app name "atom"
Error: Unsupported arch arm; must be one of: ia32, x64
Even though I'm using electron 2.0.1, what else do I need to be able to build Atom on armv71?
Thanks!
VA3SFA
on 2 Jul 2018
The Atom team does not support armv7l platform, and @hypersad your repo has gone.
Where can I start from? I'm working on an Odroid XU4 running ArchLinux.
Thanks!
gounthar
on 5 Oct 2018
Where is Hypersad's repo?I was Promised Deb packages where are they?I think atom can run on arm now.
ghost
on 16 Dec 2018
This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!
![lock[bot] picture](https://avatars1.githubusercontent.com/in/6672?v=4&s=40)
lock[bot]
on 14 Jun 2019
Related issues
spring-bu
·
101Comments
alexwhitman
·
119Comments
martindale
·
120Comments
pbhogan
·
126Comments
JamesTheAwesomeDude
·
103Comments
Most helpful comment
Would absolutely love this running on my pi3.