prebuilt for ARM devices... [$65]

[bmatusiak]

there are 2 common arm build as i can see

one is armel and the other is armhf

it would be cool if there was a ARM prebuilt binary

If there are others who would like to see ARM prebuilt binaries add a +1 to this issue and hopefully maintainer will deliver

There is a $65 open bounty on this issue. Add to the bounty at Bountysource.

[katanacrimson]

Related: #193, #437.

[davidbenhaim]

+1

[timonsku]

+1 Would be great for digital signage.

[dtauschke]

+1

[pvoisin]

+1

[cranic]

+1

[richardanaya]

+1

[richardanaya]

Does anyone know the current steps to doing this?

[gumyn]

Yeah something to "dd" on the ssd card ;) and paf node-webkit on rpi

Awesome ^^

[milanvanschaik]

Would be really nice! Want to run it on a Raspberry Pi (in fullscreen :-)).

[cranic]

@milanvanschaik but you can do this with chromium-browser in kiosk mode :-)

[bmatusiak]

@cranic, "chromium-browser" does not support nodejs plugins/modules automatically

[silkycove]

+1

[jtenner]

Workaround so far is chromium-browser with browserified packages (browser specific shims.) This is undesirable of course. Anyone who needs a solution now might benefit from this though.

[milanvanschaik]

What about this? Seems like possible but we simply need a 'prebuild' version? https://github.com/rogerwang/node-webkit/issues/193#issuecomment-21974887

[silkycove]

I was misunderstanding. I simply thought that I can do npm node-webkit on Raspberry Pi when the binary is available. During trying to build node-webkit with latest deps packages, I learnt that it was not easy to maintain multiple arm binaries. I will withdraw my +1 now. -1 ;-) Note: Actualy, I could not build webkit on Raspberry pi (w/DISTCC) with latest deps. The build is terminated by VFP related error on merging V8. I do not know it is the cause but I found "Removed ARM support for VFP2." on V8 3.18.0 release note.

[xingped]

+1. None of the instructional gists for compiling my own version seem to work. I'm dying for a prebuilt binary for arm.

[ndhunju]

+1

[qrpike]

+1

[jaredallard]

+2

On Mon, Jul 21, 2014 at 1:48 PM, Quinton Pike notifications@github.com wrote:

+1

— Reply to this email directly or view it on GitHub https://github.com/rogerwang/node-webkit/issues/1151#issuecomment-49663288 .

[smolleyes]

+1

[raykamp]

+1

[bmatusiak]

We are at 14 votes, so please vote!

[Dbuggerx]

+1

[nicu]

+1

[paul-piro]

+1

[alexjstubbs]

+1

[gumyn]

+5

[chrisJohn404]

+1

[Gutem]

+1

[ghost]

+1

[stevenvachon]

+1

[s-sjha]

I am reposting my issue here in the thread just in case if someone has any information about this problem.

Hi all, I have been trying to compile the latest version of nodewebkit for armhf to be used on a beaglebone black. As beaglebone black is not really suited for the compilation, i got a freescale imx6.quad wandboard and am using Ubuntu14.04 from armhf to compile the nodewebkit. I have followed all the instruction from different gist available like https://gist.github.com/xdenser/ba4454f79d4438d7f2f2 https://gist.github.com/albi90/6135922 and have been able to compile the source, however, the linker is failing with two different message, first was 'memory exhausted'. I activated 4 GB of swap and it still kept on failing regardless.

Then I based on chromium's fast build suggestion, I switched to shared library compilation, again compilation is fine, however, the linker now fails with following error,

/usr/bin/ld: obj/content/nw/src/api/shortcut/nw_lib.global_shortcut_listener_x11.o: undefined reference to symbol '_ZN2ui24XKeysymForWindowsKeyCodeENS_12KeyboardCodeEb' lib//libevents_base.so: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status ninja: build stopped: subcommand failed.

I checked to see if libevents_base.so exists in the lib folder or not and its there also, the file is included in the linker argument list, so I any help if resolving this problem would be really helpful.

[kyleget]

+1

[bmatusiak]

+1 over a year later and i still need

[JumpLink]

+1

[Hagith]

+1

[serverwentdown]

+1

[FREEZX]

+1

[matejkramny]

+1

[sciguy14]

+1

[amegz]

+1

[jtg-gg]

@rogerwang I manage to make an arm build, using this guide https://code.google.com/p/chromium/wiki/LinuxChromiumArm if i want to support this on live build, how I customize the build machine ?

[jtg-gg]

I've an nw12 armhf build https://github.com/jtg-gg/node-webkit/releases/download/nw-v0.12.0/nwjs-v0.12.0-linux-arm.tar.gz tested on Raspberry Pi 2

[SoulOnFire]

@jtg-gg Amazing job! Thanks!

[Hagith]

@jtg-gg Many Thanks! Can you share more detailed recipe how to make this build? It would be awesome.

I see some compatibility commits in your fork, is it enough to build for ARM? (I don't have close at hand environment to check).

[ashupp]

@jtg-gg Thank you very much! Works great!

One Question because i want to play H.264 / MP4 Files - is there a suitable ffmpegsumo.so file? Or must it be compiled together?

[jtg-gg]

@rafalgalka I compiled it using Ubuntu 14.04 LTS from my x86 PC I follow the cross compilation method https://code.google.com/p/chromium/wiki/LinuxChromiumArm

then I need to modify the zlib.gyp, because it refer to x86 assembly then the default rootfs/sysroot from Google is actually fine, but nwjs is using libnotify, hence I need to add this library package into the sysroot. then after that you can compile

but to distribute, I need to modify the nw.gypi, since the symbol dump + stripping doesn't work on x86. I strip the symbol using the raspberry pi (if you are not stripping the symbol, the executable is 1 GB in size)

[jtg-gg]

@daCuJo I am not sure about the custom ffmpegsumo.so with h.264/mp4 capability the default ffmpegsumo is supplied with the build

[eduardodoria]

@jtg-gg I tried to run your build using Raspbian with LXDE with no success. What is the environment you use to run this?

Also I tested the build of #193 and I can run, but it's too old version.