You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Stopping at module audio-data-packs
Everything cached, checking out from cache
Pruning cache
>>> flatpak-spawn --host --watch-bus flatpak build --share=network --filesystem=/home/thub/build/info.exult.Exult --filesystem=/home/thub/build/info.exult.Exult/.flatpak/repo --env=PATH=/app/bin:/app/bin:/app/bin:/usr/bin:/home/thub/.var/app/com.visualstudio.code-oss/data/node/bin:/home/thub/.var/app/com.visualstudio.code-oss/data/cargo/bin:/home/thub/.var/app/com.visualstudio.code-oss/data/python/bin:/app/bin:/usr/bin --env=LD_LIBRARY_PATH=/app/lib --env=PKG_CONFIG_PATH=/app/lib/pkgconfig:/app/share/pkgconfig:/usr/lib/pkgconfig:/usr/share/pkgconfig /home/thub/build/info.exult.Exult/.flatpak/repo mkdir -p /app/share/exult/data/music
>>> flatpak-spawn --host --watch-bus flatpak build --share=network --filesystem=/home/thub/build/info.exult.Exult --filesystem=/home/thub/build/info.exult.Exult/.flatpak/repo --env=PATH=/app/bin:/app/bin:/app/bin:/usr/bin:/home/thub/.var/app/com.visualstudio.code-oss/data/node/bin:/home/thub/.var/app/com.visualstudio.code-oss/data/cargo/bin:/home/thub/.var/app/com.visualstudio.code-oss/data/python/bin:/app/bin:/usr/bin --env=LD_LIBRARY_PATH=/app/lib --env=PKG_CONFIG_PATH=/app/lib/pkgconfig:/app/share/pkgconfig:/usr/lib/pkgconfig:/usr/share/pkgconfig /home/thub/build/info.exult.Exult/.flatpak/repo cp * /app/share/exult/data
cp: cannot stat '*': No such file or directory
>>> Error: Child process exited with code 1
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:
Yes, this is the last module. See the attached JSON.
Also note that building outside of vscode does result in a launchable, but incomplete app. The "exult.cfg" file is also needed, but you can just create an empty file. I haven't figured out how to get the app to see it yet.
Yes, this is the last module. See the attached JSON. Also note that building outside of vscode does result in a launchable, but incomplete app. The "exult.cfg" file is also needed, but you can just create an empty file. I haven't figured out how to get the app to see it yet.
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: