-
Notifications
You must be signed in to change notification settings - Fork 131
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
Building your first Flatpak doesn't work #230
Comments
I ran into this today and had another problem as well. The original line: $ flatpak-builder build-dir org.flatpak.Hello.yml fails with the message:
It seems to be a constant in the docs that merely specifying I don't know what the correct behaviour is, otherwise I'd issue a PR to fix the docs. If someone can answer my questions I'm happy to offer a fix for the docs as a PR:
|
This is Step 1 on that page: https://docs.flatpak.org/en/latest/first-build.html#install-a-runtime-and-the-matching-sdk
No, but you can pass
Build dir != cache dir. This is not a problem. |
...but it is a problem, because the documentation when followed verbatim results in an error message that isn't explained in the documentation. The docs say that you should first build your flatpak: $ flatpak-builder build-dir org.flatpak.Hello.yml and the very next code fragment says to install your flatpak with this: $ flatpak-builder --user --install build-dir org.flatpak.Hello.yml Executing these two commands in order results in an error:
Either the docs should predict or at least explain this error, or they should tell the user to (a) delete the As for the bit about needing to install the Sdk. Sorry about that, I must have had this page confused with the multitude of other pages that don't make it clear that you need to download these files first. Maybe the solution here is a better error message? Something like
|
first-build.rst
is bugged.This is not true, there is no /app subdirectory inside build-dir
flatpak-builder --user --install build-dir org.flatpak.Hello.yml
doesn't work. Error is as follows:
Using
--force-clean
doesn't work eitherThe text was updated successfully, but these errors were encountered: