Slides from the talk. Not sure how useful they are without the talk and discussion. Covers steps of getting started using Hello World Pro project so that you could get a package that passes Jolla Harbour acceptance criteria for sure and explains what's built how and where during the app process.

1. Getting Started with coding for
Jolla Sailfish OS
Artem Marchenko
@AgileArtem
29.03.2014, Tampere, Finland
29.03.14
@AgileArtem
http://www.codingsubmarine.com

2. Today
• Quick start on emulator
– And how to run on device
• Structure of the build process and artifacts
• Packaging for app store
• Troubleshooting / debugging
• Support channels and further questions
29.03.14
@AgileArtem
http://www.codingsubmarine.com

3. QUICK START
29.03.14
@AgileArtem
http://www.codingsubmarine.com

4. Preparing SDK
1. Get Python (project renaming script will need it)
2. Install SDK https://sailfishos.org/develop.html
3. Run its Updater ( Help -> Start Updater)
4. Get HelloWorld Pro from
https://github.com/amarchen/helloworld-pro-
sailfish and open it (you need a project for Updating
part of SDK)
– Configure for all available platforms
5. Rename project into harbour-my-great-app via
rename-to-my-project.py
6. Start Mer build machine (can take a couple of clicks)
7. Install more updates via Sailfish OS tab
29.03.14
@AgileArtem
http://www.codingsubmarine.com

5. Starting app on emulator
• Set i486
platform as
active
• Deploy as
RPM
• Run
subproject src
29.03.14

6. Start emulator and app
29.03.14

7. Running tests on emulator
• Run
/usr/share/tst-
harbour-my-
great-
app/runTestsOnD
evice.sh
– As README.md says
29.03.14
@AgileArtem
http://www.codingsubmarine.com

8. Connecting device
• https://sailfishos.org/develop-firstapp-article.html covers it
well
– Works fine on WiFi
– Couldn’t make it work via USB
29.03.14
@AgileArtemhttp://www.codingsubmarine.co
m

9. Then run on device
• Same as on
emulator
• Just don’t
forget to
select
armv7
platform
29.03.14

10. Continue in QML
29.03.14
@AgileArtem
http://www.codingsubmarine.com

11. STRUCTURE OF THE BUILD PROCESS
29.03.14
@AgileArtem
http://www.codingsubmarine.com

12. Project directories
Your PC
Mer build
machine
Jolla device/
emulator
/Users/artem/
projects/great-app/
/home/mersdk/
projects/great-app/
/home/mersdk/
projects/build-great-
app-MerSDK.../
/home/deploy/
installroot/usr/share/
harbour-great-app/...
/home/deploy/
installroot/usr/bin/
harbour-great-app
/usr/bin/harbour-
great-app
/usr/share/harbour-
great-app/...
Same dir
Compile
INSTALLS
phase of
qmake build
Default comes from
~/mersdk/targets/Sailfish.../usr/
share/qt5/mkspecs/
features/sailfishapp.prf
RPM
package
29.03.14
@AgileArtem
http://www.codingsubmarine.com

13. Building-packaging
harbour-great-
app.yaml
gstreamer-devel
libresourceqt5
sailfishapp
Build-time
dependencies
libsailfishapp
Runtime
dependencies
/usr/bin/harbour-great-app
/usr/share/icons/...
/usr/share/harbour-great-app/..
Files in main
package
harbour-great-
app-tests
subpackage
/usr/bin/tst-harbour-great-app
/usr/share/tst-harbour-great-app/...
harbour-great-
app-fake
subpackage
Garbage other packages
don't need
great-app.pro
source files
resources
harbour-great-
app.spec
Extra detais
Tell we are not
requiring/providing
anything not allowed
Pass QMake vars
E.g. version number
Or dir with platform-specific
resources
for bundling into app
/home/deploy/installroot/
usr/bin/harbour-great-app
...
on Mer build machine
INSTALLS
harbour-great-app-0.1-1.armv7hl.rpm
harbour-great-app-test-0.1-1.armv7hl.rpm
harbour-great-app-fake-0.1-1.armv7hl.rpm
RPM packaging
To App Store!
29.03.14
@AgileArtem
http://www.codingsubmarine.com

14. PACKAGING FOR APP STORE
29.03.14
@AgileArtem
http://www.codingsubmarine.com

15. Build RPM package
1. Choose ARMV7
platform
2. *Clean* not to package
i486 binaries
3. Deploy RPM

16. Validate

17. Submit to harbour
• http://harbour.jolla.com
• Icon templates can be found at
https://sailfishos.org/apps_icons.html
– As mentioned in README.md
• You’ll need screenshots
– Use Screenshot or SailshotMe app on device
– Upload to Dropbox via Sailbox app
29.03.14
@AgileArtem
http://www.codingsubmarine.com

18. TROUBLESHOOTING DEPLOYMENTS
29.03.14
@AgileArtem
http://www.codingsubmarine.com

19. Troubleshooting failed deployments
and not runnable apps
• Examine the content of the Mer machine and
emulator directories. And device too if you need
• Is covered well at https://sailfishos.org/develop-
faq.html
• Mer: ssh -p 2222 -i
~/SailfishOS/vmshare/ssh/private_ke
ys/engine/root root@localhost
• Emulator: ssh -p 2223 -i
~/SailfishOS/vmshare/ssh/private_ke
ys/SailfishOS_Emulator/root
root@localhost
• Real device: ssh nemo@192.168.1.38
– Address and password from the Developer Settings
on device
29.03.14
@AgileArtem
http://www.codingsubmarine.com

20. Debugging
• C++ debugging doesn’t work from IDE
• If you comfortable with GDB, it is supposed to
work
• Rumors tell that QML debugging does
– I failed to get it working
• Use logging
• Use automated tests
29.03.14
@AgileArtem
http://www.codingsubmarine.com

21. Getting support and further questions
• IRC: #sailfishos on freenode
(irc.freenode.net)
• devel-subscribe@lists.sailfishos.org
• This slideset –
http://www.codingsubmarine.com/tag/class/
@AgileArtem on twitter
29.03.14
@AgileArtem
http://www.codingsubmarine.com

22. Artem needs help
• I want to make a Telegram client, help me
understand what the biz model for it could be
like
– And for a collaboration of several authors?
• Push @JollaHQ to communicate more about
business opportunities for small devs
• Contribute to HelloWorld Pro, Log4Qt Demo
• Try my apps in Jolla app store and review
them (Flashlight, Quick Launcher)
29.03.14
@AgileArtem
http://www.codingsubmarine.com