-
Notifications
You must be signed in to change notification settings - Fork 13
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
Archive source types don't seem to be extracted before executing build-commands #233
Comments
Is this the last manifest entry? Also, can you show the full manifest so we can reproduce it? |
Yes, this is the last module. See the attached JSON. |
Usually you should put your app as the last module, that is a requirement for the extension to be able to do anything useful |
Using the same manifest with this module entry:
When using flatpak-builder on the command line, it seems to extract and execute the build-commands entries just fine, but using the "Flatpak: Build" command within this vscode extension, the first cp command fails to find any files. The files don't appear to have been extracted into a folder in the .flatpak/flatpak-builder/build/ directory.
Flatpak output:
Also note that the git source builds and installs fine; the destination paths exist and the mkdir command makes sure of it. Also a file source has a similar cp command and it works fine, though it isn't using a wildcard for the source file.
The text was updated successfully, but these errors were encountered: