arm builds

58 views
Skip to first unread message

jon.w....@gmail.com

unread,
Jun 4, 2019, 10:51:53 PM6/4/19
to nw.js
Hi Roger,

I'm looking at the abandoned arm build repos on github:


which patches nw.js from here:


and, for some reason, also patches Chromium:


Unfortunately, it appears that none of the patches apply cleanly any more. However, a lot of the nw.js patches are basically just adding entries to the build infrastructure for the arm architecture.

If I prune these out for a clean patch set would you apply them upstream? If so I'll go ahead and add some code to potentially handle arm64 as well.

Also, if anyone can shed light on why jtg-gg was patching Chromium-- which as I understand already runs on arm archs-- I would appreciate it.

Thanks,
Jonathan

Roger Wang

unread,
Jun 4, 2019, 10:55:34 PM6/4/19
to jon.w....@gmail.com, nw.js
Thanks for your interest in porting NW.js to ARM. Yes I would love to merge it. And if the patch is not too big or complex, I will see to rebase it from version to version.

Best regards,
Roger

--
You received this message because you are subscribed to the Google Groups "nw.js" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nwjs-general...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nwjs-general/5bbba558-e0fe-415a-b84e-cab2e9aa3360%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

jon.w....@gmail.com

unread,
Jun 18, 2019, 7:27:04 PM6/18/19
to nw.js
Hi Roger,

Can you tell me exactly what distro and version you are using to build nw.js?

Also-- can I successfully build nw.js from a clean install on that distro?

The Chromium link you provide in your build docs says to use Ubuntu 14.04 for the build. But I'm already hitting an error with an out-of-date version of openjdk on that distro. After fixing that I'm getting all kinds of errors like:

IOError: [Errno 2] No such file or directory: u'../../out/nw/gen/chrome/app/chrome_content_browser_manifest_overlay.json'

Plus an error previous to that about duplicate keys in a grit-related file. I'd rather not hand patch individual Chromium files just to get an x86_64 build to complete. (That is, I'm not even trying to cross-compile for arm yet...)

I'm checking out from here:


Any hints? There's no simple script to build nw.js so I can only go from your build documentation and the build script Laszlo has here:


Thanks,
Jonathan

On Tuesday, June 4, 2019 at 10:55:34 PM UTC-4, Roger Wang wrote:
Thanks for your interest in porting NW.js to ARM. Yes I would love to merge it. And if the patch is not too big or complex, I will see to rebase it from version to version.

Best regards,
Roger

On Wed, Jun 5, 2019, 10:51 AM <jon.w...@gmail.com> wrote:
Hi Roger,

I'm looking at the abandoned arm build repos on github:


which patches nw.js from here:


and, for some reason, also patches Chromium:


Unfortunately, it appears that none of the patches apply cleanly any more. However, a lot of the nw.js patches are basically just adding entries to the build infrastructure for the arm architecture.

If I prune these out for a clean patch set would you apply them upstream? If so I'll go ahead and add some code to potentially handle arm64 as well.

Also, if anyone can shed light on why jtg-gg was patching Chromium-- which as I understand already runs on arm archs-- I would appreciate it.

Thanks,
Jonathan

--
You received this message because you are subscribed to the Google Groups "nw.js" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nwjs-g...@googlegroups.com.

Roger

unread,
Jun 25, 2019, 7:34:17 PM6/25/19
to jon.w....@gmail.com, nw.js
We are using Ubuntu 16.04.2 LTS but 14.04 should be fine too. You'll need JRE 8 installed for that compile error.

To unsubscribe from this group and stop receiving emails from it, send an email to nwjs-general...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nwjs-general/7d04b89d-6ce7-4cd1-9a1b-f115c81ca30f%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages