Skip to content
This repository was archived by the owner on Jul 12, 2019. It is now read-only.

Cannot build for Raspberry Pi #22

Open
braydend opened this issue Nov 30, 2018 · 3 comments
Open

Cannot build for Raspberry Pi #22

braydend opened this issue Nov 30, 2018 · 3 comments

Comments

@braydend
Copy link

Hi,
When I try to run scripts/pack-pi It consistently errors out at:
screen shot 2018-11-30 at 1 38 13 pm

When running npm run pack:pi, however it builds successfully, but when it is loaded onto the Pi, the app launches a white screen and never changes.

The app runs successfully with the latest binary provided, just cant run any compiled myself.

Trying to compile on OSX 10.14 with node 8.12.0 and npm 6.4.1

@Zinggi
Copy link
Member

Zinggi commented Dec 5, 2018

Hi there,

This is actually the exact same problem I ran into when I tried to deploy my fix for #12 to our pi.

Unfortunately, we can currently not allocate too much time for this project, so I would greatly appreciate any help on this.
Especially on the white screen issue, as I also got that far last time I tried.

@therod
Copy link

therod commented Apr 16, 2019

@braydend & @Zinggi: Was able to get this working. Following changes fixed the problem:

  1. Upgrade node to the lastest version 11.13.0. I'm using a .node-version file with nodenv.
  2. Upgrade following packages:
"react": "^15.6.2"
"electron-packager": "^13.1.1"
"electron": "^3.1.8" // Warning: Version +4 will not work on the latest raspberry. https://github.com/electron/electron/issues/16205
"googleapis": "^14.1.0" // not really sure if this is necessary

See the whole package.json on my fork.

  1. Fix a node related issue in the storeToken function in src/gcal/index.js
// Line 71
function storeToken(token) {
  createDirectory(CREDENTIALS_DIR);

  fs.writeFile(SITINCATOR_TOKEN, JSON.stringify(token), function(err, result) {
     if(err) console.log('error', err);
  });
}

I took the codebase to create a German & Widescreen version for a client. Fork of the project can be found here.

Hope this helps with future development.

Cheers,
Rodrigo

@Zinggi
Copy link
Member

Zinggi commented Apr 16, 2019

@therod Thank you very much, this is really helpful. If I can get some time on this I'll see if I can get this fix into master

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants