Closed thatguyatgithub closed 1 year ago
At the moment, it feels like an issue in the builder framework which is not in our control
> electron-builder --publish onTag --arm64
• electron-builder version=23.6.0 os=5.15.0-1038-azure
• publishing will be skipped reason=current build is a part of pull request solution=set env PUBLISH_FOR_PULL_REQUEST to true to force code signing
There are serious security concerns with PUBLISH_FOR_PULL_REQUEST=true (see the CircleCI documentation (https://circleci.com/docs/1.0/fork-pr-builds/) for details)
If you have SSH keys, sensitive env vars or AWS credentials stored in your project settings and untrusted forks can make pull requests against your repo, then this option isn't for you.
• loaded configuration file=package.json ("build" field)
• rebuilding native dependencies dependencies=node-pty@0.10.1 platform=linux arch=arm64
• packaging platform=linux arch=arm64 electron=22.3.3 appOutDir=dist/linux-arm64-unpacked
• downloading url=https://github.com/electron/electron/releases/download/v22.3.3/electron-v22.3.3-linux-arm64.zip size=94 MB parts=4
• downloaded url=https://github.com/electron/electron/releases/download/v22.3.3/electron-v22.3.3-linux-arm64.zip duration=1.174s
• building target=AppImage arch=arm64 file=dist/OpenLens-6.5.2-314.arm64.AppImage
• building target=deb arch=arm64 file=dist/OpenLens-6.5.2-314.arm64.deb
• building target=rpm arch=arm64 file=dist/OpenLens-6.5.2-314.aarch64.rpm
> NX Successfully ran target build:app for project open-lens and 36 tasks it depends on
Nx read the output from the cache instead of running the command for 36 out of 37 tasks.
./open-lens/dist/linux-arm64-unpacked/resources/app.asar.unpacked/node_modules/node-pty/build/Release/pty.node: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=eeb4c2c5dd10b9aaf3d07790fe81f90565ba2a34, not stripped
./open-lens/dist/linux-arm64-unpacked/resources/app.asar.unpacked/node_modules/node-pty/bin/linux-x64-110/node-pty.node: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=eeb4c2c5dd10b9aaf3d07790fe81f90565ba2a34, not stripped
Should I file this issue on https://github.com/lensapp/lens ? What do you suggest me doing?
You can try this, however not sure if they interest into cross-compile issues.
And the issue might be not in lens, except they are using outdated version. The root cause maybe in the tool electron-builder, which should handle the re-compile.
And the issue might be not in lens, except they are using outdated version. The root cause maybe in the tool electron-builder, which should handle the re-compile.
Okey, makes tons of sense, do you have any clue what could I do to workaround this? I'm really really needing to make it work and it seems I'm so close that I want to cry.
Build lens on your local system could help
Hello @jkroepke Did you able to built it on your local computer?
Yes. I able to build it on my mac machine
About the issue, I looked a bit deeper into it and I could figure out that just running "npm rebuild" wont work too. The error is somewhere outside electron-builder and lens... I can not identity the issue, why cross-compile works on Mac, but not on Linux
@thatguyatgithub @Grinch321
I created a possible solution in #160 .
Are you able to validate, if the arm64 binary build are working?
You can find the binary in https://github.com/MuhammedKalkan/OpenLens/actions/runs/5283410533 -> OpenLens-ubuntu-20.04
Woohoo! You are a god! It workkks!
thanks for the confirmation
Are you kidding, thanks to you for your awesome magic! <3 Thanks a bunch!
it's working on my Chromebook , finally I will have lens on it. Many thanks to you)
@jkroepke I have the same issue,you builded the binary is Expired,do you have any url to download the binary? thx
Fresh install is not working with version 6.5.2-309-309
File is present but it's built against x86_64 instead of target arch, Linux arm64 in this case: