55519b1855
I am not sure why, but cargo does not like it if flatpak-builder and gnome Builder try to use the same target/ directory, even though the environment should be almost identical. The only difference is that Builder uses flatpak build instead of flatpak-builder as far as I can see.
34 lines
1.3 KiB
Bash
Executable File
34 lines
1.3 KiB
Bash
Executable File
#! /usr/bin/sh
|
|
|
|
export MANIFEST_PATH="org.gnome.Podcasts.json"
|
|
export RUNTIME_REPO="https://sdk.gnome.org/gnome-nightly.flatpakrepo"
|
|
export FLATPAK_MODULE="gnome-podcasts"
|
|
export CONFIGURE_ARGS=""
|
|
export DBUS_ID="org.gnome.Podcasts"
|
|
export BUNDLE="org.gnome.Podcasts.Devel.flatpak"
|
|
|
|
flatpak-builder --stop-at=${FLATPAK_MODULE} --keep-build-dirs --force-clean app ${MANIFEST_PATH}
|
|
# https://gitlab.gnome.org/World/podcasts/issues/55
|
|
# Force regeneration of gresources regardless of artifacts chage
|
|
flatpak-builder --run app ${MANIFEST_PATH} glib-compile-resources --sourcedir=podcasts-gtk/resources/ podcasts-gtk/resources/resources.xml
|
|
|
|
# Build the flatpak repo
|
|
flatpak-builder --run app ${MANIFEST_PATH} meson --prefix=/app build
|
|
flatpak-builder --run \
|
|
--env=CARGO_TARGET_DIR="target_build/" \
|
|
app ${MANIFEST_PATH} \
|
|
ninja -C build install
|
|
|
|
# Run the tests
|
|
xvfb-run -a -s "-screen 0 1024x768x24" \
|
|
flatpak-builder --run \
|
|
--env=RUSTFLAGS="--cfg rayon_unstable" \
|
|
--env=CARGO_HOME="target/cargo-home" \
|
|
--env=CARGO_TARGET_DIR="target_test/" \
|
|
app ${MANIFEST_PATH} \
|
|
cargo test -- --test-threads=1
|
|
|
|
# Create a flatpak bundle
|
|
# flatpak-builder --finish-only app ${MANIFEST_PATH}
|
|
# flatpak build-export repo app
|
|
# flatpak build-bundle repo ${BUNDLE} --runtime-repo=${RUNTIME_REPO} ${DBUS_ID} |