[SailfishDevel] SailfishOS SDK December update available today.
Hello again, Today at 14:00 UTC we will publish new installers, package repositories and updated website documentation for our SailfishOS SDK version Alpha-1312-Qt5. If you already have an existing Alpha-Qt5 SDK installed you should see updates available icon in Qt Creator. If you don't have it installed, you can get the latest installer from www.sailfishos.orghttp://www.sailfishos.org. It is recommended to uninstall the old SDK and download a new installer. This update brings the long-awaited Mer ARM device support to Qt Creator and fixes issues with the application template regarding requirements for Harbour submissions. Qt Creator Sailfish kits now also support shadow building, which separates the different architecture builds from each other negating the need to always clean the build directory when switching between ARM and i486 kits. A couple of things you should be aware of: - Like before, in this update the build engine, emulator and targets are re-installed so you will lose all changes you may have made in those - however, if your application packaging is done correctly, rebuilding your projects should reinstall the packages you have been using. - All customization done to SDK (adding new package repositories, adding custom targets, additional source paths) will be removed during the installation process so make your own backup of those before starting the update. - If you import existing projects made with a previous version of the Sailfish OS SDK, make sure you select the correct kit in the project configuration step. Both ARM and i486 kits are available. - Windows users need to install VC10 runtime from http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or Installer will ask for admin rights during installation. - Package repository structure on SailfishOS.org has changed to be closer to the released Jolla phone repositories, so previous SDK installations will not work. - For more information, please see SDK Alpha-Qt5 known issues list at: https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues. Here are the release notes of this update. Installer: * Setting the additional application source folder now actually works. This setting can be used to specify a project location that is outside of your home directory. SailfishOS SDK IDE: * Qt Creator updated to version 2.8.1-3 * Qt Creator uses new wizard to create Mer ARM device, device creation is described on https://sailfishos.org/develop-firstapp-article.html in section 'Create a connection to Mer ARM device' * Shadow building is supported, you can now safely build applications for both architectures without them clashing. * Shadow building is on by default for each new project, but can be turned off in project's settings. * Latest SDK Application template is integrated so Harbour application requirements can be more easily fulfilled. * User settings are now stored in a new directory (Linux/OSX: $HOME/.config/SailfishAlpha3, Windows:C:\users\username\AppData\Roaming\SailfishAlpha3) so deleting old settings directory is not mandatory. Templates/examples/tutorials * Templates are updated with the latest SDK Application template. * Quite a few Qt5 tutorial applications were ported to Sailfish OS, they can be found from ~/SailfishOS/tutorials and they can be used to study Sailfish OS application behaviour. Each tutorial's project directory has a README.md file which contains notes from a developer when porting the application from Desktop QML to Sailfish OS. Some of the notes might be outdated. SDK Maintenance Tool: * Installer version updated to 1.4.0-2. Documentation: * Documentation is updated with latest available versions. Documentation may contain references to Qt 5.0 - please see known issues list at: https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues. Build Engine: * Shadow building creates separate build directories outside your project directory named build-PROJECTNAME-KITNAME-[Debug|Release] * The RPM packages for your project are also created under the shadow build directory * Build Engine will not treat missing qtc_ macros in spec file as fatal. SailfishOS Emulator: * Emulator software is updated to match Jolla Phone release 1.0.1-10 Laadunjärvi. * SSH login password for nemo user can be set with Developer settings in Settings application. * Package repositories can be refreshed with Developer settings in Settings application. * Icon sizes are matched to Harbour requirements. SailfishOS Targets: * Both i486 and ARM target builds based on updated Jolla baseline. If you encounter any issues, please report them to Sailfish developers mailing list at devel@lists.sailfishos.org Happy hacking, The Jolla SDK Team ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] A new Jolla phone user - after 2 days of use
Henry Kwong henrykw...@helsinkinet.fi writes: Hi, Moving from N9/Meego two days ago, I find Jolla/Sailfish very easy to use, and have some feedback (wishlist?). I hope this is the right place for this feedback, otherwise please point me to the correct place. Right now it's probably one of the better places to leave feedback :) It'll reach the appropriate people, I'll comment on a few items. Android Support: 1. Whatsapp address book does not work - currently all my Whatsapp Contacts are empty. Understand this is due to Whatsapp on Android cannot reach Jolla's phone book - can this be fixed? This is a known issue, and on our TODO list. Once we push that update you'll be able to _read_ your Sailfish contacts from Android applications, though write support will be disabled for security reasons for now. 2. Would be great if Android apps can appear as individual/independent apps instead of a single Virtual Machine which all Android apps live inside. We've been thinking about that for a while, but it's not trivial -- it's an Android architectural issue we either need to live with, or find a hack around. Generic: 1. There will be more users wanting to provide feedback - there will need to be an easier way to submit feedback (even from inside the phone - maybe an App?) which is publicly viewable so others would know it has been submitted (and can vote on it). We're working on that. Bernd ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] A new Jolla phone user - after 2 days of use
Bernd Wachter schreef op 2013-12-13 16:14: Henry Kwong henrykw...@helsinkinet.fi writes: ... Android Support: 1. Whatsapp address book does not work - currently all my Whatsapp Contacts are empty. Understand this is due to Whatsapp on Android cannot reach Jolla's phone book - can this be fixed? Maybe not for whatsapp, but for other apps this is really good! I hate those Android apps that need access to my personal data. Now I can fake them! r wim ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] A new Jolla phone user - after 2 days of use
Sailfish/Platform specific: 1. From Lock Screen, swiping-up should bring me to Home screen, but it often brings up the Events screen even if there is no notifications/events. Events screen appears only if you start the gesture from below the screen. If you want Home screen, start inside the screen area. Jolla Store: 1. Jolla App store feels a bit confusing - dont really know what apps are there as the only clear catalog available is the list of apps built by Jolla - all other Apps are scattered If you swipe left you get the Categories view that contains all the apps listed in specific categories. It took me also some time before I noticed it :) -- Janne ___ SailfishOS.org Devel mailing list
[SailfishDevel] SDK 13.12.2013 nothing provides libgudev-1.0.so.0
Hi I upgraded the SDK on my Mac with today's release. However the build of my current project now fails with: Problem: nothing provides libgudev-1.0.so.0 needed by upower-0.9.21+git1-1.1.1.i486 Solution 1: do not install telepathy-ring-devel-2.3.12-1.7.1.i486 Solution 2: break upower-0.9.21+git1-1.1.1.i486 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): c error: Failed build dependencies: telepathy-ring-devel is needed by landed25_QT5-0.1-1.i586 On my PC which has the previous SDK, I can find libudev1 in the Sailfish Control Center. Any ideas? Grüsse Chris ___ SailfishOS.org Devel mailing list
[SailfishDevel] Building/Deploying app fails with 1312 SDK
Hello, I just completely removed my old SDK with the SDK Maintenance tool (and also removed $HOME/.scratchbox2 as the installer of the new SDK version suggested, I also removed the Mer SDK VM and Emulator VM of the old SDK version in the Virtualbox Manager) and installed the new 1312 SDK. When I tried to build my simple, little multiplication tables practising application Quick Clamshell it failed with the following messages in the Compile Output pane: Loading repository data... Reading installed packages... 'pkgconfig(Qt5Core)' not found in package names. Trying capabilities. 'qt5-qtcore-devel' providing 'pkgconfig(Qt5Core)' is already installed. 'pkgconfig(Qt5Qml)' not found in package names. Trying capabilities. 'qt5-qtdeclarative-devel' providing 'pkgconfig(Qt5Qml)' is already installed. 'pkgconfig(Qt5Quick)' not found in package names. Trying capabilities. 'qt5-qtdeclarative-qtquick-devel' providing 'pkgconfig(Qt5Quick)' is already installed. 'pkgconfig(qdeclarative5-boostable)' not found in package names. Trying capabilities. 'mapplauncherd-qt5-devel' providing 'pkgconfig(qdeclarative5-boostable)' is already installed. Resolving package dependencies... Nothing to do. Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.asdslT Project WARNING: qdeclarative-boostable not available; startup times will be slower 18:41:33: The process $HOME/.config/SailfishAlpha3/mer-sdk-tools/MerSDK/SailfishOS-i486-x86/qmake exited normally. 18:41:33: Starting: $HOME/.config/SailfishAlpha3/mer-sdk-tools/MerSDK/SailfishOS-i486-x86/make Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.ya8VtM make: Nothing to be done for `first'. 18:41:35: The process $HOME/.config/SailfishAlpha3/mer-sdk-tools/MerSDK/SailfishOS-i486-x86/make exited normally. 18:41:35: Emulator is already running. Nothing to do. 18:41:35: Deploying rpm package... 18:41:35: Starting: $HOME/.config/SailfishAlpha3/mer-sdk-tools/MerSDK/SailfishOS-i486-x86/deploy --pkcon Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.jVTaWB + umask 022 + cd /home/mersdk/Coding/ClamshellSailfish/build-Quick2Clamshell-MerSDK_SailfishOS_i486_x86-Release + '[' /home/deploy/installroot '!=' / ']' + rm -rf /home/deploy/installroot ++ dirname /home/deploy/installroot + mkdir -p /home/deploy + mkdir /home/deploy/installroot + LANG=C + export LANG + unset DISPLAY + rm -rf /home/deploy/installroot + export QT_SELECT=5 + QT_SELECT=5 + make install INSTALL_ROOT=/home/deploy/installroot install -m 755 -p Quick2Clamshell /home/deploy/installroot/usr/bin/Quick2Clamshell : /home/deploy/installroot/usr/bin/Quick2Clamshell install -m 755 -p /home/mersdk/Coding/ClamshellSailfish/Quick2Clamshell/main.qml /home/deploy/installroot/usr/share/Quick2Clamshell/ : /home/deploy/installroot/usr/share/Quick2Clamshell/main.qml cp -f -R /home/mersdk/Coding/ClamshellSailfish/Quick2Clamshell/pages /home/deploy/installroot/usr/share/Quick2Clamshell/ cp -f -R /home/mersdk/Coding/ClamshellSailfish/Quick2Clamshell/cover /home/deploy/installroot/usr/share/Quick2Clamshell/ install -m 755 -p /home/mersdk/Coding/ClamshellSailfish/Quick2Clamshell/main.qml /home/deploy/installroot/usr/share/Quick2Clamshell/ : /home/deploy/installroot/usr/share/Quick2Clamshell/main.qml install -m 755 -p /home/mersdk/Coding/ClamshellSailfish/Quick2Clamshell/Quick2Clamshell.desktop /home/deploy/installroot/usr/share/applications/ : /home/deploy/installroot/usr/share/applications/Quick2Clamshell.desktop + /usr/lib/rpm/find-debuginfo.sh --strict-build-id /home/mersdk/Coding/ClamshellSailfish/build-Quick2Clamshell-MerSDK_SailfishOS_i486_x86-Release/ extracting debug info from /home/deploy/installroot/usr/bin/Quick2Clamshell 12 blocks + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/meego/brp-compress + /usr/lib/rpm/meego/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/meego/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump + /usr/lib/rpm/brp-python-bytecompile + /usr/lib/rpm/meego/brp-python-hardlink + /usr/lib/rpm/meego/find-docs.sh /home/deploy/installroot + /usr/lib/rpm/meego/brp-java-repack-jars Processing files: Quick2Clamshell-0.1-1.i586 error: File not found: /home/deploy/installroot/icons RPM build errors: error: File not found: /home/deploy/installroot/images error: File not found: /home/deploy/installroot/usr/share/Quick2Clamshell/images File not found: /home/deploy/installroot/icons File not found: /home/deploy/installroot/images File not found: /home/deploy/installroot/usr/share/Quick2Clamshell/images receiving incremental file list sent 8 bytes received 87 bytes 190.00 bytes/sec total size is 0 speedup is 0.00 rsync: change_dir /home/nemo/RPMS failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1637) [Receiver=3.1.0] rsync: [Receiver] write error: Broken pipe (32) Command failed: A filename to install is required 18:41:38: The process
Re: [SailfishDevel] Building/Deploying app fails with 1312 SDK
On 13.12.2013 20:02, superpelican wrote: Hello, I just completely removed my old SDK with the SDK Maintenance tool (and also removed $HOME/.scratchbox2 as the installer of the new SDK version suggested, I also removed the Mer SDK VM and Emulator VM of the old SDK version in the Virtualbox Manager) and installed the new 1312 SDK. When I tried to build my simple, little multiplication tables practising application Quick Clamshell https://bitbucket.org/Superpelican/quick_clamshell it failed with the following messages in the Compile Output pane: Hi, did this build in the previous 1310 release of the SDK? The application seems to use the old way of specifying a sailfishapplication, since it doesn't use libsailfishapp, which is the new (since 1310 installer) and recommended way of creating applications for Sailfish OS. Before trying to build your project with 1312 be sure to clean all previous build results from the project directory. Your bitbucket repository has lots of build generated files (like the application binary) that should not be there. + QT_SELECT=5 + make install INSTALL_ROOT=/home/deploy/installroot install -m 755 -p Quick2Clamshell /home/deploy/installroot/usr/bin/Quick2Clamshell : /home/deploy/installroot/usr/bin/Quick2Clamshell install -m 755 -p /home/mersdk/Coding/ClamshellSailfish/Quick2Clamshell/main.qml /home/deploy/installroot/usr/share/Quick2Clamshell/ : /home/deploy/installroot/usr/share/Quick2Clamshell/main.qml cp -f -R /home/mersdk/Coding/ClamshellSailfish/Quick2Clamshell/pages /home/deploy/installroot/usr/share/Quick2Clamshell/ cp -f -R /home/mersdk/Coding/ClamshellSailfish/Quick2Clamshell/cover /home/deploy/installroot/usr/share/Quick2Clamshell/ install -m 755 -p /home/mersdk/Coding/ClamshellSailfish/Quick2Clamshell/main.qml /home/deploy/installroot/usr/share/Quick2Clamshell/ : /home/deploy/installroot/usr/share/Quick2Clamshell/main.qml install -m 755 -p /home/mersdk/Coding/ClamshellSailfish/Quick2Clamshell/Quick2Clamshell.desktop /home/deploy/installroot/usr/share/applications/ : /home/deploy/installroot/usr/share/applications/Quick2Clamshell.desktop + /usr/lib/rpm/find-debuginfo.sh --strict-build-id /home/mersdk/Coding/ClamshellSailfish/build-Quick2Clamshell-MerSDK_SailfishOS_i486_x86-Release/ ... Processing files: Quick2Clamshell-0.1-1.i586 error: File not found: /home/deploy/installroot/icons That File not found is the initial problem. RPM build errors: error: File not found: /home/deploy/installroot/images error: File not found: /home/deploy/installroot/usr/share/Quick2Clamshell/images File not found: /home/deploy/installroot/icons File not found: /home/deploy/installroot/images File not found: /home/deploy/installroot/usr/share/Quick2Clamshell/images Looking at the make install output from earlier in the log, we can see that the /icons and /images directories are not installed, leading to the initial problem. The output below comes just because the build engine tries to copy files to the emulator, but there are no files it can find because the build failed already. The build/deploy process should have ended to the RPM build errors and seems like something to fix in future SDK releases. receiving incremental file list sent 8 bytes received 87 bytes 190.00 bytes/sec total size is 0 speedup is 0.00 rsync: change_dir /home/nemo/RPMS failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1637) [Receiver=3.1.0] rsync: [Receiver] write error: Broken pipe (32) Command failed: A filename to install is required 18:41:38: The process $HOME/.config/SailfishAlpha3/mer-sdk-tools/MerSDK/SailfishOS-i486-x86/deploy exited with code 3. Error while building/deploying project Quick2Clamshell (kit: MerSDK-SailfishOS-i486-x86) When executing step 'Rpm' 18:41:38: Elapsed time: 00:06. I believe this isn't related to my app, but rather a problem with the new SDK, so I thought I'd post it on the ML ;) There is something incorrect in the way you have specified the RPM packaging for your application. Looking at your .yaml file, its files section specifies that /images and /icons should be added to the RPM package. That means images and icons directories in the root of the filesystem. I'm sure you don't really want them to be there, but somewhere under /usr/share/applicationname instead. Please take a look at the following links, which [1] describe what kind of requirements there are for an application you might want to ship to the Harbour one day and [2] in detail describe creating an installation package (RPM) for your application. [1] https://harbour.jolla.com/faq [2] https://sailfishos.org/develop-packaging-apps.html Also, take a while to study the latest application template File-New Project and the example and tutorial applications that come with the 1312 SDK to see how to use libsailfishapp
Re: [SailfishDevel] SDK 13.12.2013 nothing provides libgudev-1.0.so.0
Hi Juha Thanks for your help so far. The machine for which I reported this problem is an MBA running OSX 10.8.4 I have now deinstalled and reinstalled the Sailfish SDK several times with no joy. I always end up with a Qt Creator that has no Sailfish Templates, no Kits, and sees no Qt versions. Just for fun, I tried the same on my old Mac Pro 2008 Tower, which despite its age is running 10.9 Mavericks. On this machine I brutally deleted Sailfish and the .scratchbox2 at the command line, and then did a fresh install of todays SDK. This gave me a working Sailfish Qt Creator, with a Sailfish Template, and auto-detected MerSDK kits and Qt 5.1.0 kits Interestingly, in the SDK Control Center, no Telepathy packages were initially recognised until I pressed the refesh button. After that telepathy-ring-devel successfully installed. After this, I saw your latest mail, with the suggestion to remove ~/.config/SailfishAlpha3 So back on the MBA, I did the following Apple-Pip:~ christopherlamb$ rm -r ~/.config/SailfishAlpha3 Apple-Pip:~ christopherlamb$ rm -r ~/.config/SailfishAlpha2 Apple-Pip:~ christopherlamb$ rm -r ~/.config/SailfishAlpha Apple-Pip:~ christopherlamb$ rm -r .scratchbox2 Apple-Pip:~ christopherlamb$ rm -r SailfishOS/ Then I repeated the install (13-12-2013) After that I got a QtCreator that had the usual Sailfish templates, kits, and Qt Versions. So far so good. However on trying to build my app, I get the identical errors about libgudev-1.0.so.0 If I press the refresh button in the SDK Control Center I get Operation Progress finished: Refreshing target repos SailfishOS-i486-x86 - exited with status 4 Error code: Unrecognized error Error message: Empty reply from server Please see the above error message for a hint. Skipping repository 'jolla' because of the above error. Retrieving repository 'mer-tools' metadata [.done] Building repository 'mer-tools' cache [done] Repository 'sdk' is up to date. Some of the repositories have not been refreshed because of an error. So, in summary, I have 1) an OSX Mavericks Mac Pro Tower that upgraded first time, and is able to install telepathy-ring-devel 2) an OSX 10.8.4 MBA that is resisting all attempts... As I do most of my Sailfish development on the train, the Mac Pro Tower is not really an option ... Chris Zitat von christopher.l...@thurweb.ch: Hi Juha I have to confess that I upgraded via the maintenance tool. Now I have done a complete de-install, including removing the hidden .scratchbox2 directory. Then I re-downloaded and installed from https://sailfishos.org/develop.html Now I have a QtCreator that has no kits or Qt Versions. The hole is getting deeper and we are still digging. It is very definitely Friday the 13th Chris Zitat von Juha Kallioinen juha.kallioi...@jolla.com: On 13.12.2013 18:32, christopher.l...@thurweb.ch wrote: Hi I upgraded the SDK on my Mac with today's release. However the build of my current project now fails with: Problem: nothing provides libgudev-1.0.so.0 needed by upower-0.9.21+git1-1.1.1.i486 Solution 1: do not install telepathy-ring-devel-2.3.12-1.7.1.i486 Solution 2: break upower-0.9.21+git1-1.1.1.i486 by ignoring some of its dependencies Hi, looks like the package repositories have not been fully refreshed in your SDK. The telepathy-ring-devel version in the latest repository is telepathy-ring-devel-2.3.16-1.7.1.i486.rpm I just tested it on my Mac and verified that I can install telepathy-ring-devel. The Build Engine should refresh its repositories five minutes after it has been started. Could you reboot the MerSDK build engine and wait about 10 minutes, then try building again. Maybe something in the upgrade went wrong, it is recommended to first remove the old SDK and then install the 1312 version from a new installer. Best regards, Juha ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Sailfish app to monitor network traffic ?
Hi Winfried, In Settings app you can go to System settings - Data counters. This will show you Sent/Received for Mobile data (Home network, Roaming) and WLAN. Maybe others, but these are what I can currently see. It does not show current speed, only the totals since last reset. Best regards, Oskari On 12/14/2013 01:58 AM, W. Dobbe wrote: Hi all, A question to those who already received their Jolla phone: is there an application to monitor the amount of data going over the network, especially over the 3G/4G connection ? If not, is there already someone developing one? Otherwise I might have a go at it. regards, Winfried ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
