Commit Graph

8 Commits

Author SHA1 Message Date
Maximilian Federle
b9002ab4da snap: Use kde-frameworks-5-core18-sdk to build
Use kde-neon's corresponding sdk snap instead of
build-packages.
2020-04-17 05:29:31 +02:00
Maximilian Federle
5b1bd22b30 snap: Use kde-neon extension
The kde-neon extension reduces our boilerplate in snapcraft.yaml
and reduces the snap size considerably, as we do not need to ship
any library that is already included in the kde-frameworks-5-core18
snap itself.

This limits qelectrotech builds to the architectures supported
by kde-frameworks-5-core18, i.e. only amd64.
2020-04-17 05:29:31 +02:00
Laurent Trinques
cc72bb6e06 Revert Update org.qelectrotech.QElectroTech.json not fixing Python's Tkinter need for qet-tb-generator 2020-04-15 08:44:29 +02:00
Laurent Trinques
3f2441eb8a Update org.qelectrotech.QElectroTech.json for Flatpak build 2020-04-15 07:55:18 +02:00
Mathieu Bridon
a16b505aa6 flatpak: Properly rename the appdata file
Adding the full file name was required, just like for renaming the
desktop files, unlike for renaming the icons.
2020-02-17 15:17:42 +01:00
Mathieu Bridon
975f0db7ec build: Add a Flatpak manifest
This allows building the master branch of QElectroTech with a simple
command:

$ flatpak-builder _build build-aux/flatpak/org.qelectrotech.QElectroTech.json
2020-02-14 14:43:49 +01:00
Mathieu Bridon
d26b189d3d build: Rename the packaging directory
The Linux and Windows packaging recipes don't have any restrictions on
where they have to be located. Snapcraft is the strictest on this.

Moving this to build-aux/ means we can have all the packaging recipes in
one place.
2020-02-14 14:43:36 +01:00
Mathieu Bridon
3f38f4b16c build: Move the Snap recipes
Snapcraft can find its build recipes in 2 places:

* a snap/ directory at the top of the sources;
* a build-aux/snap/ directory, since Snapcraft 3.3;

This commit moves from the former to the latter, so that we can group
all the packaging recipes together.
2020-02-14 14:43:36 +01:00