Nixpkgs: Build node-webkit, electron from source

Created on 18 Jul 2016 · 6Comments · Source: NixOS/nixpkgs

Both node-webkit and electron are just being downloaded from binary tarballs. It would be great if we could use the outputs of "chromium" to create a "chromiumcontent" output that could be used by these two frameworks as inputs.

TODO

[ ] package "chromiumcontent"
[ ] move "node-webkit" to source based build
[ ] move "electron" to source based build
[ ] move "atom" to source based build
[ ] move "bracket" to source based build
[ ] move "vscode" to source based build

Related

issue #6689

enhancement stale

Source

matthewbauer

👍4

Most helpful comment

It would be great indeed if vscode could be built from source because it is currently a non-free package (because the binaries are non-free) while, if built from source, it would be a free package (because the source code in under MIT license).

Zimmi48 on 11 Mar 2017

👍3

All 6 comments

Zimmi48 on 11 Mar 2017

👍3

I could do this if someone would lend me computing power.

yegortimoshenko on 6 Nov 2017

@yegortimoshenko

I could do this if someone would lend me computing power.

If you ask on IRC someone might be able to set up a Hydra jobset for you...

/cc @LnL7

matthewbauer on 6 Nov 2017

Any idea how long these would take to build?

LnL7 on 6 Nov 2017

When I've built Chromium on my laptop with Intel i7-2677M CPU, it took around 24 hours. On Hydra, Electron should take about the same time to build as Chromium, as Node.js is relatively small, and Electron's own code should be negligible.

yegortimoshenko on 7 Nov 2017

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

Search for maintainers and people that previously touched the related code and @ mention them in a comment.
Ask on the NixOS Discourse.
Ask on the #nixos channel on irc.freenode.net.