Re: [SailfishDevel] mersdk: Problem: nothing provides mesa-llvmpipe-libGL

[Juha Kallioinen]

On 18.08.2014 22:19, b...@xyz.de wrote:

Hi,

in mersdk trying to install development-package for GL:

[sdk] $ sb2 -t SailfishOS-armv7hl -m sdk-install -R
[sdk] # zypper in mesa-llvmpipe-libGL-devel

Problem: nothing provides mesa-llvmpipe-libGL = 9.2.5+git1-1.2.7 needed by 
mesa-llvmpipe-libGL-devel-9.2.5+git1-1.2.7.armv7hl
  Solution 1: do not install mesa-llvmpipe-libGL-devel-9.2.5+git1-1.2.7.armv7hl
  Solution 2: break mesa-llvmpipe-libGL-devel-9.2.5+git1-1.2.7.armv7hl by 
ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/c] (c):

Solution 2 obviously does not solve the problem: cannot find -lGL



Hello,

you've found a bug in the mesa packaging. The mesa-llvmpipe-libGL-devel 
package should not be available since we don't provide the corresponding 
library package.


Instead of libGL you should probably use mesa-llvmpipe-libEGL-devel or 
mesa-llvmpipe-libGLESv2-devel.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Error in linker

[Juha Kallioinen]

On 17.08.2014 01:33, Tone Kastlunger wrote:

To whom it might concern:
just encountered the following error :


/opt/cross/bin/armv7hl-meego-linux-gnueabi-ld: Errors encountered 
processing file moc_debotadbusservicehandler.o


/opt/cross/bin/armv7hl-meego-linux-gnueabi-ld: cannot size stub 
section: File truncated


/opt/cross/bin/armv7hl-meego-linux-gnueabi-ld: BFD (GNU Binutils) 
2.23.1 internal error, aborting at merge.c line 873 in 
_bfd_merged_section_offset



/opt/cross/bin/armv7hl-meego-linux-gnueabi-ld: Please report this bug.


as it says "please report this bug", here we go :)



Thanks for the report :)

Do you have the source code available that reproduces this?

Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Fwd: QtCreator issues

[Juha Kallioinen]

On 17.07.2014 00:41, Stijn Devriendt wrote:

Hi Juha,

Been debugging a bit more until I got this:
Breakpoint 1, 0x7fffeb54bd40 in QTime::QTime(int, int, int, 
int)@plt () from /usr/lib64/libkdecore.so.5

(gdb) bt
#0  0x7fffeb54bd40 in QTime::QTime(int, int, int, int)@plt () from 
/usr/lib64/libkdecore.so.5

#1  0x77de9be6 in call_init () from /lib64/ld-linux-x86-64.so.2
#2  0x77de9cca in _dl_init_internal () from 
/lib64/ld-linux-x86-64.so.2
#3  0x77dedd99 in dl_open_worker () from 
/lib64/ld-linux-x86-64.so.2

...

Hi thanks for debugging,

I can't figure out the reason yet, just a quick report.

I can reproduce the failure here in Sabayon KDE 14.07 version, but not 
in the GNOME version.


I could not reproduce it in Kubuntu 14.04 (also uses KDE, version 4.13.2).

One system library caught my eye, Sabayon loads libpng16.so.16 and 
Kubuntu loads libpng12.so.0, although I'm sure I've built Qt so that it 
would use the qt plugin and not system libpng. But maybe it doesn't 
affect that code path yet.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Fwd: QtCreator issues

[Juha Kallioinen]

Hi,

sorry to hear that.

Did the previous version 1406 or some earlier version work for you in the same 
host?

Please send core dump to me and if you could also provide an strace log of 
starting Qt Creator:

$ strace -o output.log -s 512 installdir/bin/qtcreator

Also please mention which Sabayon variant do you use, gnome/kde/xfce?

Best regards,
 Juha


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Stijn Devriendt [high...@gmail.com]
Sent: Wednesday, July 16, 2014 7:50 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Fwd: QtCreator issues

Hi,

I'm having segfaults when starting the Qt Creator from the July SDK:
kernel: qtcreator[3217]: segfault at a1d46 ip 000a1d46 sp 
7fff634493e8 error 14 in qtcreator[40+13000]

Issue is reproducible; OS is the latest Sabayon Linux 64bit.
I can send coredump on request.

Let me know if I can be of further assistance.

Regards,
Stijn
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] QTcreator.exe

[Juha Kallioinen]

On 18.06.2014 12:47, Vesa Arttijeff wrote:

Hi,

I installed Sallfish SDK 
(SailfishOSSDK-Alpha-1406-Qt5-windows-offline) to my Windows 8. I have 
Norton Antivirus on my machine.


Please check the attached document (as Word /ODT). Norton detected 
something weird in qtcreator.exe file. Is it just my local problem or 
something else?




Hi, for some reason I only received this mail on the mailing list just 
today.


I've scanned my files on this end with Bitdefender and clamav, but those 
did not detect any problems here.


Best regards,
 Juha


___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

[SailfishDevel] Sailfish OS SDK July update available tomorrow 12:00 UTC

[Juha Kallioinen]

Hello again,

Tomorrow (July 15th) at 12:00 UTC we will publish new installers and 
package repositories for our Sailfish OS SDK version Alpha-1407-Qt5.


If you already have an existing Alpha-Qt5 SDK installed you should see 
the Updates Available icon in Qt Creator. If you don't have a previous 
SDK installation you can get the latest installer from 
http://www.sailfishos.org.


It is recommended to uninstall the old SDK and download a new installer.

SDK content has been updated to match Jolla Release 1.0.8.19. Please see 
below for detailed information of the changes.


A couple of things you should be aware of:
- As 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.
- Any 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 to 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 the 
Installer will ask for admin rights during installation.
- Package repository contents have been updated and consequently using a 
previous SDK version with these package repositories is not supported.
- Supported host platforms can be found from: 
https://sailfishos.org/alpha_qt5_sdk_release_notes.html
- For more information, please see the SDK Alpha-Qt5 known issues list 
at: https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.


This is mainly a housekeeping release and here's the short summary of 
changes:


SDK IDE (Qt Creator)
- Fix bugs related to handling symlinked home directory or project 
directory. This change affects only Linux and Mac hosts.

- Updated component gallery sources in the Example projects
- Updated Sailfish Silica help documentation

Installer:
- Fix Sailfish template application source location in Mac installer. 
Mac users should check out the updated default template application, it 
has some changes that were missing in the previous installer.


SDK Build engine:
- Build targets refreshed to Jolla release 1.0.8.19 level.
- RPM repositories point to releases.jolla.com instead of 
releases.sailfishos.org.


SDK Control Center:
- No updates

Emulator:
- Emulator packages refreshed to Jolla release 1.0.8.19 level.
- RPM repositories point to releases.jolla.com.

Website:
- The Silica documentation at http://sailfishos.org/sailfish-silica/ 
updated to current level.


If you have any questions, feel free to either send an email to this 
mailing list: mailto:devel@lists.sailfishos.org or write it up in 
http://together.jolla.com and tag your issue with 'sdk'.


Happy hacking,
Jolla SDK Team.

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] SailfishOS SDK install to /opt

[Juha Kallioinen]

On 14.07.2014 11:13, Marcin M. wrote:
Forgot to tell: the user owning it is root (who owns the whole 
/opt/SailfishOS)...


If installed to /home, works correctly.



Ok that was the problem. You can still install it under /opt as long as 
you first create the install dir manually and then set the access rights 
correctly for your user.


For example like this:

$ sudo mkdir -p /opt/SailfishOS
$ sudo chown -R $USER /opt/SailfishOS

And then install the SDK under /opt/SailfishOS

Best regards,
 Juha
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Could not resolve the prototype ‘TextBaseItem’ of ‘TextBase’. (M301)

[Juha Kallioinen]

On 11.07.2014 23:26, Andrey Kozhevnikov wrote:
This is not error and just warning, and you can ignore it and continue 
developing.


That's correct. It's a warning from Qt Creator that it cannot provide 
the code completion suggestions for that class. It is a problem with the 
metadata that is provided with the SDK and that's something we need to 
improve in the future.


This does not affect building/compiling of your application.

Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] SailfishOS SDK install to /opt

[Juha Kallioinen]

On 12.07.2014 11:02, Marcin M. wrote:
Why do the mersdk/MerSDK and emulator/SailfishOS Emulator directories 
have 700 permissions? It makes the VMs unaccesible.


Those folder rights are correct. 700 means that the user has full 
read-write-exec rights to the directories. The SDK works only for a 
single user because of how the virtual machines get set up so you cannot 
have two or more users on the same machine using it. It also means that 
the user who installs it, needs to be the user that uses it.


It's hard to guess what might be the problem and if possible, I suggest 
a reinstall.


First uninstall the SDK and after that open up the VirtualBox manager UI 
and check that the MerSDK and SailfishOS Emulator virtual machines have 
really been removed. If they are still there, manually remove them. 
Furthermore before reinstalling, remove the configuration folder with: 
rm -rf ~/.config/SailfishAlpha4


Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Failed to load platform plugin "xcb".

[Juha Kallioinen]

On 14.07.2014 10:33, Jukka Heikkilä wrote:

Hi,

no. I don't think that I have installed any other bash versions, but 
bash ---versions gives:

GNU bash, versio 4.3.0(1)-release (armv7l-unknown-linux-gnueabi)
Copyright (C) 2013 Free Software Foundation, Inc.
Lisenssi GPLv3+: GNU GPL versio 3 tai uudempi 



So looks like it has been updated, but how? I don't have any memories 
that I have installed it from openrepos...


Ok that is the problem then. I also don't know how you've installed it, 
but I could guess that if you've ever configured openrepos to your 
phone, bash might have been installed as a dependency to some 
application from there.


You can see the package installation history by looking at the 
/var/log/zypp/history file on your device. Maybe that could give a clue 
when and how the updated bash has ended up there.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Failed to load platform plugin "xcb".

[Juha Kallioinen]

On 12.07.2014 21:10, Jukka Heikkilä wrote:

Hi folks!

During developing my program I have mostly used Emulator to run the 
app and sometimes also real device and testing has been worked fine on 
both. Now I faced the next problem with real device. When I press run 
from Qt Creator, it will normally compile the app and transfer it to 
real device. However next error will be shown on Application Output:


Connecting to device...
Failed to load platform plugin "xcb". Available platforms are:
hwcomposer
eglfs
minimal
wayland-egl
wayland

Remote application crashed: Process killed by signal

I would like to ask, have you faced similar problems with it? Have you 
any idea how to fix this? From IRC logs and mail list I didn't found 
solution how to fix it (at least not sufficiently clear in related to 
my skills). On Emulator my app run fine.


Have you possibly installed another bash version for example from 
openrepos? Or have you done any customization in your .bashrc or .profile?


This failure is a symptom of the shell environment not being set 
correctly over ssh when Qt Creator starts your application. The default 
bash that comes with Sailfish has been compiled with a non-standard 
option to source the user's dotfiles even in a non-interactive session. 
If you've installed a newer bash (I understand that bash 4 is available 
from operepos), then it will cause this kind of an issue when executing 
binaries over ssh.


Another user was having a similar problem and we sorted it out in 
#sailfishos a few weeks ago:


http://merproject.org/logs/%23sailfishos/%23sailfishos.2014-07-01.log.html#t2014-07-01T11:12:04

Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Debug issue from inside the QtCreator IDE

[Juha Kallioinen]

On 09.07.2014 16:15, Iosif Hamlatzis wrote:

https://www.dropbox.com/s/t6wsbj6sohyq8wd/debug.png



My system is WindowsXP SP3 and I am using the QtCreator IDE to deploy 
my game and hopefully debug it.


As you can see from the screenshot (above link) the build and deploy 
process succeeds (both for the emulator and the actual device).


The problem is I cannot debug my code from inside the IDE either 
inside the emulator or the actual device. When I select to debug the 
IDE starts building the game, then it deploys it and then a pop-up 
dialogue appears requesting an executable (executable files for 
Windows are .exe - .com - .cmd - .vbs - .bat). BUT the build process 
doesn't produce any executable file.


Has anyone managed under Windows (any version) to debug on the 
emulator or device his/her app from inside the IDE?


Debugging does not work in Windows XP, but not because of this problem. 
I can try to explain the problem you are seeing below in case you're 
interested. For Windows XP the ultimate problem is that the gdb binaries 
which can be found from the installdir/bin/gdb-*-meego-linux-gnu*.exe 
are incompatible with Windows XP and can not be run. Windows XP is not 
on the list of supported operating systems, which can be seen in [1].


[1] https://sailfishos.org/alpha_qt5_sdk_release_notes.html

I've created a bug about running gdb in Windows XP to our bug tracker, 
but it's not going to get fixed any time soon.


Now to the problem you're experiencing:

I've understood from your earlier posts that you are working on an SDL 
project. This (to me) means that you've had to create a project either 
from scratch or you have heavily modified the default Sailfish template 
project. Without seeing sources, I can only guess what might be the 
cause for this behavior.


That dialog shown in your screenshot is Qt Creator telling you that it 
does not know which binary to run after deployment. The basic 
requirements for Qt Creator to recognize the application binary are:


Project template type is "app" and the executable binary is either the 
same as the project name or specified by the TARGET variable in the .pro 
file.


If your project's TEMPLATE is other than app and/or you haven't 
specified TARGET, then Qt Creator does not know which binary it needs to 
run after it has deployed the project.


If you don't have the TEMPLATE specified, it is by default "app".

In order to debug anything, Qt Creator would need to know which binary 
it needs to debug. So that is the first step. Additionally it needs to 
run the binary on the remote device (or Emulator), so it needs to know 
what the remote binary will be after deployment. When it knows these, it 
would be able to start a debugging session, but on Windows XP it would 
fail at this point when launching gdb.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Cannot open projects after updating SDK

[Juha Kallioinen]

On 25.06.2014 00:21, Matthias Barmeier wrote:

Hi,

after updating my SDK I cannot open my projects any more.
QtCreator shows a message saying that no kits are available.

Does anyone know how to fix this ?



Hi,

you could try removing the old configuration files and see if that helps.

I assume you are a Linux or Mac user in which case you can remove the 
configuration files like this:


1) Make sure Qt Creator is not running
2) rm -rf $HOME/.config/SailfishAlpha4
3) Start Qt Creator again

Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Recent update improvements?

[Juha Kallioinen]

On 23.06.2014 18:52, Chris Walker wrote:

On Mon, 23 Jun 2014 16:51:17 +0300
Juha Kallioinen  wrote:


On 23.06.2014 16:38, Chris Walker wrote:

What was the reason for 'improving' the Emulator? By improvement, I
mean that there is now only one option and that is to shut it down
rather than saving the state? I consider that to be a right PITA.


The reason was to prevent accidental state savings.

You can still save its state by opening the VirtualBox manager window
and selecting the menu option (Close/Save state) for the running
Emulator. It's a bit more difficult to choose and that should make it
a more deliberate action.

Just to be clear on this, you are referring to the option to save a
single state with Ctrl-V rather than a permanent change to re-enable
the option to save the state.


I think so... how do these differ in operation? I think they do exactly 
the same thing?


If you want to re-enable the three options in the shut down dialog, you 
can do this (including the quotes) on your host command line when the 
Emulator is not running:


$ VBoxManage setextradata "SailfishOS Emulator" "GUI/RestrictedCloseActions"

But I will keep shipping the Emulator with just the one option enabled 
also in the future releases.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Recent update improvements?

[Juha Kallioinen]

On 23.06.2014 16:38, Chris Walker wrote:

What was the reason for 'improving' the Emulator? By improvement, I
mean that there is now only one option and that is to shut it down
rather than saving the state? I consider that to be a right PITA.



The reason was to prevent accidental state savings.

You can still save its state by opening the VirtualBox manager window 
and selecting the menu option (Close/Save state) for the running 
Emulator. It's a bit more difficult to choose and that should make it a 
more deliberate action.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Cover Page Image

[Juha Kallioinen]

On 19.06.2014 15:49, Chris Walker wrote:


I bit the bullet and did an uninstall and a full reinstall having
deleted the SailfishAlpha folder in my home folder directory structure.

I'm now seeing lots of these errors in a Konsole window however :-

kfilemodule(15749) KDesktopFile::isAuthorizedDesktopFile: Access to '
"/home/chris/Sailfish_Git_Projects/GBG_Beertent/GBG_Beertent.desktop" '
denied, not owned by root, executable flag not set.

I didn't see them before the reinstallation.



Hi,

looks like some component in KDE is looking at your project's desktop 
file and is trying to evaluate them (or something). I don't know if this 
is a big issue, although the extra warnings can be confusing. Those 
messages do not originate from the SDK code.


Out of interest, what is your linux distro and KDE version?

Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Prototype 'TextBaseItem' from 'TextBase' could not be resolved (M301)

[Juha Kallioinen]

On 16.06.2014 19:18, i...@flyingfischer.ch wrote:

Thanks for the information!

The import statement makes the TextField error disappear. But the 
other errors remain


(process:957): dconf-CRITICAL **: unable to open file 
'/etc/dconf/db/vendor': /etc/dconf/db/vendor: invalid gvdb header; 
expect degraded performance


and when creating a new page:

[W] unknown:111 - 
file:///usr/lib/qt5/qml/Sailfish/Silica/PageStack.js:111: TypeError: 
Cannot call method 'connect' of undefined


I will try to investigate further...



Hi,

I cloned your github project and built it and deployed it to the 
Sailfish OS Emulator. At least, I'm not seeing that dconf-CRITICAL 
message. Perhaps you've managed to resolve it?


You say that you're not installing your App to the phone, so I assume 
you're installing it to the Sailfish OS Emulator? It mostly seems to 
work for me.


I do get that [W] unknown:111 - warning when clicking through the 
different pages, but I think that is a problem in your application, 
which you should be able to resolve.


Best regards,
 Juha
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Cover Page Image

[Juha Kallioinen]

On 13.06.2014 21:16, Chris Walker wrote:


Is this relevant to my problem above? I don't see how, but you never
know!

error: unpacking of archive failed on
file /usr/share/scratchbox2/modes/sdk-build: cpio: rename failed - Is a
directory

This was from an attempted update after the above failure.


Hi,

I'm not sure if this is relevant to your original problem, but that 
error looks like one that might come if you update the MerSDK with 
zypper dup instead of letting the SDK updater update/replace all of the 
components. If this is the case, I suggest that you either let the 
updater do its job or do a complete reinstall of the SDK.


Best regards,
 Juha
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Prototype 'TextBaseItem' from 'TextBase' could not be resolved (M301)

[Juha Kallioinen]

On 13.06.2014 11:01, i...@flyingfischer.ch wrote:

Hello

The IDE gives me en error on the "TextField" element. I couldn't find 
anything to resolve it.


Thank you for your inputs!
Markus

[Translated to english from the german error message:]
Prototype 'TextBaseItem' from 'TextBase' could not be resolved (M301)


Hi,

the error you are seeing is a problem with Qt Creator finding 
documentation for the TextField element. You can use the element, but 
for some reason Qt Creator cannot resolve the documentation link correctly.


If you add this line to your qml file, Qt Creator is able to resolve the 
TextField doc link and points you to the Silica documentation:


import QtQuick.Controls 1.0

This way you can read the documentation (or just search for it in the 
Help index), but you should not leave it to your code or you may get an 
error when running your program. Why that import statement helps is 
because TextField is also an element of the Qt QML.


Summary: This is a bug in how Qt Creator is able to resolve 
SailfishSilica documentation.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] problem with SDK version 5 June 2014

[Juha Kallioinen]

On 12.06.2014 20:35, Iosif Hamlatzis wrote:
I uninstalled previous SDK and did a clean installation of the latest 
SDK (SailfishOSSDK-Alpha-1406-Qt5-windows-offline.exe) under Windows 
XP SP3


Compilation now fails with error:

error: Failed build dependencies:

pkgconfig(sdl2) is needed by harbour-wanted-1.0.1-1.armv7hl

pkgconfig(glesv1_cm) is needed by harbour-wanted-1.0.1-1.armv7hl

pkgconfig(SDL2_image) is needed by harbour-wanted-1.0.1-1.armv7hl

pkgconfig(SDL2_ttf) is needed by harbour-wanted-1.0.1-1.armv7hl

pkgconfig(SDL2_mixer) is needed by harbour-wanted-1.0.1-1.armv7hl

pkgconfig(audioresource) is needed by harbour-wanted-1.0.1-1.armv7hl

pkgconfig(glib-2.0) is needed by harbour-wanted-1.0.1-1.armv7hl


I have used zypper command line utility to install the normal and 
development libraries for SDL2, SDL2_image, SDL2_ttf, SDL2_mixer, 
glib-2.0, audioresource, glesv1_cm and glesv2 libraries.


Hi, where and how exactly did you install those packages?

The MerSDK virtual machine has two scratchbox2 build targets where the 
packages should be installed using the sb2 command. You can also use 
zypper to install exactly what you're seeing in the failure. Here's an 
example of how to install packages to the arm target:


First ssh to the MerSDK virtual machine as user mersdk and then:

[mersdk@SailfishSDK ~]$ sb2 -t SailfishOS-armv7hl -R -m sdk-install 
zypper install 'pkgconfig(sdl2)'


This makes the sdl2 development files available to the arm build target. 
You should do the same for the other build requirements.


I'm guessing here, but perhaps you have installed the packages to the 
MerSDK virtual machine and not in the build target?


Looking at your spec file below, I can see that it is not compatible 
with the Qt Creator based approach we have. That approach requires that 
the project is a Qt project with a .pro file and a qmake step (which 
would automatically install the build dependencies to the build target).


If you are familiar with IRC, you are welcome to join #sailfishos 
channel in freenode for a more interactive discussion with other 
developers. It's difficult and slow to try to solve problems over e-mail 
in a case where the project is not what the SDK is directly supporting.


Best regards,
 Juha



My .spec file is:

Name:harbour-wanted
Summary: A  video  slot  game  with  bandits
Version: 1.0.1
Release: 1
Group:   Games
License: Proprietary
URL: http://7cecdab4.blogspot.gr/2014/04/wanted.html
Source:  %{name}-%{version}.tar.bz2
BuildRequires:  pkgconfig(sdl2)
BuildRequires:  pkgconfig(egl)
BuildRequires:  pkgconfig(glesv1_cm)
BuildRequires:  pkgconfig(glesv2)
BuildRequires:  pkgconfig(SDL2_image)
BuildRequires:  pkgconfig(SDL2_ttf)
BuildRequires:  pkgconfig(SDL2_mixer)
#  for  playing  sound  on  DEVICE
BuildRequires:  pkgconfig(audioresource)
BuildRequires:  pkgconfig(glib-2.0)
#  for  playing  sound  on  DEVICE
%description
A  video  slot  game  themed  with  sheriff  and  bandits
%prep
%setup  -q  -n  %{name}-%{version}
%build
#  Command  used  to  compile  the  application
make
%install
rm  -rf  %{buildroot}
#  Command  used  to  install  files  into  %{buildroot}
%make_install
%files
%defattr(-,root,root,-)
%{_bindir}/%{name}
%{_datadir}/%{name}
%{_datadir}/applications/%{name}.desktop
%{_datadir}/icons/hicolor/86x86/apps/%{name}.png





___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org


___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

[SailfishDevel] Sailfish OS SDK June update available today 13:00 UTC

[Juha Kallioinen]

Hello again,

Today (June 12th) at 13:00 UTC we will publish new installers and 
package repositories for our Sailfish OS SDK version Alpha-1406-Qt5.


If you already have an existing Alpha-Qt5 SDK installed you should see 
the Updates Available icon in Qt Creator. If you don't have a previous 
SDK installation you can get the latest installer from 
http://www.sailfishos.org.


It is recommended to uninstall the old SDK and download a new installer.

SDK content has been updated to match Jolla Release 1.0.7.16. Please see 
below for detailed information of the changed items.


A couple of things you should be aware of:
- As 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 
theSailfish OS SDK, make sure toselect 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=8328or the 
Installer will ask for admin rights during installation.
- Package repository contents have been updated and consequently using a 
previous SDK version with these package repositories is not supported.
- Supported host platforms can be found from: 
https://sailfishos.org/alpha_qt5_sdk_release_notes.html
- For more information, please see the SDK Alpha-Qt5 known issues list 
at: https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.


Here is the summary of changes:

SDK IDE (Qt Creator)
- Syntax highlighting definitions added for spec, yaml, desktop and 
changes files.
- In Windows, configuration directory is created under theSDKinstall 
path (e.g. C:\SailfishOS\settings\SailfishAlpha4)

- Project path can have whitespace

Installer:
- Fixed VirtualBox 4.3.12 support in Windows
- In Windows, SDK install path can no longer have whitespace.
- Installer will request Qt Creator to be closed in case it is 
runningand if a component requires that Qt Creator is restarted.
- SDK version can be checkedfrom the file sdk-release in the install dir 
(e.g. ~/SailfishOS/sdk-release)


SDK Build engine:
- Faster rsync deploy method (skips RPM package check step).
- Deploy the correct RPM package in case package version has been changed.
- i486 target finally creates i486 packages instead of i586 packages.
- Handle Windows CRLF type linefeeds in RPM spec files.
- Build targets refreshed to Jolla release 1.0.7.16level.
- Better translation support in libsailfishapp.
- Deployed packages are installed using sdk-deploy-rpm instead of pkcon.

SDK Control Center:
- Package search in target view is now case-insensitive.

Emulator:
- Emulator packages refreshed to Jolla release 1.0.7.16level.
- Closing the Emulator window offers now only the power off option.

If  you have any questions, feel free toeither send an email to this 
mailing list: > or write it up in 
http://together.jolla.com  and tag your issue with 'sdk'.


Happy hacking,
Jolla SDK Team.

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."

[Juha Kallioinen]

On 03.06.2014 19:57, Christopher Lamb wrote:

Hi Juha

I am now on the train. Deployment also works with WiFi active, but not 
properly connected.


This means that - at least in my case - adding SailfishSDK to the 
/etc/hosts is a good fix for this error.


Hi,

I'm happy to hear that it works for you! I've added a section about this 
to the SDK known issues page [1] as you suggested.


[1] https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues

Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."

[Juha Kallioinen]

Hi Christopher,

the changing networks may play a part in this problem. Did I already 
sometime earlier ask you to modify your Mac's /etc/hosts file?


It has helped in some cases to add the name for the MerSDK virtual 
machine to /etc/hosts like this:


127.0.0.1 SailfishSDK

Or if you already have the 127.0.0.1 there, just add the SailfishSDK to 
the end of the existing line like this:


127.0.0.1localhost.localdomain localhost SailfishSDK

Could you try this and let me know if there's any improvement? If you 
already have it there.. well then we'll have to think of something else. 
VirtualBox has some DNS related settings like these:


|--natdnsproxy<1-N> on|off|: This option makes the NAT engine proxy all 
guest DNS requests to the host's DNS servers|

|

|--natdnshostresolver<1-N> on|off|: This option makes the NAT engine use 
the host's resolver mechanisms to handle DNS requests


Of these we use the "--natdnshostresolver1 on" in MerSDK and the Emulator.

The options are documented here:

http://www.virtualbox.org/manual/ch08.html#vboxmanage-modifyvm

The rpmbuild command does a DNS query in the place where the failure is 
in your log. Usually it just prints out:


"warning: Could not canonicalize hostname: SailfishSDK"


Which is fine.. but in some networks that bit can cause a failure. In 
those cases modifying the /etc/hosts file has helped.


Best regards,
 Juha

On 03.06.2014 10:24, Christopher Lamb wrote:

Hi Saija

In my case restarting the VMs does not help. I think (from memory) 
that rebooting the whole laptop does help.


It is possible that the same reported error may have a number of 
different causes - in my case it seems to be when my development host 
loses its network connection (though as with all sporadic problems it 
is difficult to be sure).


Thanks

Chris
On 03.06.14 09:02, Saija Saarenpää wrote:
I get the same error often when developing with Windows 8 64-bit, 
never on Mac OSX 10. They are both always connected to the (same) 
network. It helps to close and open the virtual machine, the  it 
stays reachable for another while once it does the same again.


- Saija

Lähetetty iPadista

"Christopher Lamb"  kirjoitti 3.6.2014 
kello 9.58:


Hi Jarko

Still on the train, now with the Jolla Wifi Hotspot active, and I 
can build without problems.


This indicates that I get the problem when no network is connected. 
In this case I am deploying to the Emulator, so no network should be 
required 


Grüsse

Chris


On 02.06.14 10:23, Jarko Vihriala wrote:
journalctl -fa

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to 
devel-unsubscr...@lists.sailfishos.org

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to 
devel-unsubscr...@lists.sailfishos.org


___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to 
devel-unsubscr...@lists.sailfishos.org


___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."

[Juha Kallioinen]

On 28.04.2014 09:01, christopher.l...@thurweb.ch wrote:

Hi

Thanks.

I found a well hidden {1} timeout setting in the preferences / devices 
and increased this from the default 2 secs to 10 secs. This does seem 
to help, but as always with sporadic problems only time will tell if 
this is a fix, or if the problem is just dormant for a while.


What I don't understand is, given the error says "Could not connect to
MerSDK Virtual Machine" why should a timeout for connecting to a 
Jolla device play any role?


Is the error misleading? is the problem actually in connecting FROM 
the MerSDK to the Jolla?


Hi, I can't seem to reproduce these timeout problems when I'm testing 
this. I've tried on Linux and Windows and a bit less on a Mac. I wish I 
could, so I could debug this because I can't fix it if I can't reproduce it.


The error you get might be a bit misleading. The deploy operation does 
currently go through the MerSDK machine:


Qt Creator -> ssh mersdk -> rsync to device (from mersdk) -> ssh to 
device to install package (from mersdk)

Qt Creator -> ssh to device to run the app

So Qt Creator does not really know what happens inside MerSDK as it 
requests the deploy operation and if a timeout happens at some point, it 
will just look like a timeout connecting to MerSDK.


Can you describe in detail what happens when you get the timeout? Does 
it timeout after 2 seconds or 10 seconds or a minute or two?




Chris

{1} when the preferences pane opens, at least on my OSX host the 
timeout setting is "offscreen" in an embedded pane with scroll bars in 
the middle of the preferences pane. Only if you scroll down in the 
embedded pane are further settings including the timeout revealed. 
Truly a wonderful bit of UI design 8-)


Yes, I noted that comment earlier and tried for a few minutes to 
rearrange the view. Failed. It's in the "todo when all the fires are 
out" - list.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Follow up on "Warnings shown as errors"

[Juha Kallioinen]

Hi,

I can't reproduce this in Windows XP either. I installer Win XP Pro SP3 
(32 bit) and the warnings and errors show up just fine and warnings can 
be filtered away.


Also I don't get the word "warning:" in front of the warning messages as 
you can see in the picture I included in the previous message.


Is it possible that something in the project you are compiling is 
producing these messages since they seem to be slightly different from 
the standard messages? Or have you turned on some extra options in Qt 
Creator that aren't on by default?


What I was trying to say about the compiler was that the Qt Creator that 
is shipped in the installer is compiled with MSVC 2010. It's not a 
compiler that can be used with the SDK. But also it does not

seem to matter since it works in my Win XP installation.

One more thing for you to check: if you create some other project, like 
the default template project and add some code lines that produce 
warnings there, do you see the same behavior?


Best regards,
 Juha

On 21.05.2014 19:03, Iosif Hamlatzis wrote:
As I see you're using a different OS, you use Win7 and I'm on WinXP 
Pro with SP3, it's one difference. Also you mention of MSVC2010 for 
the compiler. I am using the one provided with the SDK, that's a 
second difference.



https://www.dropbox.com/s/t9djgevjufj5ekx/only_errors.PNG
https://www.dropbox.com/s/prf0b61pzgwgyw3/warnings_errors.PNG

From the two screen captures you can see that the same icon is used 
for both warnings and errors. In the first screen capture I have 
selected to display only errors, but you can see warnings as well. In 
the second screen capture I have selected to display both warnings and 
errors. The result is exactly the same, everything is shown.


And in both cases you'll see that no icon is displayed on the line 
with the error. I know the usage of #error is not exactly the same as 
having an actual compile error, but it was the fastest way to 
reproduce the problem.




On 21 May 2014 12:25, Juha Kallioinen <mailto:juha.kallioi...@jolla.com>> wrote:


On 21.05.2014 09 :04, Iosif Hamlatzis wrote:

As I haven't gotten a response I am coming back to the issue:

After updating to the latest SDK on a Windows XP Pro with SP3 all
warnings and errors have the same icon a red triangle. Pressing
the button on the QtCreator IDE to display all or only errors
doesn't work. Also double clicking on an error or warning it
doesn't take me to the corresponding file/line.


Sorry, I think I did respond in the most annoying way: "works for
me". I don't know what else can be done since the same Qt Creator
source is used to build the Windows version. The Windows version
is built in Windows 7 (32bit) with MSVC2010 compiler.

I also tested it in Windows 7 and I do get separate indication for
warnings and errors as you can see [1]. Double clicking on an
error/warning does take me to the corresponding file and line.

Is anyone else having the same problem as Iosif?

[1] http://i.imgur.com/MUjDAuM.png





I have tried this on two different machines both as an upgrade
from previous SDK version and as a clean installation. All
occasions similar conclusion.

Another thing is that when I try to debug on the actual device
the application builds correctly and is automatically deployed on
the device then a pop-up dialogue appears asking me for an
executable, but which .exe or .cmd file should I use and what
parameter should I pass? I presume as a parameter I should pass
the name of the application I want to debug, but what is the
executable?


The debugging from Qt Creator works if Qt Creator knows what the
executable it needs to run is. The pop-up dialogue is an
indication that in your project this is not the case.

Does the simple Sailfish template project application work for you
in the way that Qt Creator would know which binary to run and
consequently debug?

The template project is very simple and it is of template type
"app" (which is the default and not mentioned in the template's
.pro file). It only builds one binary and it's quite obvious for
Qt Creator that that is the binary it needs to run.

I'm not sure how exactly Qt Creator figures out which binary to
run in a more complex case.



Under the folder
.\SailfishAlpha4\mer-sdk-tools\MerSDK\SailfishOS-arm7hl are
only files for compiling, packaging and deploying. NO debugging.

eg:
deploy.cmd
gcc.cmd
make.cmd
qmake.cmd
rpm.cmd
rpmbuild.cmd


These files are internal for Qt Creator and SDK use and there
should not be need to study them. Debugging is not done via any of
those scripts as you have already discovered.

Best regards,
 Juha


__

Re: [SailfishDevel] Screenshots in silica reference

[Juha Kallioinen]

On 23.05.2014 08:21, Kimmo Lindholm wrote:

Hi,

I so would like to see screenshots in silica reference.

Like there is on "common pitfails" -page.

-kimmo


I'll use this as an opportunity to mention that the "Components Gallery" 
application which comes pre-installed in the SDK emulator has 
interactive examples of the Silica components.


The Components Gallery can also be built as a project in Qt Creator and 
it can be found from the Qt Creator Welcome page/Examples tab/Sailfish 
Silica Component. If you're not using Qt Creator, then the project 
sources can be found from SDK installdir/examples/componentgallery.


This is not discrediting the idea of having screenshots in the Silica 
reference page.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Follow up on "Warnings shown as errors"

[Juha Kallioinen]

On 21.05.2014 09:04, Iosif Hamlatzis wrote:

As I haven't gotten a response I am coming back to the issue:

After updating to the latest SDK on a Windows XP Pro with SP3 all 
warnings and errors have the same icon a red triangle. Pressing the 
button on the QtCreator IDE to display all or only errors doesn't 
work. Also double clicking on an error or warning it doesn't take me 
to the corresponding file/line.


Sorry, I think I did respond in the most annoying way: "works for me". I 
don't know what else can be done since the same Qt Creator source is 
used to build the Windows version. The Windows version is built in 
Windows 7 (32bit) with MSVC2010 compiler.


I also tested it in Windows 7 and I do get separate indication for 
warnings and errors as you can see [1]. Double clicking on an 
error/warning does take me to the corresponding file and line.


Is anyone else having the same problem as Iosif?

[1] http://i.imgur.com/MUjDAuM.png




I have tried this on two different machines both as an upgrade from 
previous SDK version and as a clean installation. All occasions 
similar conclusion.


Another thing is that when I try to debug on the actual device the 
application builds correctly and is automatically deployed on the 
device then a pop-up dialogue appears asking me for an executable, but 
which .exe or .cmd file should I use and what parameter should I pass? 
I presume as a parameter I should pass the name of the application I 
want to debug, but what is the executable?


The debugging from Qt Creator works if Qt Creator knows what the 
executable it needs to run is. The pop-up dialogue is an indication that 
in your project this is not the case.


Does the simple Sailfish template project application work for you in 
the way that Qt Creator would know which binary to run and consequently 
debug?


The template project is very simple and it is of template type "app" 
(which is the default and not mentioned in the template's .pro file). It 
only builds one binary and it's quite obvious for Qt Creator that that 
is the binary it needs to run.


I'm not sure how exactly Qt Creator figures out which binary to run in a 
more complex case.


Under the folder 
.\SailfishAlpha4\mer-sdk-tools\MerSDK\SailfishOS-arm7hl are only 
files for compiling, packaging and deploying. NO debugging.


eg:
deploy.cmd
gcc.cmd
make.cmd
qmake.cmd
rpm.cmd
rpmbuild.cmd

These files are internal for Qt Creator and SDK use and there should not 
be need to study them. Debugging is not done via any of those scripts as 
you have already discovered.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] QML creates a Segfault

[Juha Kallioinen]

On 13.05.2014 14:00, Matthias Barmeier wrote:

Hi,

when trying to download data in a WorkerScript thread I got this:

bash: line 1: 1459 Segmentation fault QT_NO_JOURNALD_LOG=1 
DISPLAY=:0.0 /usr/bin/CalDav



Can somebody explain if I can avoid this or what the reason is ?



That script part is  how Qt Creator runs your application in the 
device/emulator. So it just means that /usr/bin/CalDav crashed to a 
SEGFAULT and you'll need to figure out why.


Qt Creator launches the application in the device/emulator almost like this:

ssh nemo@device_address "QT_NO_JOURNALD_LOG=1 DISPLAY=:0.0 
/usr/bin/applicationname"


It does not use ssh command, but an ssh library, which is part of Qt 
Creator.


The QT_NO_JOURNALD_LOG =1 is there to make the application not put its 
output to journald, but to stdout/stderr instead so that Qt Creator can 
display it.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Warnings shown as errors

[Juha Kallioinen]

On 06.05.2014 20:38, Iosif Hamlatzis wrote:
Just updated to the latest SDK (1404 16 April 2014) and what I've 
noticed is that all warnings are shown as errors, at least the icons.


Under the previous version of QtCreator I could select to display only 
errors or include warnings as well by pressing the yellow icon on the 
issues tab. Under this version pressing this icon doesn't seem to do 
anything. All warnings are always visible.




Hi,

what is your host operating system where you run the SDK? Win/Mac/Linux 
and which version?


I just tested this in Ubuntu 12.04/64bit and toggling the warnings 
on/off works for me. Also the warnings and errors had different icons. 
These warnings/errors originated from a C++ file.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] rcc -threshold option doesn't work?

[Juha Kallioinen]

On 24.04.2014 07:48, tw_bolek wrote:

Hello guys,

Has anyone managed to get the -threshold option of rcc (resource compiler) to 
work?   By default the threshold is quite high and leaves many files 
uncompressed in the resource, so I usually change it to much lower threshold.  
It used to work fine on Symbian and Harmattan, it does work on BB10,  but on 
Sailfish OS adding e.g.

-threshold 2

to rcc command in Makefile (to get threshold level of 2%) doesn't seem to have 
any result whatsoever - all the files remain uncompressed while with such a 
very low threshold everything should be compressed...  Also tried other values, 
e.g. 10, to no avail.



I believe the problem may be that the Makefile is recreated every time 
you press build because of limitations in the qt creator / virtual 
machine integration. You could try adding QMAKE_RESOURCE_FLAGS to your 
"spec" file in a suitable place.


QMAKE_RESOURCE_FLAGS += -threshold 0 -compress 9


That example is from [1].

[1] http://qt-project.org/doc/qt-5/qmake-variable-reference.html

Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Qt Kits broken on Windows?

[Juha Kallioinen]

On 22.04.2014 16:55, Gabriel Böhme wrote:

Hi Juha,

first of all - thanks for your fast answer! Secondary: it's not a big
problem in my case, cause my main system is Linux and there is
everything working fine. Also creating another user in Windows, may not
be perfect, but also not too much effort. ;)

But maybe it could help, if you allow to change the deploy path. Or the
path of the "SailfishAlphaX" folder itself. Because linking to the new
user solved the problem with the Qt Kits, what means it's building the
project, only deploy is not working. So the user (or the installer
checks) could change it to pure C:\ or something else the user wants? Or
is there something preventing this?


Hi Gabriel,

I just noticed that Qt Creator has a commandline option '-settingspath' 
that can be used to tell where it should save/load its settings from.


If you set it to for example "C:\SailfishOS\mysettings" then Qt Creator 
will use that as its settings directory. This should avoid the problem 
with non-ascii chars. In principle we could use this as a default for 
all windows installations, which is something we'll have to consider.


If you want to try this, you should add the -settingspath option to the 
SailfishOS IDE shortcut, which you use to launch the IDE.


Fixing the non-ascii chars in the bat files is proving to be a bit more 
involved than I had hoped.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Qt Kits broken on Windows?

[Juha Kallioinen]

On 22.04.2014 16:55, Gabriel Böhme wrote:

Hi Juha,

first of all - thanks for your fast answer! Secondary: it's not a big
problem in my case, cause my main system is Linux and there is
everything working fine. Also creating another user in Windows, may not
be perfect, but also not too much effort. ;)

But maybe it could help, if you allow to change the deploy path. Or the
path of the "SailfishAlphaX" folder itself. Because linking to the new
user solved the problem with the Qt Kits, what means it's building the
project, only deploy is not working. So the user (or the installer
checks) could change it to pure C:\ or something else the user wants? Or
is there something preventing this?



Hi, I'm able to reproduce the problem here on my test environment, so I 
can now try to fix it too :-)


Changing the configuration folder path is not trivial. Only the 
"SailfishAlphaX" part can be changed easily (and that at compile time 
only), but the rest of the path is sort of part of Qt Creator's core 
code, which I don't want to touch. These config directories work for 
other programs just fine, so I'll just have to fix this one to work 
properly too.


I've made a small change now to how the small cmd scripts set the path 
in Windows (use \ instead of / as path separator) and the remaining 
issue seems to be the character encoding of 'ö' and presumably other 
non-ascii chars. So, somewhere those chars are handled as Latin1 and 
elsewhere as UTF-8. After that's fixed, it should work just fine.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SDK 1404 and translations

[Juha Kallioinen]

On 22.04.2014 16:47, Luca Donaggio wrote:

Did I hit a bug with the newly added translations support?

This two lines in .pro (I just changed the lang code in standard .pro 
file created by sialfishapp/qtquick app wizard) file:


CONFIG += sailfishapp_i18n
TRANSLATIONS += translations/harbour-yourproject-it.ts

produce the following error at buld time:

lrelease error: Cannot open 
/home/mersdk/share/Projects/SailfishOS/harbour-yourproject/translations/harbour-yourproject-it.ts: 
No such file or directory



Looking at sailfishapp_i18n.prf it seems it generates 
harbour-yourproject.ts file only, not all the *.ts files specified in 
your .pro file.







Did I get something wrong or is it really a bug?




You did nothing wrong. It is a bug.

The translation support was very lightly tested and could fail in a 
number of ways.


This support was changed and fixed over the Easter weekend. If you want 
to try the changes and know what to do, you can replace the 
sailfishapp_18n.prf file in the sb2 targets with the latest from here:


https://github.com/sailfish-sdk/libsailfishapp/blob/master/data/sailfishapp_i18n.prf

Or as a workaround you can copy the existing .ts file to 
harbour-yourproject-it.ts in the project's translations folder.


The changes will be released after the next device software release.

Best regards,
 Juha


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Qt Kits broken on Windows?

[Juha Kallioinen]

Hi Gabriel,

sorry to hear about the problems. Although we are aware of problems with 
whitespace and "special chars", there's no easy solution in sight. We'll 
have to put more effort into finding a solution for this problem.


Unfortunately there's no file that points to the deploy command. It's 
hard coded in Qt Creator's code.


To see the SailfishOS project, Qt Creator must have functional kits, 
otherwise it filters out the projects that it cannot build.


Best regards,
 Juha

On 19.04.2014 20:56, Gabriel Böhme wrote:

Hi again,

I could isolate the problem a bit, it seems that my user name is 
(again) a problem. In Windows 7 it was me, naming it to my full name, 
including special char (ö) and space, but Windows 8 did it itself by 
using my Microsoft account name. If I create a new user (just few 
chars) everything works as you would expect.


For the real user (with issues) it is possible to change the paths to 
this new users "...AppData/Roaming/SailfishAlpha4..." folder. Doing 
this, I get working compilers and kits, but can't deploy because I 
have not found the file (there seems to be no option) that points to 
the deploy.cmd file. Changing that could fix the issue.


Also with the problematic user, I don't see/get the option for a 
SailfishOS project, as new project.


Maybe this is easy to fix, I hope that will help!

Thanks, Gabriel.


Am 19.04.2014 00:48, schrieb Gabriel Böhme:

Hi Sailors,

I've switched to Win8.1 Pro and one of the first things to do was to 
install the latest SDK (fresh). ;) But now my Qt Kits shown as broken 
in the settings (red warning sign). In the next tab the QtVersions 
seems to be the problem, because it says that qmake can't be found or 
is not executable. But the qmake, make, deploy ... *.cmd files are 
there in AppData/Roaming where the path want's them.


Any idea, hint, or known problem?

Thanks, Gabriel.


___
SailfishOS.org Devel mailing list



___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow. [update:all installers and repositories are online]

[Juha Kallioinen]

On 18.04.2014 14:35, christopher.l...@thurweb.ch wrote:

Hi Juha and Mikael

For what it is worth, to kill some time while a batch of beer is 
brewing, I installed Kubuntu 14.04 in a VM, and then the April SDK.


In my case the Emulator does work in Kubuntu 14.04 - though it does 
take inordinately long to do so (maybe down to the multiple layers of 
VMs.


The mother host is an Mac Pro 2008 running Mavericks and Professional 
Version 6.0.3 (1747349).


In that I did I fresh install of Kubuntu 14_04 64 bit.

Into this I installed VirtualBox 4.3.10 for Linux (package for Ubuntu 
13.04 ("Raring Ringtail") / 13.10 ("Saucy Salamander") AMD), and the 
April SailfishOS SDK.


Having installed everything, the Emulator starts, and I eventually get 
a GUI, and am able to deploy a demo "Hello Sailors" app.




Hi Chris,

thanks for testing! I think your Mac Pro from 2008 is a bit too old to 
encounter this problem. The problematic instruction set extension 'AVX' 
was introduced in 2011 in Intel CPUs. My Mac is from late 2011 and I got 
the problem when running Ubuntu 12.04 or 14.04 in VMware, but not in the 
native Mac SDK 1404.


We had this same problem in earlier SDKs and it presented itself more 
easily back then (just on my linux laptop) and was patched in the 
mesa/llvm packages. Those packages were updated some time after the 
previous SDK release and the patches were dropped, because it looked 
like the problem was gone.


But here we are... reapplying the AVX patches makes the problem go away 
at least in in my Mac + VMware environment.


Also, as you report, running the SDK inside another virtual machine 
makes it run really slowly.


Best regards,
 Juha



___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow. [update:all installers and repositories are online]

[Juha Kallioinen]

On 18.04.2014 03:09, Juha Kallioinen wrote:
Hi, I installed ubuntu 14.04 (not KDE) to my Mac vmware Fusion and the 
SDK into that - I'm seeing the same problem here now.


What's your host machine and how do you run the SDK in it? I'm just 
trying to collect more info to figure out what's common in our systems.


If I set all the environment variables correctly (from 
/var/lib/eviconment/compositor/*.conf) and run lipstick from nemo's 
console it crashes to a SIGILL in the end.




Seems that this is caused by unsupported CPU capability (AVX) leaking 
into VirtualBox in some machines. At least that's my case. The 
mesa-llvmpipe  packages need patching and that's in the pipeline now. I 
hope we can get a new patched Emulator out there some time next week 
already, but since today and Monday are public holidays in Finland, 
there can be delays.


Mikael, I would be interested to hear the specs of your machine where 
you have this problem. And do you happen to run the SDK in another 
virtual machine by any chance?


Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow. [update:all installers and repositories are online]

[Juha Kallioinen]

On 17.04.2014 23:55, Mikael Hermansson wrote:

Reinstall from scratch did not solve the issue.

I guess kubuntu 14.04 have to be blacklisted for now since emulator don't work
:/

Let me know if someone else got similar issues.

Btw. the "touchpointer" is shown.



Hi, I installed ubuntu 14.04 (not KDE) to my Mac vmware Fusion and the 
SDK into that - I'm seeing the same problem here now.


What's your host machine and how do you run the SDK in it? I'm just 
trying to collect more info to figure out what's common in our systems.


If I set all the environment variables correctly (from 
/var/lib/eviconment/compositor/*.conf) and run lipstick from nemo's 
console it crashes to a SIGILL in the end.


Best regards,
 Juha
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow. [update:all installers and repositories are online]

[Juha Kallioinen]

On 17.04.2014 17:51, Luca Donaggio wrote:
After updating succesfully, is it safe removing the 
~/.config/SailfishAlfa3 directory?




Yes it is.

This is also mentioned in the known issues page [1], which may also 
contain other useful bits of information.


[1] https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues

Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] OSX sdk issue (was maces sdk issue)

[Juha Kallioinen]

On 17.04.2014 12:08, christopher.l...@thurweb.ch wrote:
Note on OSX, even if you do a clean uninstall & reinstall as 
recommended in the release notes, the "old" SDK and Emulator VMS are 
not deleted.


However this is not a real problem, the installer installs the new VMs 
next to the old, and the old VMs can be easily removed using the 
VirtualBox GUI




Hi, I have not seen this happen in any mac where I've tested (three 
different macs). The old virtual machines definitely should get deleted 
in the process. The uninstaller does need some work to make it more robust.


Best regards,
 Juha
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow. [update:all installers and repositories are online]

[Juha Kallioinen]

On 17.04.2014 11:02, Iosif Hamlatzis wrote:
Has anyone noticed that the link (at least for Windows) on the main 
page of https://sailfishos.org/ is the old one 
http://releases.sailfishos.org/sdk/installers/1312/SailfishOSSDK-Alpha-1312-Qt5-windows-offline.exe 
(SDK Release Alpha "1312" is out 13-Dec-2013)


and the latest version is https://sailfishos.org/develop.html 
(http://releases.sailfishos.org/sdk/installers/1404/SailfishOSSDK-Alpha-1404-Qt5-windows-offline.exe)?




Could you try force-reloading the https://sailfishos.org page in your 
browser? For me it does show the links to 1404 installer...


We'll need to put remove the old installers from a functional path so 
that someone doesn't accidentally download one of those.


Best regards,
 Juha


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow. [update:all installers and repositories are online]

[Juha Kallioinen]

On 16.04.2014 23:01, Mikael Hermansson wrote:

I don't know if this is related to just kubuntu or just a VMissue since the
sailfishemulator does not work. I just get the kernel message but sailfishUI
does not start. More exactly lipstick does not start. I can login via ssh and
try start lipstick but only get:

[C] unknown:0 - Failed to create display (Connection refused)

also Vbox eating cpu since fan goes wild.


That sounds like something that went wrong in update/install phase, but 
I've never seen this problem myself. I'm afraid you will need to try 
uninstall/reinstall from scratch.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] maces sdk issue

[Juha Kallioinen]

On 16.04.2014 19:52, Nicola De Filippo wrote:

Hi,
updating the sdk on MacOS i have 2 issue:

1) when the maintenance tool execute/usr/bin/VBoxManage createvm 
--name MerSDK --register --basefolder /Users/nicola/SailfishOS/mersdk 
and i resolved removing MerSDK.vbox and pressing retry in the dialog


2)  when the maintenance tool execute /usr/bin/VBoxManage createvm 
--name SailfishOS Emulator --register --basefolder 
/Users/nicola/SailfishOS/emulator and i resolved removing 
Emulator.vbox and pressing retry in the dialog





Hi I think this can happen if you chose to update your SDK (instead of a 
reinstallation) and the MerSDK and SailfishOS Emulator virtual machines 
were in running state. I need to add more checking to the installer in 
the update case.


In the worst case you will be required to uninstall and download the 
full installer and reinstall from that.


Same goes for Mikael.

Best regards,
 Juha
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

[Juha Kallioinen]

On 16.04.2014 16:19, christopher.l...@thurweb.ch wrote:

Zitat von "Juha Kallioinen" :

Hi Juha


On my host the access permissions were

apple-pip:javascript christopherlamb$ cd 
/Users/christopherlamb/QTProjects/landed/landed26_QT5/landed26_QT5/qml/javascript

apple-pip:javascript christopherlamb$ ls -ahl
total 72
drwxr-xr-x  7 christopherlamb  staff   238B 22 Feb 22:01 .
drwxr-xr-x  9 christopherlamb  staff   306B  8 Feb 19:57 ..
-rw-r--r--  1 christopherlamb  staff   4,1K 22 Feb 22:01 jsonpath.js
-rw---  1 christopherlamb  staff   349B  8 Nov 15:56 landed.js
-rw---  1 christopherlamb  staff   1,1K 11 Feb 19:33 message.js
-rwxrwxrwx  1 christopherlamb  staff   9,4K 22 Feb 19:47 readDataModel.js
-rw-r--r--  1 christopherlamb  staff   5,2K  8 Feb 17:29 
writeDataModel.js



I am not sure why the files on my host have such wildly different 
permissions. This probably reflects the different ages / sources of 
the files. Until now the permissions set on the host was not an issue 
I had to think about.


I have now done a chmod 777 *.js


That got me a little further, it next complained about missing qml 
files, so we have a similar issue with the permissions of .qml files.


Having gone through all my qml file in the project on my host with 
chmod 755 *.qml the project now deploys successfully to the device.


So it looks like, that (at least on OSX) the permissions of files on 
the host are important and need to be set correctly as expected on the 
end device. Something for the known issues page?


Ok glad it was this issue. You can do permission management for RPM 
packages in the yaml/spec file %files section using the %attr and 
%defattr directives. Here's more information about those directives:


http://www.rpm.org/max-rpm-snapshot/s1-rpm-inside-files-list-directives.html

Best regards,
 Juha



___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

[Juha Kallioinen]

On 16.04.2014 15:39, christopher.l...@thurweb.ch wrote:

Hi All


...

I also get the white screen when trying to open the app.

Via SSH on the jolla device I can find the file is present:
[nemo@Jolla javascript]$ pwd
/usr/share/landed26_QT5/qml/javascript
[nemo@Jolla javascript]$ ls -ahl
total 48K
drwxr-xr-x 1 root root  152 2014-04-16 14:31 .
drwxr-xr-x 1 root root  110 2014-04-16 14:31 ..
-rw-r--r-- 1 root root 4.2K 2014-04-16 14:31 jsonpath.js
-rw--- 1 root root  349 2014-04-16 14:31 landed.js
-rw--- 1 root root 1.2K 2014-04-16 14:31 message.js
-rwxr-xr-x 1 root root 9.4K 2014-04-16 14:31 readDataModel.js
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
-rw-r--r-- 1 root root 5.2K 2014-04-16 14:31 writeDataModel.js

However the access permissions look very strange. I suspect that all 
the js files should have rights like -rwxr-xr-x


Hi Chris,

I've changed the way the shared directories are mounted to the virtual 
machine. This might be caused by that. Previously the shared folders 
were mounted with 777 rights and all files were shown as read/write/exec 
for all inside the virtual  machine. I've changed it so that the rights 
are as they are on your host filesystem.


But there's really no reason for those two files to have only root 
access and the others have more access unless there's some root cause 
with your source files.


There's no code anywhere in the SDK that checks if a file is named 
'landed.js' and modifies its access rights :-)


What are the source files' permissions in your Mac's filesystem when you 
list them?


Best regards,
 Juha



___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Warning: File `Makefile' has modification time 0.51 s in the future

[Juha Kallioinen]

On 14.04.2014 16:49, Chris Walker wrote:

Physician heal thyself!

I installed the ntp client and it now picks up network time. I'm
assuming therefore that there is some time 'slip' between the host
machine and VBox.

I now get loads of warnings which again, I haven't seen before such as
these :-
Warning for %files line: "/usr/share/icons/hicolor/86x86/apps"
please use %{_datadir} to replace the leading path /usr/share

But I *ought* to be able to fix that one ;-)


Hi,

glad to hear ntp worked for you.

Those %files warnings will be gone in the next SDK update. They are 
caused by an almost-but-not-quite working .pro/.yaml file updater 
functionality in Qt Creator.


They are quite ugly, but harmless.

Best regards,
 Juha


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Changelog in rpm

[Juha Kallioinen]

On 10.04.2014 10:50, k...@foder.dk wrote:

Hi

Do you know how I can add a changelog file to the RPM package from the creator 
(like we did in the Harmattan SDK), and how it should be formatted ?


Hi,

inspired by your question I implemented changelog support, that will be 
released with our upcoming SDK update.


It will work as follows:

Add a projectname.changes file to your project's rpm subdirectory and 
the contents of that file will be added as a %changelog section to your 
RPM file. The format is as follows:


* date Author's Name  version-release
- Summary of changes

For example:

* Sun Apr 13 2014 Jack Tar  0.0.1-1
- Scrubbed the deck
- Hoisted the sails

Keep most recent entries on top of the list and separate entries by a 
blank line.


An example will be included in the latest Sailfish template project.

Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Changelog in rpm

[Juha Kallioinen]

On 10.04.2014 10:50, k...@foder.dk wrote:

Hi

Do you know how I can add a changelog file to the RPM package from the creator 
(like we did in the Harmattan SDK), and how it should be formatted ?


Hi Kim,

short answer: no.

Longer answer:

There's no direct support for changelogs in Qt Creator for Sailfish 
projects. You can manually add changelogs to RPMs by appending a 
%changelog section to the end of your package's spec file using the 
normal changelog format:


If you use a yaml file to create the spec file, the conversion will 
remove the %changelog section you have added to the spec unless you put 
it between some of the comment sections in spec known to specify (the 
yaml converter utility).


For example, add this to the end of your spec file:

# << files
%changelog
* Thu Apr 10 2014 John Doe  1.0.0
- some more comments

* Wed Apr 09 2014 John Doe  0.9
- some comments

# >> files

Since there's no support for this, you will need to make sure the 
version number matches your package version.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] [Update] Changelog for SailfishOS update 4 (1.0.4.20)

[Juha Kallioinen]

On 18.03.2014 00:14, Dmitry wrote:

Hi, will SDK be updated?


Hi Dmitry,

we're not ready with the SDK update yet, but we're working on it. The 
current SDK can still be used to create software for this SailfishOS 
release.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] HowTo debug from inside the IDE an application?

[Juha Kallioinen]

Hi,

sorry but with the current SDK it is not possible to use gdb from IDE. 
That scratchbox2 message is not relevant, since gdb would be run from 
the host and not from inside the build machine.


We're working hard to get a new SDK release out, but can't give a date yet.

Best regards,
 Juha

On 27.02.2014 10:52, Iosif Hamlatzis wrote:
I've just managed to port one of my BB10 games to SailfishOS, but now 
the problem is how to debug it on the emulator and later on the actual 
device.


I am using *windows* and want to be able to debug (step by step) from 
_*inside the IDE*_.


When the compilation finished I've noticed a message on the "compile 
output" window:


===

Welcome to scratchbox2 enabled gdb!


Before starting target program you should run command

'sb2-prepare' that sets breakpoint which is used

to stop target before its main() gets called. After

the breakpoint is hit, you are able to set furtherbreakpoints and do 
normal debugging actions.



If you are attaching to already running process or

examining a core dump, this step is not necessary.

===


How do I call this "sb2-prepare" command from inside the *IDE?*









___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Update SDK Virtual Machines to 1.0.3.8 Naamankajärvi

[Juha Kallioinen]

Hi Harald,

the SDK virtual machines/targets have not yet been updated to the latest 
device release level. What you have now is the latest SDK stuff that's 
out there.


Best regards,
 Juha

On 07.02.2014 12:42, Harald Schmitt wrote:

Hi,

probably it is a dump question, but I updated the sdk with the latetst
January update.
Now I wonder how I can update the virtual machines to the latest release?
The QT Creator SailfishOS section says, I have the latest targets, but
when I login via ssh to the emulator it welcomes me with
,---
| SailfishOS 1.0.1.11 (Laadunjärvi) (i486)
'---
I tried to remove the targets and re add them, but it did not help.

How do I update the build vm and the emulator vm?

Best regards,
Harald
___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SDK update

[Juha Kallioinen]

On 02.02.2014 21:44, Dmitry wrote:

Hi.

I have Mer VM and emulator version 2013.10.18-0 installed on Windows,
will VM disk image will be overwriten during update to 2013.12.10-1 
and i loose everything installed in VM?




Hi Dmitry,

yes that is how the update is done at the moment. Same goes for the 
Emulator.


If you have done any configuration, added extra repositories or 
installed new packages to the MerSDK build engine, build targets or the 
Emulator, all those will be lost.


Best regards,
 Juha
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Different behavior when starting application from QtCreator or Launcher

[Juha Kallioinen]

On 30.01.2014 11:21, Luciano Montanaro wrote:

Hello everybody,
maybe someone may shed some light on this odd behavior:

I have implemented an active cover in my train timetable application,
where the action is enabled when a certain property in a C++ object (a
string) has a length different from zero. This property is set by the
application when loading data from a station.

The odd thing is that this works correctly if I launch the application
from qtcreator or fingerterm, but does not when starting it from the
launcher.

The only thing that may be different is that the application is
invoked differently...

Maybe it would help me to understand how the laucher invoker works...
Can anybody give me some pointer on how it works?



Hi Luciano,

the way QtCreator launches an application is afaik not entirely correct 
and will be addressed in a future SDK update.


To see how the application is lauched when it's started from the 
homescreen icon, use fingerterm and find your application in the output 
of 'ps faxw'.


If you then start your application from fingerterm as you see it with ps 
command.. for example:


$ invoker --type=silica-qt5 --single-instance /usr/bin/yourapplication

The invoker parameters depend on what you have in your .desktop file, 
which is not used when you start it from QtCreator.


Best regards,
 Juha
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SailfishOS SDK January update 2 available today

[Juha Kallioinen]

Hi,

this could have been some temporary cache hiccup. The rpmvalidator 
package was also updated to version 
"sdk-harbour-rpmvalidator-1.4-10.7.1.jolla.noarch". The previous package 
version was what your error message shows.


I neglected to mention in my original message that also the rpmvalidator 
package was updated. It has been already updated a couple of times since 
its first release and we don't plan to announce each and every update of 
the script.


This is the script you can run from the "Harbour Tools" tab in the SDK 
control center and unless you disable the updates from that tab, the 
script is always updated to the latest available when it's run.


FYI: if you plan to send your packages to Harbour for acceptance, it's 
wise to enable updates and run the validator tool just before sending in 
case the script (and possibly some acceptance criteria) has been updated.


Best regards,
 Juha

On 28.01.2014 15:22, christopher.l...@thurweb.ch wrote:

Hi Juha

On the first attempt I got this error:

"
Operation Failed
finished: Updating SDK Engine - exited with status 4

History:
- File './noarch/sdk-harbour-rpmvalidator-1.3-10.6.1.jolla.noarch.rpm' 
not found on medium 
'http://releases.sailfishos.org/sdk/latest/hotfixes/i486/'


- Can't provide 
./noarch/sdk-harbour-rpmvalidator-1.3-10.6.1.jolla.noarch.rpm


Problem occured during or after installation or removal of packages:
Installation aborted by user

Please see the above error message for a hint.
"

On the second try a few seconds later, the update worked properly.

Chris






Zitat von "Juha Kallioinen" :


Hello,

another minor update to the SDK Build Engine was released today.

The update concerns again only the SDK Control Center, which gets 
some performance improvements, layout changes and provides a "Check 
for updates now" button in the Updates page.


You should see updates available for the Build Engine in the SDK 
Control Center Updates tab after your build engine has been running 
about 10 minutes. Please do not visit the Updates tab before the 10 
minutes has passed, otherwise the updates will show up later. The 
'Check for updates now' button was put there to avoid this wait 
period in the future.


As always, if you have any questions, you can send email to this 
mailing list <mailto:devel@lists.sailfishos.org> or write it up on 
together.jolla.com and tag your issue with 'sdk'.


Happy hacking,
Jolla SDK Team.

___
SailfishOS.org Devel mailing list





.



___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SailfishOS SDK January update 2 available today

[Juha Kallioinen]

Hello,

another minor update to the SDK Build Engine was released today.

The update concerns again only the SDK Control Center, which gets some 
performance improvements, layout changes and provides a "Check for 
updates now" button in the Updates page.


You should see updates available for the Build Engine in the SDK Control 
Center Updates tab after your build engine has been running about 10 
minutes. Please do not visit the Updates tab before the 10 minutes has 
passed, otherwise the updates will show up later. The 'Check for updates 
now' button was put there to avoid this wait period in the future.


As always, if you have any questions, you can send email to this mailing 
list  or write it up on 
together.jolla.com and tag your issue with 'sdk'.


Happy hacking,
Jolla SDK Team.

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Project Kits lost on Target Refresh

[Juha Kallioinen]

On 21.01.2014 09:17, christopher.l...@thurweb.ch wrote:

Hi All

If I do a QtCreator / SailfishOS/ Targets / Manage Targets /  
/ Manage / Sync, with project(s) open in QtCreator, then I lose the 
kits of the open project(s), and have to re-add these.




Hi Chris,

yes it's an unfortunate side effect of the way the build engine/qt 
creator interface has been implemented. This should be fixed in some 
future release, but is not a high priority.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] MerSDK VM - "src" folder change (under Windows) not possible

[Juha Kallioinen]

Hi,

no worries about the known issues, I just wanted to advertise that we 
have such a page :-)


Changing the extra src directory is currently only possible via a clean 
reinstall. Making it re-configurable after installation is on the TODO list.


Best regards,
 Juha

On 15.01.2014 18:43, Simon Bolek wrote:
OMG! I wonder how many of you thought "what a moron not to read known 
issues" - please do not answer this...
...i did remove, clean and install SDK again, and it does work. 
However before that, i also tried to change the settings under 
AppData, but it did not work for some reason. Apparently only complete 
removal and new installation helps.


thanks+br
simon :-)

On Wed, Jan 15, 2014 at 5:11 PM, Juha Kallioinen 
mailto:juha.kallioi...@jolla.com>> wrote:


Hi Simon,

if you want to get rid of your old settings, clean the Qt creator
config directory after uninstallation (be sure to close qt creator
before cleaning too).

This is mentioned in the known issues page:

https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues

* If you want to change settings such as SDK installation location
or additional source code location path, you need to remove SDK
installation and manually delete the config file directory
SailfishAlpha3 (in Windows it's under
C:\Users\\AppData\Roaming\SailfishAlpha3 and in other
systems it's under $HOME/.config/SailfishAlpha3) and then
re-install SDK.

Best regards,
 Juha


On 15.01.2014 18:07, Simon Bolek wrote:

Short update. I finally removed SailfishOS SDK and installed it
again.
I used ccleaner to clean registry etc.
Installed SDK again AND... still the same :((( (crying)
QtCreator sees the old settings. (see screenshots)
HELP! Is there something obvious i'm missing?

br
simon ;-)

On Tue, Jan 14, 2014 at 4:14 PM, Simon Bolek
mailto:simon.bo...@googlemail.com>>
wrote:

hi,
I have a difficulty in changing src shared folder for VM
MerSDK in QtCreator. It seems impossible right now.
Working on windows 7 with the latest SailfishOS installed.

While installing I set, stupid me, Project Folder to:
C:/path1/path1;C:/path2/path2
thinking QtCreator would understand both. After that started
a project and noticed that QtCreator  does not accept that.

Under
Tools->Options->Mer: MerSDK-"Shared Folders"-"src"
I see
"C:/path1/path1;C:/path2/path2"
Also in QtCreator in my particular App under Projects I see
System Environment variable
MER_SSH_SHARED_SRC = C:/path1/path1;C:/path2/path2.

So far so good.
Me thinking change settings -> all is well.
However the following changes did not change anything.

1) in the MerSDK VM under Shared Folders changed:
src1 to C:/path1/path1 or
tried with src, src2 etc.

2) in

C:\PATH_TO\SailfishOS\share\qtcreator\SailfishAlpha3\qtcreator\mersdk.xml
changed SharedSrc to C:/path1/path1 or C:\path1\path1

3) tried to override MER_SSH_SHARED_SRC in the particular
project with only
C:/path1/path1 or C:\path1\path1

Nothing helps :( Every time i remove Mer SDK under Options
and add it, first QtCreator sees only the one correct folder
C:\path1\path1 , but after Apply and invoking Options again
it shows me
C:/path1/path1;C:/path2/path2.

I also searched in the filesystem C:\ for all files
containing string:
C:/path1/path1;C:/path2/path2
or only
C:/path2/path2
there is nothing left in any .ini, .txt, .vbox etc. files.

Any hints? What am I possibly doing wrong. I am not able to
compile any project, as it gets me the error: Project is
outside of mer shared src "C:/path1/path1;C:/path2/path2"

The only way I see, how to work around this, is to delete and
install sailfishos again :(

br
simon:-)




___
SailfishOS.org Devel mailing list



___
SailfishOS.org Devel mailing list




___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] MerSDK VM - "src" folder change (under Windows) not possible

[Juha Kallioinen]

Hi Simon,

if you want to get rid of your old settings, clean the Qt creator config 
directory after uninstallation (be sure to close qt creator before 
cleaning too).


This is mentioned in the known issues page:

https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues

* If you want to change settings such as SDK installation location or 
additional source code location path, you need to remove SDK 
installation and manually delete the config file directory 
SailfishAlpha3 (in Windows it's under 
C:\Users\\AppData\Roaming\SailfishAlpha3 and in other systems 
it's under $HOME/.config/SailfishAlpha3) and then re-install SDK.


Best regards,
 Juha

On 15.01.2014 18:07, Simon Bolek wrote:

Short update. I finally removed SailfishOS SDK and installed it again.
I used ccleaner to clean registry etc.
Installed SDK again AND... still the same :((( (crying)
QtCreator sees the old settings. (see screenshots)
HELP! Is there something obvious i'm missing?

br
simon ;-)

On Tue, Jan 14, 2014 at 4:14 PM, Simon Bolek 
mailto:simon.bo...@googlemail.com>> wrote:


hi,
I have a difficulty in changing src shared folder for VM MerSDK in
QtCreator. It seems impossible right now.
Working on windows 7 with the latest SailfishOS installed.

While installing I set, stupid me, Project Folder to:
C:/path1/path1;C:/path2/path2
thinking QtCreator would understand both. After that started a
project and noticed that QtCreator  does not accept that.

Under
Tools->Options->Mer: MerSDK-"Shared Folders"-"src"
I see
"C:/path1/path1;C:/path2/path2"
Also in QtCreator in my particular App under Projects I see System
Environment variable
MER_SSH_SHARED_SRC = C:/path1/path1;C:/path2/path2.

So far so good.
Me thinking change settings -> all is well.
However the following changes did not change anything.

1) in the MerSDK VM under Shared Folders changed:
src1 to C:/path1/path1 or
tried with src, src2 etc.

2) in
C:\PATH_TO\SailfishOS\share\qtcreator\SailfishAlpha3\qtcreator\mersdk.xml
changed SharedSrc to C:/path1/path1 or C:\path1\path1

3) tried to override MER_SSH_SHARED_SRC in the particular project
with only
C:/path1/path1 or C:\path1\path1

Nothing helps :( Every time i remove Mer SDK under Options and add
it, first QtCreator sees only the one correct folder
C:\path1\path1 , but after Apply and invoking Options again it
shows me
C:/path1/path1;C:/path2/path2.

I also searched in the filesystem C:\ for all files containing string:
C:/path1/path1;C:/path2/path2
or only
C:/path2/path2
there is nothing left in any .ini, .txt, .vbox etc. files.

Any hints? What am I possibly doing wrong. I am not able to
compile any project, as it gets me the error: Project is outside
of mer shared src "C:/path1/path1;C:/path2/path2"

The only way I see, how to work around this, is to delete and
install sailfishos again :(

br
simon:-)




___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Harbour: Rejections clarify

[Juha Kallioinen]

On 03.01.2014 00:02, Mikael Hermansson wrote:


now I can understand that gst-plugins-good was rejected because its 
not on the list but the others? (Notice gst* was okey first 
version...) actually I think that lib is on the phone but not in 
emulator...




Forgot to answer to this. We'll strive to provide an emulator that is 
more in line with the device content in upcoming SDK releases.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Harbour: Rejections clarify

[Juha Kallioinen]

On 03.01.2014 00:02, Mikael Hermansson wrote:


But It seems to me Required field in yaml file should not be used is 
that the case? Please clarify this?




No it can and should be used, but only with requirements that are 
allowed. I can't comment on whether the list of allowed dependencies is 
the correct at the moment. The list will be updated if something that 
should be allowed is missing.


Please also note that even if you don't declare Requires in your spec 
file, rpm will automatically add Requires to your package's metadata 
when it notices that your binary for example links to a library it is 
using. This feature is on by default and should in most cases not be 
turned off (by declaring AutoReqProv: no).



and what about line:

sailfishsilica-qt5 >= 0.10.9 (not sure if I added this or if autoadded?)

now should this still be left in the reuquires? Because I remember 
first time I installed it on my phone(s) both n9(with sail) and my 
Jolla cried about missing "libsailfishapp.so"?




That package does not provide libsailfishapp.so. It comes from the 
package "libsailfishapp".


The default template application yaml file declares:

PkgConfigBR:
- sailfishapp >= 0.0.10

Which is converted to the spec file as:

BuildRequires:  pkgconfig(sailfishapp) >= 0.0.10

(Notice that the name there is "sailfishapp", which is the pkg-config 
name for the rpm package "libsailfishapp-devel", which in turn depends 
on the package "libsailfishapp").


If you have those lines in your yaml/spec and your application really 
does use libsailfishapp.so, rpm will notice it and will add it as an 
automatic requires dependency unless you have specified "AutoReqProv: 
no" in your spec file.


Now, if you choose to deploy your package as RPM to the device, then it 
will also install all other missing packages that are required by your 
package.


If you choose to "deploy package as binaries" in Qt Creator, then the 
RPM packaging is not built and any dependencies your package might have 
are also not handled. Either this deploy method or "AutoReqProv: no" 
might be the reason you got the "missing libsailfishapp.so" error 
originally.


As a hint, you should always deploy your package as RPM once and always 
if you add more Requires to it, so that its requirements are pulled into 
the target device. After that you can use "deploy as binaries", which is 
a bit faster since it skips the RPM package creation step.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Quickfix for SailfishOS SDK available today.

[Juha Kallioinen]

Hi,

sorry about that, there was a mishap in copying the updated files to the 
correct path. The mishap is being fixed and the update will be available 
shortly.


Best regards,
 Juha

On 17.12.2013 12:02, christopher.l...@thurweb.ch wrote:

Hi Juha

Unfortunately the Updater is giving me the error

"The hash of one component does not match the expected one"

and

Could not download meta information for component: 
org.merproject.tools. Error: Bad hash.


I am running 1312 on OSX

Chris

Zitat von "Juha Kallioinen" :


Hi,

this Qt Creator fix will be available only as an update to the "1312" 
installer. We won't make another complete installer because of this.


Best regards,
 Juha

On 17.12.2013 10:22, christopher.l...@thurweb.ch wrote:

Hi Jarko

Super, I am very glad this was given priority.

Can you confirm, we can just update, no need to completely deinstall 
like previous SDK updates?


Chris

Zitat von "Jarko Vihriala" :


Hello again,

Today at 10:00 UTC we will publish an update for Qt Creator 
(SailfishOS SDK IDE), which fixes the missing application output logs.


The update will be made available via the SDK maintenance tool and 
Qt Creator will display an update notifier when it is ready for 
downloading.


Here's are the release notes for this update:

SailfishOS SDK IDE:
* Qt Creator updated to version 2.8.1-4
* Fixes missing application output logs - emulator traces can be 
now seen in Qt Creator's application output window.


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



___
SailfishOS.org Devel mailing list





.



___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Quickfix for SailfishOS SDK available today.

[Juha Kallioinen]

Hi,

this Qt Creator fix will be available only as an update to the "1312" 
installer. We won't make another complete installer because of this.


Best regards,
 Juha

On 17.12.2013 10:22, christopher.l...@thurweb.ch wrote:

Hi Jarko

Super, I am very glad this was given priority.

Can you confirm, we can just update, no need to completely deinstall 
like previous SDK updates?


Chris

Zitat von "Jarko Vihriala" :


Hello again,

Today at 10:00 UTC we will publish an update for Qt Creator 
(SailfishOS SDK IDE), which fixes the missing application output logs.


The update will be made available via the SDK maintenance tool and Qt 
Creator will display an update notifier when it is ready for 
downloading.


Here's are the release notes for this update:

SailfishOS SDK IDE:
* Qt Creator updated to version 2.8.1-4
* Fixes missing application output logs - emulator traces can be now 
seen in Qt Creator's application output window.


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



___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SDK 13.12.2013 "nothing provides libgudev-1.0.so.0 "

[Juha Kallioinen]

Hi,

no worries.. did you by chance install to another directory than before? 
Even if you did not, let's try the following:


Exit from qtcreator if you have it running and then remove the config 
directory, which is in Linux and mac in ~/.config/SailfishAlpha3


The config directory contains qtcreator specific settings for the 
Sailfish SDK and it might have some wrong settings from a previous 
installation. The config directory is created when qtcreator is run the 
first time.


You can just remove the whole directory, then start qtcreator again and 
see if that helped.


If that didn't help, then exit from qtcreator, remove the 
~/.config/SailfishAlpha3 directory again and uninstall the whole SDK and 
run the installer once more.


If the "1310" SDK worked for you, the "1312" should work too. Nothing 
fundamental has changed.


Best regards,
 Juha

On 13.12.2013 22:40, christopher.l...@thurweb.ch wrote:

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" :


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

Re: [SailfishDevel] SDK 13.12.2013 "nothing provides libgudev-1.0.so.0 "

[Juha Kallioinen]

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

Re: [SailfishDevel] Building/Deploying app fails with 1312 SDK

[Juha Kallioinen]

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 
 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 

Re: [SailfishDevel] [Update] Changelog for SailfishOS update 1 (1.0.1.10)

[Juha Kallioinen]

On 11.12.2013 14:30, Juha Kallioinen wrote:


For more real-time assitance you could join #sailfishos channel in 
ircNET and ask for help there. It's also ok to ask questions on this 
mailing list.


Argh, #sailfishos is of course in Freenode network and not in ircnet.

Sorry gor the brainfart,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] [Update] Changelog for SailfishOS update 1 (1.0.1.10)

[Juha Kallioinen]

Hi Seppo,

if you have developer mode activated, then you probably also have 
Fingerterm. Could you please start it and check that you haven't 
accidentally changed the ssu settings?


You can check this by opening fingerterm and entering: ssu domain

If it says the domain is something else than "sales", then enter: ssu 
domain sales


If this was the case for you, rebooting the device at this point should 
fix the situation.


For more real-time assitance you could join #sailfishos channel in 
ircNET and ask for help there. It's also ok to ask questions on this 
mailing list.


Best regards,
 Juha

On 11.12.2013 14:12, Seppo Tiainen wrote:
...just adding that the version keeps showing Salfish 1.0.0.5 
(Kajaanlampi) and the checking does not take long. Working on WLAN.



2013/12/11 Seppo Tiainen >



Today, on 11th December, I choose on my Jolla v.1.0.0.5:

Settings > [i] Device info > pull-down menu / Check for updates

=>

Updates: checking...
then
Updates: Up to date

The device has not been hacked in any way, just Dev mode is active
as normal.

Did I do something wrong or is there a delay with the update?

rgds,
Seppo


2013/12/9 Bernd Wachter mailto:bernd.wach...@jolla.com>>


Hi all,

SailfishOS gets its very first update today, version 1.0.1.10
(Laadunjärvi). It is mainly a bug fix release aimed at
improving the
stability and usability of the OS. Here are the highlights of the
improvements this release brings to your Jolla phone:

Connectivity
* WLAN password input improvements
* WLAN connection possible to change directly from one hotspot to
  an other
* Notification banner visible when checking updates without
internet
  connection
* USB MAC address does not change anymore between connections in
  developer mode
* Mobile data switch status (toggle on/off) is shown on the
Settings
  cover

Store
* Items in Store feed view now have visual busy indication while
  installing
* Chinese comments are no longer presented as "?" characters
* Improved notifications when app download fails
* App grid now shows busy indicators or current status when
leaving and
  reopening page
* Application downloads are now more resilient to failures

Bluetooth
* File receive dialog displays the name of the paired device
correctly
* Improvements in BT pairing
* BT settings now responds to bluetooth daemon restart properly

Phone & Messages
* Phone now displays number labels (i.e. work/home/mobile) during
  selection
* DTMF tones are not skipped when user rapidly presses keys
* Fixed a case when incoming call is silenced and there is
still sound
  played after call ends
* Improved contact matching in call logs when contacts
imported from SIM
* Active cover shows contact names
* Visual improvements in call forwarding UI and supplementary
services
* Support for sms: URL in Messages

People
* No more duplicated data in SIM contact import
* Improved handling of contact card details including avatars
* Added address does not disappear any more from contact
viewer screen
  after adding website information
* Stability improvements in People app during contact linking
operation
* Performance improvements in Birthday plugin for contacts

Accounts/services
* Removing a service account now removes related content from
People app
* Account emits a signal when enabled / status changes
* Option to share to Facebook does not disappear anymore after
adding an
  email account
* Facebook notification will not appear repeatedly anymore
* Disabling Facebook account removes Facebook from Events view
* IM accounts now connect without needing to reboot device, after
  adding them
* IM presence state persists now over reboot or changing
connectivity
* Improved Exchange account setup flow
* Improved interoperability with servers preferring
unsupported EAS
  protocol 14.x

Browser
* Audio and video are now in sync while playing youtube videos
* Browser does not crash when playing multiple videos

Calendar
* New dedicated calendar alarm UI introduced which will show
up with
  alarms added after the update.

Homescreen & notifications
* Events view wallpaper stays aligned with homescreen wallpaper
* Lock screen pulley menu shortcuts are not broken when device
  lock is on
* In Events view, Share what's on your mind accou

Re: [SailfishDevel] Fwd: Massive issues while installing SailfishOS IDE

[Juha Kallioinen]

On 23.11.2013 18:12, Gabriel Böhme wrote:

Hi,

I have the same problem with the SailfishOS IDE in Windows 7 and guess 
special chars and/or spaces causes the issues. The main folder is 
C:/SailfishOS and also my projects are in C:/SailfishOS/projects, but 
the "SailfishAlpha2" folder in AppData is just affected, cause it's in 
the user path, in my case a very bad path "Gabriel Böhme". So a 
special char and a space. :)




Hi,

thanks Gabriel for clarification on this issue! I wasn't aware of the 
problems with special chars in user names and had not even considered 
user names with spaces :-)


This is definitely something we need to improve on in future SDK updates.

Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Fwd: Massive issues while installing SailfishOS IDE

[Juha Kallioinen]

On 22.11.2013 12:58, Kajetan Dobczyk wrote:


After the IDE installation:

- There's no Sailfish project option in "File -> New File or Project", 
although Mer is checked in "Help -> About Plugins"


- In "Tools -> Options -> Mer", when I click "Start Emulator", nothing 
happens, either in SailfishOS Emulator / MerSDK. My VirtualBox is 
4.1.8, I've tried with the newest one too. After one of many 
installations, I could turn on the emulator, but when I tested the 
connection, I got this message: "ssh connection failure: server 
rejected key.".
I see that some other folders are created on my hard drive - IDE is 
installed in "Sailfish", and near it are "SailfishOS" and "Sailfish 
OS". Maybe the uninstall utility doesn't clear everything?


There should only be one directory under which the SDK (IDE) is 
installed. You get to select this path when running the installer.


The uninstall utility does not clean everything. It does its best to 
remove the main installation directory which usually is called 
SailfishOS. It leaves behind the QtCreator configuration directory, 
which contains for example paths to the installation directory.


Since you are seeing several directories with the word Sailfish in them, 
is it possible that you have tried to install the SDK multiple times to 
different paths? If this is the case, then the aforementioned config 
files may contain wrong paths, which will lead to problems when trying 
to use QtCreator.


In Linux this configuration data is saved under the 
/home/username/.config/SailfishAlpha2 directory. In Windows it should be 
under C:\Users\username\AppData\Roaming\SailfishAlpha2.


Could you run the uninstaller once more and then manually remove that 
SailfishAlpha2 directory?


Afterwards, when running the installer, please choose a path that does 
not have any space characters in it. The SDK does not currently work 
properly if the install path has spaces.


Best regards,
 Juha




___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Problems with the emulator (I think)

[Juha Kallioinen]

Hi Lauri,

you don't mention which SDK installer you have used. That would be vital 
information in troubleshooting this and any future problems :-)


None of the problems below seem to concern the SDK emulator. I believe 
these are build time problems?


On 16.11.2013 12:42, Lavanti Lauri wrote:


Hi all,

First time on this list, so sorry if this is an old problem but:

When I created my new project on SailfishOS IDE the main.cpp file 
complains that:


#include 
"No such file or directory"



The sailfishapp.h is part of the libsailfishapp-devel package, which is 
preinstalled in the latest "1310" installer targets released last month. 
If you have an older SDK, then this package might not yet be available.


If you are using the latest SDK, then with this information at hand, I 
cannot fathom why it would not be found.


When you say "When I created my new project", how did you create it?



And whenever I try to add a package to my sdk it says the following 
(as an example):


Operation Progress

 finished: installing package 
jolla-sailfish-core - exited with status 0


Loading repository data...

Reading installed packages...

'jolla-sailfish-core' not found in package names. Trying capabilities.

No provider of 'jolla-sailfish-core' found.

Synchronising target to host

cannot delete non-empty directory: usr/bin

Sync completed



This looks perfectly fine, although unnecessarily cryptic.

There is in fact no package called "jolla-sailfish-core". The 
jolla-sailfish-core is a pattern, not a package. A pattern is metadata 
describing a collection of packages. Unfortunately the web management 
view does not understand that and shows it as a normal package and tries 
to install it as a normal package.


What's happening in the background is that the web management calls 
zypper install for the "package", but since there's no such package, it 
does nothing and unnecessarily syncs the results between the target and 
the host.


If you try to add some real package, then it should report something 
different.


Best regards,

 Juha


Thank you J

--

Lauri Lavanti

lauri.lava...@aalto.fi



___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Packaging for harbour

[Juha Kallioinen]

Hi Luciano,

some answers below.

On 12.11.2013 11:54, Luciano Montanaro wrote:

I would like to submit my application for review, but I probably need
to do some cleanup:

Has the icon size changed to 86x86? If so I will need to update it
with the new size.


Yes icon size is supposed to be 86x86. The next SDK update will have 
this sorted out in the template and example applications.




Moreover, I think the package is meant to be uploaded as an armv7hl rpm,
but I cannot build it with qtcreator.


You are correct, ARM packages are required. It is possible with 
qtcreator, but it is a bit clumsy until we have real device support in 
the SDK.




What I tried is: change target to ARM, use rpm as deploy mechanism,
use the "deploy" menu item of the "Build" menu.

But I get an error that I need a device defined for the deploy to
complete, and no RPM packages.


To create ARM packages, you will need to add/select the ARM target and 
then choose the "Deploy Method ARM", which will create the RPMs for you, 
but won't try to install them on any device.


To execute the ARM rpm creation, choose the Build->Deploy project 
"projectname" from qtcreator menu. Once ready, qtcreator will display a 
pop-up window telling the location of the created packages.


If you have tried to change the qtcreator kit/target while 
troubleshooting this yourself, the behavior might not be as described above.


Also be sure to clean the project from Build->Clean project 
"projectname" if you switch between target architectures (i486/ARM). 
Otherwise you'll end up packaging wrong architecture binaries to the RPM.




Is this supposed to work, or should I wait for an updated SDK?


It does work, but is quite awkward as you can see. Again once we have 
the real device support in the SDK, it will become easier.


We are working on shadow build support, which will build ARM/i486 
binaries in separate directories. It will be available in the next SDK 
update.




I also tried a few combinations of the mb2 command, with no better luck.


If you want to play with the mb2 command, here's a line that should 
work. First login to the build engine as user 'mersdk' and cd to your 
project directory.


$ mb2 -t SailfishOS-armv7hl build

Note, that you can use tab-completion to fill in the target name, which 
is easy to typo.


Best regards,
 Juha


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Cannot deploy application since SDK upgrade

[Juha Kallioinen]

On 28.10.2013 11:21, Luciano Montanaro wrote:

Hi everybody,

since I upgraded to the latest SDK release, I can no longer deploy my
application.

The RPM is built correctly, after the emulator update, but the "run"
icon is grayed out, and in the "project" page, the "run" configuration
warns that the application path is missing. The text edits to set
custom executable/path are disabled, so I cannot fix this manually...

Maybe this is due to how my project is structured?
I have a main project of type subdirs, with the code/resources in the
"application" folder. Also, there are conditionals to select
maemo5/harmattan/sailfish specific options; maybe these are preventing
the automatic detection of the executable.
However the TARGET" is not under any condition at all...

Any suggestion?


The updated SDK release installs two targets; one ARM target and one 
i486 target. The ARM target has no official device support yet, so the 
Run method is not available. Please double check that you are using the 
i486 target if you want to deploy your project to the emulator.


The target names are SailfishOS-armv7hl (for ARM) and 
SailfishOS-i486-x86 (for i486).


If you are sure that you indeed have the i486 selected then let's 
explore this problem further.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] System management is locked by the application with pid 5695 (zypper) - Win 7 (behind proxy)

[Juha Kallioinen]

On 10.10.2013 11:14, Simon Bolek wrote:


I am behind the Proxy and already set up the http_proxy in global 
variables like:

http://:@:

When I try to manage->find a package e.g. ofono, i get:

+++
NoMethodError at /C/targets/add
undefined method `include?' for nil:NilClass
file: sdk_helper.rb location: toolchain_exists line: 210
+++

Are there issues when working behind proxy / win 7?


Hello,

how did you set the proxy environment variables? There's probably a bug 
somewhere in the SDK control center, since the proxy case hasn't been 
tested at all, afaik.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list