-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to build on ChromeOS Debian 11/12 #622
Comments
Please build the latest master. I'm still working on a fresh release. The code is considered mostly stable (RC, basically). |
I just gave this another try, but now I'm on Debian 12 Bookworm on ChromeOS:
Following the instructions, I downloaded and set up the repo, and installed the dependencies:
This time, I switched to the 'master' branch before building:
Then I ran the build commands:
It succeeded (with warnings, but no errors). Then I ran the install command:
However, when I try launching any of the binaries, I get an error:
I looked back at the build output, and I see:
But looking at the output from |
Closed by #686. |
Pre-submit checks
Describe the bug
I'm unable to build AppImageLauncher for Linux on ChromeOS, which runs Debian Bullseye:
I followed the instructions exactly as written here (see attached screencapture), i.e.
At first,
cmake .. -DCMAKE_INSTALL_PREFIX="$PREFIX" -DUSE_SYSTEM_BOOST=true
failed because I was missingxxd
, which was easily fixed by the following:Then,
make libappimage libappimageupdate libappimageupdate-qt
failed with the following output:Here's the commit that I built from:
Expected behavior
I expected the build to complete.
Steps to reproduce the issue
On ChromeOS, open Terminal and enter the following:
Screenshots
Distribution and desktop environment
Distribution: Debian 11 (Bullseye)
Desktop environment: ChromeOS
Installed AppImageLauncher version
None installed (this bug is about trying to build and install).
Here's the commit that I built from:
List of AppImages you tried
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: