answered
2014-02-23 22:10:09 +0300
Update:
Please check the public repos in the other answer, both versions Windows and Linux.
Hi,
Ok I think I have something:
Though I'm unsure if it makes any difference, I'm using GNU/Linux Mint 15 x64 to do the Ambiance and at the time, I'm being successful deploying the RPM and applying the Ambiance:
- I updated the SDK:
- SailfishOS option on the left, Update Engine
- Qt Creator main window, bottom right, update button
- I modified the template.spec file
- manually created the "translations" directory in the shadow build directory that is defined in the project settings
- the template builds properly with Qt Creator
- I'm using Release > Deploy as RPM Package - a coherent popup shows up in Qt Creator claiming there's no executable to run, close that
- connecting to the phone over SSH:
- I check the /usr/share/ambience directory on the Jolla mobile and no update
- I turn the phone off, then on again and /usr/share/ambience (it's actually spelled with an "e") has the directory there
- I'm able to select the ambiance from the Gallery and apply it
Next, Removing and adding again:
- I swap the template back to another ambiance
- I remove the template from the pulley menu options
- /usr/share/ambience files remain there, I manually remove them
- I re-deploy the template after a clean on Qt Creator
- I deploys, same as before, no new files in /usr/share/ambience, turn the phone off, on again, ambiance is available again.
Please test and see if it works for you as well.
full template project on bitbucket:
https://bitbucket.org/wickwire/sailfishos-jolla-ambience-linux
template.spec file below (the only file I changed, apart from the jpg background)
Name: ambience-template
Summary: Template ambience
Version: 0.0.1
Release: 1
Group: System/GUI/Other
License: TBD
Source0: %{name}-%{version}.tar.bz2
BuildRequires: qt5-qttools
BuildRequires: qt5-qttools-linguist
BuildRequires: qt5-qmake
Requires: ambienced
%description
This is a template ambience description
%package ts-devel
Summary: Translation source for template ambience
License: TBD
Group: System/GUI/Other
%description ts-devel
Translation source for a template ambience
%prep
%setup -q -n %{name}-%{version}
# >> setup
# << setup
%build
# >> build pre
# << build pre
%qtc_qmake5
%qtc_make %{?_smp_mflags}
# >> build post
# << build post
%install
rm -rf %{buildroot}
# >> install pre
# << install pre
%qmake5_install
# >> install post
# << install post
%files
%defattr(-,root,root,-)
%{_datadir}/ambience/ambience-template/ambience-template.ambience
%{_datadir}/ambience/ambience-template/sounds.index
%{_datadir}/ambience/ambience-template/images/*
%{_datadir}/ambience/ambience-template/sounds/*
%{_datadir}/translations/ambience-template_eng_en.qm
%files -n ambience-template-ts-devel
%defattr(-,root,root,-)
%{_datadir}/translations/source/ambience-template.ts
Hi Eische, (I'm not a developer either). I'm interested in this as well. The TOH Dev Kit does contain some rather garbled, poorly laid out information, but still doesn't tell you how to actually package an RPM. I tried formatting and cleaning the notes up to make them understandable, I understand many of the terms used but concise instructions would be better - I think we will have a bit of a wait on this one. I found a few websites giving a 'how-to' create RPM packages, but many were for Fedora (but similar logic may well apply, but I don't know for sure) and I'm also not using the Sailfish SDK - the GUI is 'overload' for me aka steep learning curve!
Spam Hunter ( 2014-02-08 18:32:27 +0300 )editI voted this question up because I think creating good ambiences is totally different from creating good software; it takes other people to do it, and therefore should be supported through other means (like, for example, a fool-proof RMP-builder that only takes image and sounds as input...) See also the discussion at: https://together.jolla.com/question/14852/jolla-store-extension-section-for-ambiences/
ossi1967 ( 2014-02-09 13:26:37 +0300 )editHi, I'm also interested in this. So far, I have:
- the template is suited for Qt Creator, but on Linux I get an RPM build error (Run -> Deploy As an RPM Package)
- on Windows, the same project does build - in the shadow build directory, RPMs are placed
- after deploying, often the ambience doesn't show up in the Gallery
- when it did, I haven't yet managed to figure out how it works
- the procedure seems to have a connection to the jolla store
- files are placed in /usr/share/ambience/
wickwire ( 2014-02-19 23:44:08 +0300 )edit