Re: [SailfishDevel] Dynamically populate a ContextMenu

[Martin Kampas]

Hi,

simply assign id to one of the static items, e.g. firstStatic, and then use 
firstStatic.parent instead of menu._contentColumn as parent for the 
dynamic items -- this way you do not rely on implementation details:

menu: ContextMenu {
id: menu
MenuItem { id: firstStatic; text: Static 1 }
MenuItem { text: Static 2 }
}

Component.onCompleted: {
console.debug(Populating menu)
for (var i=0; i 4 ; i++){
var newMenuItem = menuItemComp.createObject(firstStatic.parent, 
{text : Dynamic + i})
}
}

Event better consider using Repeater and provide the list of dynamic 
items as item model[1] (assiging a number as a model gives exactly the 
same result as in your original example):

ApplicationWindow {
initialPage: Page {
ComboBox {
width: parent.width
label: Menu

menu: ContextMenu {
id: menu
MenuItem { text: Static 1 }
MenuItem { text: Static 2 }
Repeater {
model: 4
MenuItem { text: Dynamic  + index }
}
}
}
}
}


BR,
Martin

[1] 
https://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-repeater.html#model-prop


On Saturday, November 23, 2013 04:06:40 PM 
christopher.l...@thurweb.ch wrote:
 Hi Andrey
 
 Zitat von Andrey Kozhevnikov coderusin...@gmail.com:
  you may need to make childs of menu._contentColumn, not just menu.
 
 I thought that the underscore stuff are private internal properties /
 functions that we mere mortals should not be using 8-) (Not that
 that would necessarily stop me).
 
 Chris
 
 
 ___
 SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] No map overlay objects shown if zoomLevel 3

[Martin Kampas]

Again lying - it is used in the same object, this will not work. 2x sorry :) I 
should sleep more.

Martin

On Tuesday, November 26, 2013 09:02:19 AM Martin Kampas wrote:
 Not true - I overlooked the condition. sorry. Still you can implement your
 own version of QDeclarativeGeoMapItemBase::zoomLevelOpacity() 
directly
 in your app so that linker will meet this first.. :)
 
 BR,
 Martin
 
 On Tuesday, November 26, 2013 08:56:12 AM Martin Kampas wrote:
  Hi,
  
  you might be able to modify this behavior through overriding
  QDeclarativeGeoMapItemBase::updateMapItemPaintNode()
 
 
https://qt.gitorious.org/qt/qtlocation/commit/523ebec5dca356e7ddf24792
 
  d9f6d2994a57599a
  
  BR,
  Martin
  
  On Tuesday, November 26, 2013 08:21:52 AM tw_bolek wrote:
   Hi Aaron,
   
You are not doing anything wrong. As you discovered items are 
only
  
  visible
  
when the map zoom level is greater than 3. Between zoom levels 
2
 
 and
 
  3 the
  
opacity is ramped down linearly and is 0 below a zoom level of 2. 
See
https://bugreports.qt-project.org/browse/QTBUG-25393 for details
 
 on
 
  why
  
this was implemented.
   
   Thank you very much. But does it mean that I cannot show any 
objects
 
 in
 
   zoomLevel 1?  Are there no workarounds for this?   Let's say that I
 
 need
 
  to
  
   show a full cruise of a ship between two distant continents - I want 
to
   show it over the whole world map visible at once, i.e. zoom level 1, 
so
   that the user does not have to scroll the map all around to see the
  
  whole
  
   route...  Zoom level 3 where the items become visible is of no use - 
it
   only fits a very small part of the what I need to show at once...
   Everything worked so well in Qt4.8/QtMobility.location 1.2
   
   Many thanks, bolek
   ___
   SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Putting data with QML on first screen after power on ?

[Martin Kampas]

Hi,

see https://sailfishos.org/core-article.html for UX elements naming.

BR,
Martin

On Tuesday, January 07, 2014 12:46:28 PM Matthias Barmeier wrote:
 Hi,
 
 is it possible to add notification, calendar entries or something else
 on the first screen with QML ?
 
 Does an official name for all the screens exists ?
 
 There is the screen after the device is double tapped or the power
 button is pressed,
 the screen when you scroll down and the screen that contains the apps.
 
 It would be helpful for searching that there is a reliable terminology.
 
 Ciao
 Matze
 ___
 SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Installation trouble with the SDK

[Martin Kampas]

Hi Luciano,

is it possible it just hangs waiting for enough entropy[1] to generate the 
keys? How long did you wait before you rebooted? Try to keep moving the mouse 
pointer randomly for about a minute - it may help.

If it does not help, you should be at least able to switch to VT console 
(Ctrl+Alt+F1) and kill the installer process without rebooting.

BR,
Martin

[1] http://en.wikipedia.org/wiki/Entropy_(computing) 

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

Re: [SailfishDevel] Installation trouble with the SDK

[Martin Kampas]

Hi Luciano,

On Thursday, December 11, 2014 10:21:16 AM Luciano Montanaro wrote:
 [...] My question is...
 shouldn't there be a virtualbox mersdk instance available before
 invoking the merssh command? Because the virtualbox manager does not
 show a configuration for it.

this shouldn't be an issue here - the keys are stored on host, in a directory 
shared with the VM [1].

BTW, earlier you wrote:

 [...] and I unwisely removed the SailfishOS directory

IIUC you didn't use the uninstaller - it might be worth to search your home 
directory for garbage from the previous installation which may possibly cause 
some troubles.. Also consider removing (renaming) ~/.config/SailfishAlpha4.

BR,
Martin

[1] 
https://github.com/sailfish-sdk/sailfish-qtcreator/blob/next/src/tools/merssh/generatekeyscommand.cpp
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] SDK version 1510 (1.1.9) is released

[Martin Kampas]

Hello Thomas,

> Somehow the "unfoldability" of the Silica reference has gone AWOL in the 
> process.

Thanks for reporting this - fixed, to be released soon.

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

[SailfishDevel] SDK version 1511 (2.0.0) is released

[Martin Kampas]

Hello again,

Today (November 10th) at 11:30 UTC we have published new installers and
repositories of the Sailfish OS SDK. This SDK release is called 1511 and it
matches Jolla Release 2.0.0.

The installers for this release of the SDK are available at
http://www.sailfishos.org. If you have an older beta release of the SDK,
you should see an update notification in the SailfishOS IDE.

SDK content matches Jolla Release 2.0.0.10 (Saimaa). 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
reinstalled 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.

- 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/develop/sdk-overview/sdk-release-notes/

- For more information, please see the SDK Beta-Qt5 known issues list
at: https://sailfishos.org/develop/sdk-overview/sdk-beta-qt5-known-issues/.

SDK IDE (Qt Creator):
- Qt Creator updated to version 3.5
- Jolla application template now supports application icon in multiple sizes
- Refreshed API documentation available in the Help mode (Ctrl+7) in Qt Creator 
to Jolla release 2.0.0.10 level
- Sailfish Silica API documentation have working table of contents again

SDK Build engine:
- Build targets refreshed to Jolla release 2.0.0.10 level
- Applications using libsailfishapp can set SAILFISHAPP_ICONS qmake variable 
(*) to provide application icon in multiple sizes
- Harbour RPM validator updated

*) See 
https://github.com/sailfish-sdk/libsailfishapp/blob/master/docs/documentation.mdown

Emulator:
- Emulator packages refreshed to Jolla release 2.0.0.10 level
- Fixed TimePickerDialog appearance in Components Gallery

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

Happy hacking,
Jolla SDK Team

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

Re: [SailfishDevel] SDK version 1511 (2.0.0) is released

[Martin Kampas]

Hello Alexander,

Design feature (for Sailfish QML components) has been unmaintaned for long time 
and it used to be hidden/disabled by default. In SDK-1511 it was left enabled 
by mistake.

You can hide the design mode by disabling the "Designer" and "QmlDesigner" 
plugin in "About Plugins" dialog if it helps you.

BR,
Martin


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Alexander Ladygin [fake...@gmail.com]
Sent: Tuesday, November 10, 2015 1:45 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] SDK version 1511 (2.0.0) is released

updated for me just fine!
Design feature does not work though... should it?

On Tue, Nov 10, 2015 at 3:36 PM, Peter Pykäläinen 
<peter.pykalai...@gmail.com<mailto:peter.pykalai...@gmail.com>> wrote:
Hi,

Tried to update my version, but SDK updater gives checksum mismatch.
Please fix.


// Peter Pykäläinen

2015-11-10 13:55 GMT+02:00 Martin Kampas 
<martin.kam...@jolla.com<mailto:martin.kam...@jolla.com>>:
Hello again,

Today (November 10th) at 11:30 UTC we have published new installers and
repositories of the Sailfish OS SDK. This SDK release is called 1511 and it
matches Jolla Release 2.0.0.

The installers for this release of the SDK are available at
http://www.sailfishos.org. If you have an older beta release of the SDK,
you should see an update notification in the SailfishOS IDE.

SDK content matches Jolla Release 2.0.0.10 (Saimaa). 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
reinstalled 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.

- 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/develop/sdk-overview/sdk-release-notes/

- For more information, please see the SDK Beta-Qt5 known issues list
at: https://sailfishos.org/develop/sdk-overview/sdk-beta-qt5-known-issues/.

SDK IDE (Qt Creator):
- Qt Creator updated to version 3.5
- Jolla application template now supports application icon in multiple sizes
- Refreshed API documentation available in the Help mode (Ctrl+7) in Qt Creator 
to Jolla release 2.0.0.10 level
- Sailfish Silica API documentation have working table of contents again

SDK Build engine:
- Build targets refreshed to Jolla release 2.0.0.10 level
- Applications using libsailfishapp can set SAILFISHAPP_ICONS qmake variable 
(*) to provide application icon in multiple sizes
- Harbour RPM validator updated

*) See 
https://github.com/sailfish-sdk/libsailfishapp/blob/master/docs/documentation.mdown

Emulator:
- Emulator packages refreshed to Jolla release 2.0.0.10 level
- Fixed TimePickerDialog appearance in Components Gallery

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

Happy hacking,
Jolla SDK Team


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


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

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

Re: [SailfishDevel] Help,,,SDK don't love my jolla phone

[Martin Kampas]

Hello yinweijianyinweijian,

If your SailfishOS version is 2.0.0 and your SDK is 1510 then this is most 
probably due to SSH incompatibility after dropping support for the unsafe 
aes128-cbc cipher from the phone.

Upgrading to SDK-1511 (released yesterday November 10th) should fix this for 
you.

BR,
Martin


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of yinweijianyinweijian [iamyinweij...@outlook.com]
Sent: Wednesday, November 11, 2015 2:36 AM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Help,,,SDK don't love my jolla phone

Hello ,Recently,I can't connect my jolla with the latest SDK,something happened 
just like Pictures.
I set anything well,like "open developer model ","set password or auto get 
password","recover jolla","reset SDK"... but nothing happend.
A long time ago it can work.,but now,it "sleep".My computer system is 
WIN7&64bit,can you help me?Thanks[Emoji]
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Help,,,SDK don't love my jolla phone

[Martin Kampas]

oops you are right, 2.0.0.x is still OK, this only comes with 2.0.1.x.
-Martin

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Tone Kastlunger [users.giulie...@gmail.com]
Sent: Wednesday, November 11, 2015 7:59 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Help,,,SDK don't love my jolla phone

Funny; i've been on 1510 for a month now, no issues with 2.0.0.10?

On Wed, Nov 11, 2015 at 8:25 AM, Martin Kampas 
<martin.kam...@jolla.com<mailto:martin.kam...@jolla.com>> wrote:
Hello yinweijianyinweijian,

If your SailfishOS version is 2.0.0 and your SDK is 1510 then this is most 
probably due to SSH incompatibility after dropping support for the unsafe 
aes128-cbc cipher from the phone.

Upgrading to SDK-1511 (released yesterday November 10th) should fix this for 
you.

BR,
Martin


From: 
devel-boun...@lists.sailfishos.org<mailto:devel-boun...@lists.sailfishos.org> 
[devel-boun...@lists.sailfishos.org<mailto:devel-boun...@lists.sailfishos.org>] 
on behalf of yinweijianyinweijian 
[iamyinweij...@outlook.com<mailto:iamyinweij...@outlook.com>]
Sent: Wednesday, November 11, 2015 2:36 AM
To: devel@lists.sailfishos.org<mailto:devel@lists.sailfishos.org>
Subject: [SailfishDevel] Help,,,SDK don't love my jolla phone

Hello ,Recently,I can't connect my jolla with the latest SDK,something happened 
just like Pictures.
I set anything well,like "open developer model ","set password or auto get 
password","recover jolla","reset SDK"... but nothing happend.
A long time ago it can work.,but now,it "sleep".My computer system is 
WIN7&64bit,can you help me?Thanks[Emoji]

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

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

Re: [SailfishDevel] Help,,,SDK don't love my jolla phone

[Martin Kampas]

Hello yinweijianyinweijian,

only now I noticed in your configuration SSH port is set to 2223 - this should 
be 22 unless you changed your phone settings somehow.

BR,
Martin


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Martin Kampas [martin.kam...@jolla.com]
Sent: Wednesday, November 11, 2015 9:04 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Help,,,SDK don't love my jolla phone

oops you are right, 2.0.0.x is still OK, this only comes with 2.0.1.x.
-Martin

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Tone Kastlunger [users.giulie...@gmail.com]
Sent: Wednesday, November 11, 2015 7:59 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Help,,,SDK don't love my jolla phone

Funny; i've been on 1510 for a month now, no issues with 2.0.0.10?

On Wed, Nov 11, 2015 at 8:25 AM, Martin Kampas 
<martin.kam...@jolla.com<mailto:martin.kam...@jolla.com>> wrote:
Hello yinweijianyinweijian,

If your SailfishOS version is 2.0.0 and your SDK is 1510 then this is most 
probably due to SSH incompatibility after dropping support for the unsafe 
aes128-cbc cipher from the phone.

Upgrading to SDK-1511 (released yesterday November 10th) should fix this for 
you.

BR,
Martin


From: 
devel-boun...@lists.sailfishos.org<mailto:devel-boun...@lists.sailfishos.org> 
[devel-boun...@lists.sailfishos.org<mailto:devel-boun...@lists.sailfishos.org>] 
on behalf of yinweijianyinweijian 
[iamyinweij...@outlook.com<mailto:iamyinweij...@outlook.com>]
Sent: Wednesday, November 11, 2015 2:36 AM
To: devel@lists.sailfishos.org<mailto:devel@lists.sailfishos.org>
Subject: [SailfishDevel] Help,,,SDK don't love my jolla phone

Hello ,Recently,I can't connect my jolla with the latest SDK,something happened 
just like Pictures.
I set anything well,like "open developer model ","set password or auto get 
password","recover jolla","reset SDK"... but nothing happend.
A long time ago it can work.,but now,it "sleep".My computer system is 
WIN7&64bit,can you help me?Thanks[Emoji]

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

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

Re: [SailfishDevel] SailfishOS SDK 1510 and launcher icon for tablet version

[Martin Kampas]

On 20.10.2015 19:02, Osmo Salomaa wrote:
> This is the first time I hear this. Is this documented somewhere?

https://harbour.jolla.com/faq#Icons

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

[SailfishDevel] SDK version 1510 (1.1.9) is released

[Martin Kampas]

Hello again,

Today (October 9th) at 10:00 UTC we have published new installers and
repositories of the Sailfish OS SDK. This SDK release is called 1510,
it is mainly a bugfix release and it again matches Jolla Release 1.1.9.

The installers for this release of the SDK are available at
http://www.sailfishos.org. If you have an older beta release of the SDK,
you should see an update notification in the SailfishOS IDE.

SDK content matches Jolla Release 1.1.9.28 (Eineheminlampi). 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
reinstalled 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.

- 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/develop/sdk-overview/sdk-release-notes/

- For more information, please see the SDK Beta-Qt5 known issues list
at: https://sailfishos.org/develop/sdk-overview/sdk-beta-qt5-known-issues/.

SDK IDE (Qt Creator):
- Updated icon reference documentation
- Updated Notification API documentation
- Updated DBus API documentation
- Added Configuration (DConf) API documentation

(All the updated documentation entries are available in the Help mode (Ctrl+7) 
in Qt Creator.)

SDK Build engine:
- Harbour RPM validator updated

Emulator:
- Fixed issue with emulator mode switching on Windows (Emulator mode can be 
changed under menu Tools -> Mer in Qt Creator)

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

Happy hacking,
Jolla SDK Team

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

Re: [SailfishDevel] SDK version 1510 (1.1.9) is released

[Martin Kampas]

Hi John,

what version of OS X and VirtualBox do you use? I couldn't reproduce this with 
OS X 10.8 and VirtualBox 5.0.

Could you please paste the output of the following command?

   VBoxManage getextradata 'SailfishOS Emulator' 'Mer/DeviceModels' |hexdump -C

(you may need to type full path to VBoxManage if it is in /usr/local/bin)

BR,
Martin


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of John Pietrzak [jpietrz...@gmail.com]
Sent: Saturday, October 10, 2015 5:52 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] SDK version 1510 (1.1.9) is released

Hi Martin & everybody,

There still seems to be a problem switching the emulator mode on OS X; I'm only 
given a single choice of "Jolla Phone (540x960)".  Maybe there is a fix 
available similar to the problem under Windows?

Thanks!

--John

On 10/9/15 6:22 AM, Martin Kampas wrote:
Emulator:
- Fixed issue with emulator mode switching on Windows (Emulator mode can be 
changed under menu Tools -> Mer in Qt Creator)

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

Re: [SailfishDevel] How to use nemo-qml-plugin-notifications?

[Martin Kampas]

Hello Иван Черненький,

You hit a bug. Please follow this 
https://bugs.merproject.org/show_bug.cgi?id=1360

You can still use nemo-qml-plugin-notifications in your app - missing 
plugin.qmltypes only affects the autocompletion feature of Qt Creator.

BR,
Martin


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Иван Черненький [chei...@mail.ru]
Sent: Sunday, October 04, 2015 5:40 PM
To: Andrey Kozhevnikov; devel
Subject: Re: [SailfishDevel] How to use nemo-qml-plugin-notifications?

Doesn't help. QtCreator still does not see import.

I'm now using mlite5 for notifications. How bad is that?


Воскресенье, 4 октября 2015, 11:43 UTC от "Andrey Kozhevnikov" 
:

You might like this: https://github.com/CODeRUS/better-sailfishos-qmltypes
Jolla for some reason is not shipping proper plugin.qmltypes for nemomobile 
stuff

-- Исходное сообщение --
От: "Иван Черненький" 

Кому: "devel" 

Отправлено: 04.10.2015 16:37:08
Тема: [SailfishDevel] How to use nemo-qml-plugin-notifications?

Hello everyone!

I am trying to use nemo-qml-plugin-notifications in my app.
In documentation is wrote:

import org.nemomobile notifications .

but this import doesn't recognized by QtCreator. What should i import?

I'm trying to send notification to events view of Sailfish OS.


--
С уважением, Иван Черненький


--
С уважением, Иван Черненький
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

[SailfishDevel] SDK version 1.1.9 is released

[Martin Kampas]

Hello again,

Today (September 24th) at 11:00 UTC we have published new installers and 
repositories of the Sailfish OS SDK. This SDK release is called the 1509 
and it matches the Jolla Release 1.1.9.

The installers for this release of the SDK are available at 
http://www.sailfishos.org. If you have an older beta release of the SDK, 
you should see an update notification in the SailfishOS IDE.

SDK content has been updated to match Jolla Release 1.1.9.28 
(Eineheminlampi). 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 
reinstalled 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.

- 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/develop/sdk-overview/sdk-release-notes/

- For more information, please see the SDK Beta-Qt5 known issues list 
at: https://sailfishos.org/develop/sdk-overview/sdk-beta-qt5-known-issues/.

General:
- Enabled development for Jolla tablet (Emulator mode can be changed under menu 
Tools -> Mer in Qt Creator)
- Added compatibility with VirtualBox 5

SDK IDE (Qt Creator):
- Updated Sailfish Silica help documentation and examples

SDK Build engine:
- Build targets refreshed to Jolla release 1.1.9.28 level

Emulator:
- Emulator packages refreshed to Jolla release 1.1.9.28 level

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

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

Re: [SailfishDevel] QtCreator CONFIG has debug even in release mode

[Martin Kampas]

Hello Tone Kastlunger,

Read this carefully to learn how to test these properly 
http://doc.qt.io/qt-5/qmake-test-function-reference.html#config-config

BR,
Martin


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Tone Kastlunger [users.giulie...@gmail.com]
Sent: Sunday, October 18, 2015 12:16 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] QtCreator CONFIG has debug even in release mode

Right out of the box.

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

Re: [SailfishDevel] Not documented missing SDK features

[Martin Kampas]

Hello Eli,

here https://sailfishos.org/wiki/Application_SDK_Known_Issues you can find the 
list of known issues related to the SDK. Seems you just hit an unknown one. 
Thank you for reporting!

Regards,
Martin


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of E.S. Rosenberg [es.rosenberg+sailfishos@gmail.com]
Sent: Monday, June 13, 2016 11:39 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Not documented missing SDK features

I don't mind the fact that they are missing, I mind the fact that the SDK 
doesn't give a clear error and that it is not documented, instead of spending 
my time in a useful way I spent it trying to solve a problem that wasn't there 
because the error doesn't read "not implemented" but rather a potentially 
normal error that could be caused by a ton of different things...

2016-06-13 12:24 GMT+03:00 Alexey Andreyev 
>:
Hello! I'm not from Jolla, but I'm also working with the SDK.
As I can see, Jolla is not a super-huge company, but there are a lot of hard 
tasks to solve...
I know some guy (also not from Jolla) who also needs some missing SDK emulator 
features (let's say GPS coords, etc),
if you want to help, we can start some project to implement missing SDK 
features for the emulator.

2016-06-13 11:00 GMT+03:00 E.S. Rosenberg 
>:
Hi all,
After a week of trying to get sound working on the SDK only to discover that 
the issue is the SDK doens't support it while my code works on my phone I can 
only say I a very miffed.
Why doesn't the error message in the SDK reflect the fact that it shouldn't 
work?
Or the docs, why is there no mention of this?
Why do I need to find a forum discussion that says "Oh yes, use your phone as a 
deploy device instead"?

I hope someone from Jolla on the list sees this and does something about it, 
because waisting your developers' time is just about the best way of showing 
you don't respect them.

Regards,
Eli

___
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] Not documented missing SDK features

[Martin Kampas]

Hello Eli,

I have tested SoundEffect and Audio QML elements with SDK-1602 on Linux and it 
worked.

SoundEffect element worked out of box. For Audio element to work I had to 
package my app with  "Requires: 
qt5-qtmultimedia-plugin-mediaservice-gstmediaplayer". There was a warning on 
application output which helped me to identify the missing requirements:

[W] QPluginServiceProvider::requestService:437 - 
defaultServiceProvider::requestService(): no service found for - 
"org.qt-project.qt.mediaplayer"

Does sound work for you at all in emulator? E.g. sound effects when closing 
applications or pulling down menus? What about "paplay 
/usr/share/sounds/jolla-ringtones/stereo/jolla-ringtone.wav" executed on 
emulator (logged in as user "nemo", not "root")?

What platform do you use the SDK on? What is your VirtualBox version?

BR,
Martin


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Martin Kampas [martin.kam...@jolla.com]
Sent: Monday, June 13, 2016 2:21 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Not documented missing SDK features

Hello Eli,

here 
https://sailfishos.org/wiki/Application_SDK_Known_Issues<redir.aspx?REF=gQ3KQKIHjqU7l4WXAu6xr537olQe2Vz7xb4rxym24hYE1mkSKJ_TCAFodHRwczovL3NhaWxmaXNob3Mub3JnL3dpa2kvQXBwbGljYXRpb25fU0RLX0tub3duX0lzc3Vlcw..>
 you can find the list of known issues related to the SDK. Seems you just hit 
an unknown one. Thank you for reporting!

Regards,
Martin


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of E.S. Rosenberg [es.rosenberg+sailfishos@gmail.com]
Sent: Monday, June 13, 2016 11:39 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Not documented missing SDK features

I don't mind the fact that they are missing, I mind the fact that the SDK 
doesn't give a clear error and that it is not documented, instead of spending 
my time in a useful way I spent it trying to solve a problem that wasn't there 
because the error doesn't read "not implemented" but rather a potentially 
normal error that could be caused by a ton of different things...

2016-06-13 12:24 GMT+03:00 Alexey Andreyev 
<yetanotherandre...@gmail.com>:
Hello! I'm not from Jolla, but I'm also working with the SDK.
As I can see, Jolla is not a super-huge company, but there are a lot of hard 
tasks to solve...
I know some guy (also not from Jolla) who also needs some missing SDK emulator 
features (let's say GPS coords, etc),
if you want to help, we can start some project to implement missing SDK 
features for the emulator.

2016-06-13 11:00 GMT+03:00 E.S. Rosenberg 
<es.rosenberg+sailfishos@gmail.com>:
Hi all,
After a week of trying to get sound working on the SDK only to discover that 
the issue is the SDK doens't support it while my code works on my phone I can 
only say I a very miffed.
Why doesn't the error message in the SDK reflect the fact that it shouldn't 
work?
Or the docs, why is there no mention of this?
Why do I need to find a forum discussion that says "Oh yes, use your phone as a 
deploy device instead"?

I hope someone from Jolla on the list sees this and does something about it, 
because waisting your developers' time is just about the best way of showing 
you don't respect them.

Regards,
Eli

___
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] Deploy as RPM package vs copying binaries

[Martin Kampas]

Hi Dylan,

could you describe step by step your procedure from unpacking the source 
archive from your original message to installing the resulting RPM package? And 
attach the output of 'rpm -qlp Sailfinder-0.1-1.armv7hl.rpm'?

Martin


From: Dylan Van Assche [dylan.van.ass...@protonmail.com]
Sent: Wednesday, March 23, 2016 12:19 PM
To: Martin Kampas
Subject: Re: [SailfishDevel] Deploy as RPM package vs copying binaries

Hi,

No it was, I think it's a bug in QT creator...
Time for an update?

Dylan


Sent from ProtonMail mobile



 Original Message 
On 10:15, 23 Mar 2016, Martin Kampas wrote:

Hello Dylan,

does this still persist? I tried to build and use RPMs from your sources and it 
worked.

BR,
Martin


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Dylan Van Assche [dylan.van.ass...@protonmail.com]
Sent: Thursday, March 17, 2016 10:30 PM
To: Sailfish OS Developers
Subject: [SailfishDevel] Deploy as RPM package vs copying binaries

Dear developers,

I just finished my app and I'm ready to pack it into an RPM.
I used the 'copying binaries' method when I developed it and that worked fine 
since it copies all the files piece by piece to my Jolla.
However when I use 'deploy as RPM package' method I'm getting in trouble with 
the dependencies. I expected that I have to change my .pro file to include my 
dependencies, which I did.
QT creator shows in the project tree those files on 'Other files'.
I haven't changed the .yaml file since all my dependencies are in the 'qml' 
folder which is already covered by the .yaml file (as far as I understand it).

When I try to deploy the RPM package I get this error:


[W] unknown:-1 - file:///usr/share/Sailfinder/qml/Sailfinder.qml: File not found

The app can't find the page Sailfinder.qml (which is the page that calls the 
firstPage).
I'm not experienced with QT since it's my first app for Sailfish OS, so I don't 
know what to do (I already read the 'packaging apps' tutorial on 
sailfishos.org)...
Here's a link to my project as a ZIP file since it's too big to send it as an 
attachment to the mailing list: 
mega.nz/#!Xt0QlCbJ!kvPIGNriIVEtQ9cg1d1qDFNDz65II_XjtRSwjSdWE9M<https://mega.nz/#!Xt0QlCbJ!kvPIGNriIVEtQ9cg1d1qDFNDz65II_XjtRSwjSdWE9M>
I hope somebody can help?

Regards,
Dylan

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

Re: [SailfishDevel] Using QtQuick.Layouts

[Martin Kampas]

Hi Marcin,

> Is it possible to change the port for the SailifshOS tab? I have tty.js
> running on the same port, had to kill it.

Yes.

1. Stop the MerSDK VM
2. Open MerSDK VM settings in VirtualBox, navigate to Network -> Adapter 1 -> 
Advanced -> Port Forwarding and change the Host Port there.
3. In Qt Creator go to Options -> Mer -> SDK, remove the VM, confirm with 
Apply, then re-Add it. (Tick the No window checkbox to get the original 
headless behavior.)

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

Re: [SailfishDevel] The SailfishOS IDE todo plugin doesn't work

[Martin Kampas]

Hi Marcin,

For me it works well. Did you notice you can switch between displaying TODOs 
from current document only or from all documents in the active project in the 
To-Do Entries output pane? Could you please provide a detailed step-by-step 
description what did you do?

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

Re: [SailfishDevel] Option to extract content of Sailfish SDK

[Martin Kampas]

Hi Louis,

The Sailfish OS SDK installer application is based on Qt Installer Framework 
[1]. You can write a script to instruct the installer and pass it via the 
'-script' command line switch. There is also a client-server mode available so 
that you can instruct the installer interactively.

BR,
Martin

[1] http://doc.qt.io/qtinstallerframework/
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

[Martin Kampas]

Hi Marcin,

failed.log, statefs.log: both failing statefs and tmpfiles are known issues and 
shouldn't be related to this.

sshd.log: according to the log you mistyped "sshd" as "ssh", but anyway 
"sshd.service" is not used, instead you should check the status of 
"sshd.socket". Also note that the config is "/etc/ssh/sshd_config_engine".

If the output of `journalctl _COMM=sshd -b` was empty after trying to log in 
via SSH even with verbosity increased, then my suspicion falls on 
host/virtualbox.

You could also verify with tcpdump that it did not reach the guest (install 
with `zypper in tcpdump`, run as `tcpdump -n port ssh` inside the MerSDK VM). 
And on host you can check that the ports are really occupied by virtualbox with 
`sudo ss -tpln |grep ':222[23]\>'`.

I am also using Arch Linux as you (last full system upgrade on 2016-06-28) and 
it works well. Did you try reboot? :)

BR,
Martin

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

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

[Martin Kampas]

Hi Marcin,

Could you check SSH logs on the VM side? For that purpose please start the 
MerSDK VM directly from VirtualBox and quit Qt Creator *before* that (it would 
try to reconnect periodically, filling the log excessively). Started this way 
the MerSDK VM will show its window - read the instructions there, log in, then 
check logs e.g. with 'journalctl -b _COMM=sshd' before/after trying to log in 
via SSH. Possibly increase SSH verbosity on both client and server side.

You can copy logs from the VM via /home/mersdk/share/ which is mapped to your 
HOME by default.

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

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

[Martin Kampas]

Hi Marcin,

> Before and after: No journal files were found.

Did you run it as root?

BR,
Martin

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

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

[Martin Kampas]

Hi Marcin,

Simply move the -b switch to the very end of the command line: `journalctl 
_COMM=sshd -b` so that it does not treat "_COMM=sshd" as an argument to it.

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

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

[Martin Kampas]

Hi Marcin,

> ssh_exchange_identification: read: Connection reset by peer

Could this be result of some firewall or mandatory access control  (SELinux, 
AppArmor, ...) on your installation? (Can you SSH to any other VirtualBox VM? 
If you have no other VM, could you install e.g. Arch Linux in your VirtualBox, 
setup port forwarding like it is done with build VM and emulator from Sailfish 
SDK and check if you can SSH to it?)

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

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

[Martin Kampas]

Hi Marcin,

Does SSH-ing from command line work?

For emulator you can try:

ssh -i ~/devel/SailfishOS/vmshare/ssh/private_keys/SailfishOS_Emulator/root -p 
2223 root@localhost -o StrictHostKeyChecking=no

For build engine:

ssh -i ~/devel/SailfishOS/vmshare/ssh/private_keys/engine/root -p  
root@localhost -o StrictHostKeyChecking=no

Please ensure you use correct path according to your install location above - 
from the log output you provided I guess you installed to ~/devel/SailfishOS.

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

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

[Martin Kampas]

Hi Marcin,

> Anyway, the SDK reported a timeout and asked whether I want to try running 
> the emulator again.

What happened then? Did the message window persisted (re-)appearing on the 
screen indefinitely?

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

Re: [SailfishDevel] SDK Maintenance Tool - partial upgrades?

[Martin Kampas]

Hi Marcin,

You can make local copy of the repositories with some tool which supports 
resuming, e.g. wget, and then add these in SDK Maintenance Tool settings. Most 
recent repositories can be downloaded here 
http://releases.sailfishos.org/sdk/repository/ . You will need the "common" 
repository and the one for your platform.

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

Re: [SailfishDevel] Using QtQuick.Layouts

[Martin Kampas]

Hi Marcin,

Yes, see https://sailfishos.org/wiki/Tutorial_-_Building_packages_manually

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

Re: [SailfishDevel] Debugging a segmentation fault

[Martin Kampas]

Hello Костадин,

gdb's "exec-wrapper" option should help you.

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Костадин Дамянов 
[maxmi...@gmail.com]
Sent: Sunday, January 22, 2017 8:45 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Debugging a segmentation fault

Hello.

I am trying to build a project that is not developed in Sailfish IDE.
I managed to build in the SDK VM and deploy it on the emulator VM.

My problem is that the app segfaults on startup and I do not know how to debug 
the crash.
One way to launch it is by running

xdg-open /usr/shared/applications/harbour-.desktop

It starts loading the application and it crashes at start so I have no time to 
attach gdb.
My question is: is there a way to start the app in such a way as to connect gdb.
Is it possible to connect gdb remotely?
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Translation support broken? | Re: SDK version 1701 (2.1.0) is released to Early Access

[Martin Kampas]

Hi micu,

As a workaround until a fixed version of the SDK is released you can execute 
this command inside the build engine VM:

sb2-config -l |xargs -I{} sb2 -t {} -R sed -i 's/\\"//g' 
/usr/share/qt5/mkspecs/features/sailfishapp_i18n.prf

Undo the change with:

sb2-config -l |xargs -I{} sb2 -t {} -R -m sdk-install zypper in -fy 
libsailfishapp-devel

(Some info on how to enter the build VM can be found here 
https://sailfishos.org/wiki/Tutorial_-_Building_packages_manually)

BR,
Martin


From: Martin Kampas
Sent: Thursday, February 23, 2017 11:00 AM
To: Sailfish OS Developers
Subject: RE: [SailfishDevel] Translation support broken? | Re: SDK version 1701 
(2.1.0) is released to Early Access

Hi micu,

I can confirm it can be reproduced - the build is not terminated though and I 
never scrolled up enough to check the output!

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Martin Kampas 
[martin.kam...@jolla.com]
Sent: Monday, February 13, 2017 11:52 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Translation support broken? | Re: SDK version 1701 
(2.1.0) is released to Early Access

Hi micu,

For me it works also with the development branch 
(6d90504b299505465e3a7a5278704ffba7c2ea27). I also tried with an updated 
installation of SDK (1611->1701), instead of a clean installation. Is there 
anything special about your installation?

BR,
Martin
___
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] Translation support broken? | Re: SDK version 1701 (2.1.0) is released to Early Access

[Martin Kampas]

Hi micu,

I can confirm it can be reproduced - the build is not terminated though and I 
never scrolled up enough to check the output!

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Martin Kampas 
[martin.kam...@jolla.com]
Sent: Monday, February 13, 2017 11:52 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Translation support broken? | Re: SDK version 1701 
(2.1.0) is released to Early Access

Hi micu,

For me it works also with the development branch 
(6d90504b299505465e3a7a5278704ffba7c2ea27). I also tried with an updated 
installation of SDK (1611->1701), instead of a clean installation. Is there 
anything special about your installation?

BR,
Martin
___
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] QtLocstion (5.6) | Re: SDK version 1701 (2.1.0) is released to Early Access

[Martin Kampas]

Hi Martin

> Is there a listing of Qt 5 modules available on Sailfish OS and their status 
> (version & usability in Jolla store applications) ? It would be very useful 
> for application developers.

Does this help you?
https://harbour.jolla.com/faq#2.16.0
https://harbour.jolla.com/faq#5.1.0
https://harbour.jolla.com/faq#6.1.0
+ simply query the exact version available directly on your device/emulator.

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

Re: [SailfishDevel] Translation support broken? | Re: SDK version 1701 (2.1.0) is released to Early Access

[Martin Kampas]

Hi micu,

I could not reproduce this with

1) sources from "master" branch from 
https://github.com/micuintus/harbour-Berlin-Vegan, and
2) cleanly installed SDK 1701, accepting defaults during installation

Any suggestion?

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of micu 
[micuin...@gmx.de]
Sent: Saturday, February 11, 2017 2:14 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Translation support broken? | Re: SDK version 1701 
(2.1.0) is released to Early Access

Hi there,

It's me again ;) --- another thing:

Is it possible that the translation support is broken with the new SDK --- or
do I need to do sth. different?

Somehow my qm's aren't generated correctly anymore (automatically):

> install: cannot stat
> `/home/mersdk/share/devel/projects/Sailfish/harbour-Berlin-vegan//home/mers
> dk/share/devel/projects/Sailfish/build-BerlinVegan-MerSDK_SailfishOS_armv7hl
> -Debug/translations/harbour-berlin-vegan-de.qm': No such file or directory
> make: [install_qm] Error 1 (ignored)
> install -m 644 -p
> /home/mersdk/share/devel/projects/Sailfish/harbour-Berlin-vegan/"/home/mers
> dk/share/devel/projects/Sailfish/build-BerlinVegan-MerSDK_SailfishOS_armv7hl
> -Debug/translations/harbour-berlin-vegan-en.qm"
> /home/deploy/installroot/usr/share/harbour-berlin-vegan/translations/
> install: cannot stat
> `/home/mersdk/share/devel/projects/Sailfish/harbour-Berlin-vegan//home/mers
> dk/share/devel/projects/Sailfish/build-BerlinVegan-MerSDK_SailfishOS_armv7hl
> -Debug/translations/harbour-berlin-vegan-en.qm': No such file or directory
> make: [install_qm] Error 1 (ignored)

It works fine with the current stable SDK --- I am using ID based
translations.

Best,
micu
--
OpenPGP / GnuPG:0xE4CB4E80
Fingerprint:1A15 A480 1F8B 07F6 9D12 3426 CEFE 7455 E4CB 4E80

<<>

http://www.micuintus.de
___
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] SDK version 1701 (2.1.0) is released to Early Access

[Martin Kampas]

Hi Michael,

Could you please try to run c:\SailfishOS\bin\qmllivebench.exe with the 
QT_OPENGL environment variable subsequently set to "desktop", "angle" and 
"software"?

(Before we fix this you can configure Qt Creator to work with your own build of 
QmlLive - just go to Qt Creator's menu Tools > Options > Mer > General and set 
Bench location to the binary you built from source. Restart Qt Creator after 
this.)

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Michael Neufing 
[mich...@neufing.org]
Sent: Friday, February 10, 2017 10:22 PM
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] SDK version 1701 (2.1.0) is released to Early 
Access

Hi Martin,

thank you for the reply.
I pasted the debugger log to pastebin [1].

When I build the project from the sources with Qt 5.8.0
(MSVC2015_64bit), the project can be started without any problems.

BR,
Michael

[1] http://pastebin.com/aqH2Nzw7


Am 10.02.2017 07:59, schrieb Martin Kampas:
> Hi Michael,
>
> Could you please follow these steps to provide more information?
>
> 1. Launch a vanilla Qt Creator, NOT the one comming with Sailfish OS
> SDK
> 2. Go to menu Debug > Start Debugging > Start and debug external
> application...
> 3. Browse for C:\SailfishOS\bin\qmllivebench.exe and start it
> 4. Go back to Qt Creator
> 5. Go to menu Window > Views and enable Debugger log
> 6. Right click in Backtrace view and choose Create full backtrace
> 7. Right click in Debugger log view and choose Save contents - paste
> the resulting file
>
> It would be also nice if you try to build & run QmlLive Bench from
> here https://github.com/sailfish-sdk/qmllive
>
> BR,
> Martin
>
> 
> From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Michael
> Neufing [mich...@neufing.org]
> Sent: Thursday, February 09, 2017 6:44 PM
> To: devel@lists.sailfishos.org
> Subject: Re: [SailfishDevel] SDK version 1701 (2.1.0) is released to
> Early Access
>
> Hi,
> nice update!
>
> Unfortunately I am not able to test the new QML live coding, as the
> qmllivebench.exe crashes directly after the window appears
> ("qmllivebench.exe has stopped working").
> I am on a Windows 10 machine (insider preview).
> I tried to run it as Administrator and even though CMD in the hope to
> get some useful output there... But nothing...
>
> Can you help me with this problem?
>
> Thanks!
>
> Michael
>
>
> Am 09.02.2017 14:08, schrieb Jarkko Lehtoranta:
>> Hello,
>>
>> Today (Feb 9th) at 13:00 UTC we have published new installers and
>> repositories of the Sailfish OS SDK. This SDK release is called 1701
>> and it matches Jolla Release 2.1.0.
>>
>> Please, read the following notes about the Early Access SDK:
>> - By using the Early Access SDK developers can test their Sailfish OS
>> apps a week before the Sailfish OS release is made public
>> - During the early access time the Early Access SDK should not be used
>> for submitting apps to the Jolla Harbour
>> - The installers for this release of the SDK are available at
>> http://sailfishos.org/wiki/Application_SDK_Early_Access#Latest_Early_Access_SDK_Release
>> - Instructions for adding the early access repository into the SDK can
>> be found from
>> http://sailfishos.org/wiki/Application_SDK_Early_Access#Receiving_Early_Access_SDK_Updates_Automatically
>>
>> If you add the early access repository into your SDK and have an older
>> beta release of the SDK, you should see an update notification in the
>> Sailfish OS IDE. Otherwise, you will see an update notification in the
>> Sailfish OS IDE, when the Jolla Release 2.1.0 is publicly available to
>> all users.
>>
>> SDK content matches Jolla Release 2.1.0.9 (Iijoki). 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
>> reinstalled 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 A

Re: [SailfishDevel] Translation support broken? | Re: SDK version 1701 (2.1.0) is released to Early Access

[Martin Kampas]

Hi micu,

For me it works also with the development branch 
(6d90504b299505465e3a7a5278704ffba7c2ea27). I also tried with an updated 
installation of SDK (1611->1701), instead of a clean installation. Is there 
anything special about your installation?

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

Re: [SailfishDevel] SDK version 1701 (2.1.0) is released to Early Access

[Martin Kampas]

Hi Michael,

Could you please follow these steps to provide more information?

1. Launch a vanilla Qt Creator, NOT the one comming with Sailfish OS SDK
2. Go to menu Debug > Start Debugging > Start and debug external application...
3. Browse for C:\SailfishOS\bin\qmllivebench.exe and start it
4. Go back to Qt Creator
5. Go to menu Window > Views and enable Debugger log
6. Right click in Backtrace view and choose Create full backtrace
7. Right click in Debugger log view and choose Save contents - paste the 
resulting file

It would be also nice if you try to build & run QmlLive Bench from here 
https://github.com/sailfish-sdk/qmllive

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Michael Neufing 
[mich...@neufing.org]
Sent: Thursday, February 09, 2017 6:44 PM
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] SDK version 1701 (2.1.0) is released to Early 
Access

Hi,
nice update!

Unfortunately I am not able to test the new QML live coding, as the
qmllivebench.exe crashes directly after the window appears
("qmllivebench.exe has stopped working").
I am on a Windows 10 machine (insider preview).
I tried to run it as Administrator and even though CMD in the hope to
get some useful output there... But nothing...

Can you help me with this problem?

Thanks!

Michael


Am 09.02.2017 14:08, schrieb Jarkko Lehtoranta:
> Hello,
>
> Today (Feb 9th) at 13:00 UTC we have published new installers and
> repositories of the Sailfish OS SDK. This SDK release is called 1701
> and it matches Jolla Release 2.1.0.
>
> Please, read the following notes about the Early Access SDK:
> - By using the Early Access SDK developers can test their Sailfish OS
> apps a week before the Sailfish OS release is made public
> - During the early access time the Early Access SDK should not be used
> for submitting apps to the Jolla Harbour
> - The installers for this release of the SDK are available at
> http://sailfishos.org/wiki/Application_SDK_Early_Access#Latest_Early_Access_SDK_Release
> - Instructions for adding the early access repository into the SDK can
> be found from
> http://sailfishos.org/wiki/Application_SDK_Early_Access#Receiving_Early_Access_SDK_Updates_Automatically
>
> If you add the early access repository into your SDK and have an older
> beta release of the SDK, you should see an update notification in the
> Sailfish OS IDE. Otherwise, you will see an update notification in the
> Sailfish OS IDE, when the Jolla Release 2.1.0 is publicly available to
> all users.
>
> SDK content matches Jolla Release 2.1.0.9 (Iijoki). 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
> reinstalled 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.
> - Package repository contents have been updated and consequently using
> a previous SDK version with these package repositories is not
> supported.
> - For more information, please see the Application SDK known issues
> list at https://sailfishos.org/wiki/Application_SDK_Known_Issues.
>
>
> Release Content
>
> SDK IDE (Qt Creator, Qt QmlLive)
> - Refreshed API documentation available in the Help mode (Ctrl+7) in
> Qt Creator to Jolla release 2.1.0.9 level
> - Initial release of QML live coding support with Qt QmlLive. Check
> out the tutorial at
> https://sailfishos.org/wiki/Tutorial_-_QML_Live_Coding_With_Qt_QmlLive
>
> SDK Build engine
> - Build targets refreshed to Jolla release 2.1.0.9 level
> - Harbour RPM validator updated
>* Qt 5.6 module imports allowed
>* Relaxed app internal QML module naming rules. All module names
> are now allowed inside an app, except the ones used by the operating
> system.
>
> Emulator
> - Emulator packages refreshed to Jolla release 2.1.0.9 level
>
> If you have any questions, feel free to either send an email to this
> mailing list: devel at lists.sailfishos.org, write it up in
> http://together.jolla.com and tag your issue with 'sdk' or send an
> e-mail to developer-care at jolla.com.
>
> Happy hacking,
> Jolla SDK Team
> ___
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to
> devel-unsubscr...@lists.sailfishos.org
___
SailfishOS.org Devel mailing list
To unsubscribe, 

Re: [SailfishDevel] missing build dependencies in mersdk-VM

[Martin Kampas]

Hi Bernhard,
 
> I had installed some of them, but as far as I understood the behaviour of
> mb2, it should install missing dependencies automatically.
 
Correct
 
> So after manually installing all dependencies zypper could find, three
> packages cannot be found:
> pkgconfig(xtables)
> pkgconfig(libsystemd-daemon)
> pkgconfig(libglibutil)
 
I can confirm libglibutil-devel is missing from the public repos by mistake. It 
will be fixed in some of the upcoming releases - meanwhile you could build 
libglibutil yourself as a workaround 
https://git.merproject.org/mer-core/libglibutil .
 
The other two packages seems to be available in fresh installed Sailfish OS SDK 
1608 (latest):
 
[mersdk@SailfishSDK ~]$ sb2 -t SailfishOS-armv7hl -m sdk-install -R zypper wp 
'pkgconfig(xtables)'
Loading repository data...
Reading installed packages...
S | Name   | Type| Version  | Arch| Repository
--++-+--+-+---
  | iptables-devel | package | 1.4.15-1.1.3 | armv7hl | jolla 
[mersdk@SailfishSDK ~]$ sb2 -t SailfishOS-armv7hl -m sdk-install -R zypper wp 
'pkgconfig(libsystemd-daemon)'
Loading repository data...
Reading installed packages...
S | Name  | Type| Version   | Arch| Repository
--+---+-+---+-+---
  | systemd-devel | package | 208-1.9.1 | armv7hl | jolla 
[mersdk@SailfishSDK ~]$ sb2 -t SailfishOS-armv7hl -m sdk-install -R zypper wp 
'pkgconfig(libglibutil)'
Loading repository data...
Reading installed packages...
No providers of 'pkgconfig(libglibutil)' found.
 
BR,
Martin
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Debugging on emulator and/or device

[Martin Kampas]

Hi Iosif,

> in my makefile I have defined DEBUG & _DEBUG and I don't use for the debug 
> version the linker flag -s (for stripping)

This sounds like your project is not using Qmake - if this is true than I am 
not sure I can help you.

> Does anyone know if there is a setting in the QtCreator IDE or any other way 
> so that I am not transferred into assembly but on the actual .cpp file so I 
> can check the code?

For Qmake based projects debugging on Sailfish devices works out of box 
including navigation to source code. Just switch to debug build configuration 
in Projects mode, rebuild, and you can start debugging. Debugger will transfer 
you to your source code for sure. Does this work for you with basic application 
created with the "Sailfish OS Qt Quick Application" wizard?

BR,
Martin

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

Re: [SailfishDevel] Connection error

[Martin Kampas]

Hi Iosif,

Could you please go throught the thread linked from the question on 
together.jolla.com which Lewis pointed to a provide as much info as possible 
based on that? You could start reading at this email 
https://lists.sailfishos.org/pipermail/devel/2016-July/007256.html.

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Iosif Hamlatzis 
[i.hamlat...@gmail.com]
Sent: Thursday, December 01, 2016 2:05 PM
To: Sailfish OS Developers
Subject: [SailfishDevel] Connection error

After clean install of SDK 1611 (2.0.5) on a Win10 machine I cannot deploy to 
the emulator. I always get the same error message:

Could not connect to the "SailfishOS Emulator" virtual machine. Do you want to 
try again?
Connection error: 1 Connection refused


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

Re: [SailfishDevel] Translation support broken? | Re: SDK version 1701 (2.1.0) is released to Early Access

[Martin Kampas]

Hi micu,

No problem! :) FYI it is fixed in SDK 1701-1 that was released last Thursday.

BR,
Martin

From: Devel [devel-boun...@lists.sailfishos.org] on behalf of micu 
[micuin...@gmx.de]
Sent: Tuesday, March 28, 2017 9:12 AM
To: devel@lists.sailfishos.org; devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] Translation support broken? | Re: SDK version  
1701(2.1.0) is released to Early Access

Hi Martin,

Sorry, I totally forgot to answer to this.
I only wanted to let you know that your solution fixed the issue for me
and say thank you! ;)

Best,
micu

On Donnerstag, 23. Februar 2017 11:42:58 CEST Martin Kampas wrote:
> Hi micu,
>
> As a workaround until a fixed version of the SDK is released you can execute
> this command inside the build engine VM:
>
> sb2-config -l |xargs -I{} sb2 -t {} -R sed -i 's/\\"//g'
> /usr/share/qt5/mkspecs/features/sailfishapp_i18n.prf
>
> Undo the change with:
>
> sb2-config -l |xargs -I{} sb2 -t {} -R -m sdk-install zypper in -fy
> libsailfishapp-devel
>
> (Some info on how to enter the build VM can be found here
> https://sailfishos.org/wiki/Tutorial_-_Building_packages_manually)
>
> BR,
> Martin
>
> 
> From: Martin Kampas
> Sent: Thursday, February 23, 2017 11:00 AM
> To: Sailfish OS Developers
> Subject: RE: [SailfishDevel] Translation support broken? | Re: SDK version
> 1701 (2.1.0) is released to Early Access
>
> Hi micu,
>
> I can confirm it can be reproduced - the build is not terminated though and
> I never scrolled up enough to check the output!
>
> BR,
> Martin
>
> ____
> From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Martin Kampas
> [martin.kam...@jolla.com] Sent: Monday, February 13, 2017 11:52 AM
> To: Sailfish OS Developers
> Subject: Re: [SailfishDevel] Translation support broken? | Re: SDK version
> 1701 (2.1.0) is released to Early Access
>
> Hi micu,
>
> For me it works also with the development branch
> (6d90504b299505465e3a7a5278704ffba7c2ea27). I also tried with an updated
> installation of SDK (1611->1701), instead of a clean installation. Is there
> anything special about your installation?
>
> BR,
> Martin
> ___
> 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


--
OpenPGP / GnuPG:0xE4CB4E80
Fingerprint:1A15 A480 1F8B 07F6 9D12 3426 CEFE 7455 E4CB 4E80

<<>

http://www.micuintus.de
___
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] Odd issues with SDK - shared libraries not recognized as such

[Martin Kampas]

Hi Rinigus,

Fix this by installing boost-regex also outside sb2

[mersdk@SailfishSDK ~]$ sb2 -t SailfishOS-i486 ldd 
/usr/lib/libboost_regex.so.1.51.0
not a dynamic executable
[...]
[mersdk@SailfishSDK ~]$ sudo zypper in boost-regex
[mersdk@SailfishSDK ~]$ sb2 -t SailfishOS-i486 ldd 
/usr/lib/libboost_regex.so.1.51.0
linux-gate.so.1 =>  (0x6f758000)
libsb2.so.1 => /usr/lib/libsb2/libsb2.so.1 (0x6f5fb000)
libicuuc.so.52 => /usr/lib/libicuuc.so.52 (0x6f48b000)
libicui18n.so.52 => /usr/lib/libicui18n.so.52 (0x6f282000)
libicudata.so.52 => /usr/lib/libicudata.so.52 (0x6dc16000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x6db2e000)
libm.so.6 => /lib/libm.so.6 (0x6dae6000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x6dacd000)
libc.so.6 => /lib/libc.so.6 (0x6d907000)
libdl.so.2 => /lib/libdl.so.2 (0x6d902000)
libpthread.so.0 => /lib/libpthread.so.0 (0x6d8e6000)
/lib/ld-linux.so.2 (0x6f759000)
[...]

Applies to other packages as well.

Apart from that are you sure you want to use sb2's sdk-install mode?

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of rinigus 
[rinigus@gmail.com]
Sent: Monday, April 03, 2017 9:52 PM
To: Sailfish OS Developers
Subject: [SailfishDevel] Odd issues with SDK - shared libraries not recognized 
as such

Hi,

I have been struggling with an odd issue which is present in current stable and 
EA SDKs. Namely, several libraries are not recognized as dynamic libraries on 
i486 target. For example:

sb2 -t SailfishOS-i486 -m sdk-install ldd /usr/lib/libboost_regex.so.1.51.0
not a dynamic executable
Messages from sb2:
 (WARNING) ldd{bash}[6959] Executing statically linked native binary 
/srv/mer/targets/SailfishOS-i486/lib/ld-2.19.so
 (WARNING) ldd{bash}[6960] Executing statically linked native binary 
/srv/mer/targets/SailfishOS-i486/lib/ld-2.19.so
# exit 1 (1)

Probably most libraries are fine, like

sb2 -t SailfishOS-i486 -m sdk-install ldd /usr/lib/libboost_filesystem.so.1.51.0
linux-gate.so.1 =>  (0x6f79c000)
libsb2.so.1 => /usr/lib/libsb2/libsb2.so.1 (0x6f721000)
libboost_system.so.1.51.0 => /usr/lib/libboost_system.so.1.51.0 (0x6f719000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x6f631000)
libm.so.6 => /lib/libm.so.6 (0x6f5ea000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x6f5d)
libc.so.6 => /lib/libc.so.6 (0x6f409000)
libdl.so.2 => /lib/libdl.so.2 (0x6f403000)
/lib/ld-linux.so.2 (0x6f79d000)
Messages from sb2:
 (WARNING) ldd{bash}[6829] Executing statically linked native binary 
/srv/mer/targets/SailfishOS-i486/lib/ld-2.19.so
 (WARNING) ldd{bash}[6830] Executing statically linked native binary 
/srv/mer/targets/SailfishOS-i486/lib/ld-2.19.so
 (WARNING) ldd{bash}[6833] Executing statically linked native binary 
/srv/mer/targets/SailfishOS-i486/lib/ld-2.19.so
# exit 0 (0)

This issue does not appear on ARM target:

sb2 -t SailfishOS-armv7hl -m sdk-install ldd /usr/lib/libboost_regex.so.1.51.0
libicuuc.so.52 => /usr/lib/libicuuc.so.52 (0x488cc000)
libicui18n.so.52 => /usr/lib/libicui18n.so.52 (0x489d)
libicudata.so.52 => /usr/lib/libicudata.so.52 (0x48b28000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x4a1a4000)
libm.so.6 => /lib/libm.so.6 (0x4a256000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x4a2cb000)
libc.so.6 => /lib/libc.so.6 (0x4a2e3000)
libpthread.so.0 => /lib/libpthread.so.0 (0x4a3e8000)
libdl.so.2 => /lib/libdl.so.2 (0x4a40b000)
/lib/ld-linux-armhf.so.3 (0x40801000)

The libraries in question that I stumbled upon are libboost_regex and 
libharfbuzz. I tried to recompile harfbuzz to see if something went wrong on 
its generation, but got the same issue - its not recognized as a shared library 
by ldd.

Note that you can compile and link against these libraries. Don't know if the 
compiled code would run on the tablet, but it refuses to run under mb2/sb2. 
Which is a major problem preventing using libraries/code that has configure 
scripts to check for these libraries.

I have found some logs on sfos-porters #irc channel (2013 & 2014) with the 
similar issue, but there was no solution as far as I could tell.

Does anyone know how to fix it? Apart from skipping i486 or hacking configure 
scripts...

Cheers,

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

Re: [SailfishDevel] Odd issues with SDK - shared libraries not recognized as such

[Martin Kampas]

Hi Rinigus,

There is no suitable docs I am aware of, but anyway following the simple rule 
to pass "-m sdk-install" if and only if you are installing (removing, 
updating...) packages in the target should be enough for normal SDK usage.

The need to install packages also outside sb2 should be exceptional. There is 
an ongoing activity to improve SDK in regards to this.

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of rinigus 
[rinigus@gmail.com]
Sent: Wednesday, April 05, 2017 8:51 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Odd issues with SDK - shared libraries not 
recognized as such

Hi Martin,

thank you for the tip, it worked nicely! There were several other libraries 
affected: boost-program-options, libtiff, and libjpeg-turbo to name in addition 
to the ones I mentioned earlier.

As for using sdk-mode - I actually didn't find (relatively fast google search) 
on what does it do. In all examples on how to build packages manually, I could 
see "-m sdk-install" option given. So, if you can give me URL with description 
or tell what does it do and whether I should omit it, please do so.

Ideally, I don't want to mess with sb2, all I wanted to run was

mb2 -t SailfishOS-i486 -s package.spec build

which failed due to the configuration error. Taking into account this bug, 
maybe all packages specified in spec files as build-dep should be installed in 
addition by zypper outside sb2?

Best wishes,

Rinigus

On Wed, Apr 5, 2017 at 8:03 AM, Martin Kampas 
<martin.kam...@jolla.com<redir.aspx?REF=BlRet5twj2Crwc7W7O7I1Z9YFL5MaGTXFsQUmrm967ClrFRjBHzUCAFtYWlsdG86bWFydGluLmthbXBhc0Bqb2xsYS5jb20.>>
 wrote:
Hi Rinigus,

Fix this by installing boost-regex also outside sb2

[mersdk@SailfishSDK ~]$ sb2 -t SailfishOS-i486 ldd 
/usr/lib/libboost_regex.so.1.51.0
not a dynamic executable
[...]
[mersdk@SailfishSDK ~]$ sudo zypper in boost-regex
[mersdk@SailfishSDK ~]$ sb2 -t SailfishOS-i486 ldd 
/usr/lib/libboost_regex.so.1.51.0
linux-gate.so.1 =>  (0x6f758000)
libsb2.so.1 => /usr/lib/libsb2/libsb2.so.1 (0x6f5fb000)
libicuuc.so.52 => /usr/lib/libicuuc.so.52 (0x6f48b000)
libicui18n.so.52 => /usr/lib/libicui18n.so.52 (0x6f282000)
libicudata.so.52 => /usr/lib/libicudata.so.52 (0x6dc16000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x6db2e000)
libm.so.6 => /lib/libm.so.6 (0x6dae6000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x6dacd000)
libc.so.6 => /lib/libc.so.6 (0x6d907000)
libdl.so.2 => /lib/libdl.so.2 (0x6d902000)
libpthread.so.0 => /lib/libpthread.so.0 (0x6d8e6000)
/lib/ld-linux.so.2 (0x6f759000)
[...]

Applies to other packages as well.

Apart from that are you sure you want to use sb2's sdk-install mode?

BR,
Martin


From: Devel 
[devel-boun...@lists.sailfishos.org<redir.aspx?REF=red6WrN6nZnw3ibb7Yu0XS44p74x0879e6kUNQ0ShUalrFRjBHzUCAFtYWlsdG86ZGV2ZWwtYm91bmNlc0BsaXN0cy5zYWlsZmlzaG9zLm9yZw..>]
 on behalf of rinigus 
[rinigus@gmail.com<redir.aspx?REF=O4gyhzgobECtluZ0ewTLfxROAtl72wmsgN2MItxlW9ylrFRjBHzUCAFtYWlsdG86cmluaWd1cy5naXRAZ21haWwuY29t>]
Sent: Monday, April 03, 2017 9:52 PM
To: Sailfish OS Developers
Subject: [SailfishDevel] Odd issues with SDK - shared libraries not recognized 
as such

Hi,

I have been struggling with an odd issue which is present in current stable and 
EA SDKs. Namely, several libraries are not recognized as dynamic libraries on 
i486 target. For example:

sb2 -t SailfishOS-i486 -m sdk-install ldd /usr/lib/libboost_regex.so.1.51.0
not a dynamic executable
Messages from sb2:
 (WARNING) ldd{bash}[6959] Executing statically linked native binary 
/srv/mer/targets/SailfishOS-i486/lib/ld-2.19.so<redir.aspx?REF=5PVEdlZK2kDjBwQ3WEDYMHgqXtf8qmNCOuVHnLp6m8OlrFRjBHzUCAFodHRwOi8vcmVkaXIuYXNweD9SRUY9NEt1MUJNRXdFNVBpQnFtdGl2dVJKRllwVUhFdmRULXJiaWFWdjJ4ZHZaQ3hnbE13NEh2VUNBRm9kSFJ3T2k4dmJHUXRNaTR4T1M1emJ3Li4.>
 (WARNING) ldd{bash}[6960] Executing statically linked native binary 
/srv/mer/targets/SailfishOS-i486/lib/ld-2.19.so<redir.aspx?REF=5PVEdlZK2kDjBwQ3WEDYMHgqXtf8qmNCOuVHnLp6m8OlrFRjBHzUCAFodHRwOi8vcmVkaXIuYXNweD9SRUY9NEt1MUJNRXdFNVBpQnFtdGl2dVJKRllwVUhFdmRULXJiaWFWdjJ4ZHZaQ3hnbE13NEh2VUNBRm9kSFJ3T2k4dmJHUXRNaTR4T1M1emJ3Li4.>
# exit 1 (1)

Probably most libraries are fine, like

sb2 -t SailfishOS-i486 -m sdk-install ldd /usr/lib/libboost_filesystem.so.1.51.0
linux-gate.so.1 =>  (0x6f79c000)
libsb2.so.1 => /usr/lib/libsb2/libsb2.so.1 (0x6f721000)
libboost_system.so.1.51.0 => /usr/lib/libboost_system.so.1.51.0 (0x6f719000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x6f631000)
libm.so.6 => /lib/libm.so.6 (0x6f5ea000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x6f5d)
libc.so.6 => /lib/libc.so.6 (0x6f409000)
libdl.so.2 => /lib/libdl.so.2 (0x6f403000)
/lib/ld-linux.so.2 (0x6f79d000)
Mes

Re: [SailfishDevel] Mouse events with emulator

[Martin Kampas]

Hello Костадин Дамянов,

I am not expert in this area so this is just my opinion:

Touch events are the only "native" events on a (hardware) device with 
touchscreen as the only pointing device. For compatibility with older widgets 
"By default, QGuiApplication translates the first touch point in a QTouchEvent 
into a QMouseEvent."[1]. Nothing more. Sailfish OS Emulator currently does not 
emulate eny device with other than touchscreen pointing device.

So IMO what you want is not likely to be possible.

I suggest you to describe your case in more detail - someone could than advice 
you a better solution.

BR,
Martin

[1] http://doc.qt.io/qt-5/qtouchevent.html#event-delivery-and-propagation


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Костадин Дамянов 
[maxmi...@gmail.com]
Sent: Sunday, March 05, 2017 2:44 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Mouse events with emulator

Hello.

I am developing an application an I have noticed that with the emulator the 
application only receives only QEvent::TouchBegin and QEvent::TouchEnd events.

Is there a way to receive QEvent::MouseButtonPress, QEvent::MouseMove and 
QEvent::MouseButtonRelease events when working with the emulator?
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] SQLite linking

[Martin Kampas]

Hi Rinigus,

Did you consider this recommendation?

"To simplify matters, SQLite is also available as a pre-packaged amalgamation 
source code file: sqlite3.c. The amalgamation is a single file of ANSI-C code 
that implements the entire SQLite library. The amalgamation is much easier to 
deal with. Everything is contained within a single code file, so it is easy to 
drop into the source tree of a larger C or C++ program. [...]  For these 
reasons, the amalgamation source file ("sqlite3.c") is recommended for all 
applications."[1]

What are the reasons that prevent you from using the upstream recommended 
approach? Are they worth your time and effort?

Thinking out loud: If an application (in its packaged form) is to be supported 
on a variety of devices and (future) OS releases all its dependencies must be 
satisfied in these environments. In order to make both the OS/devices vendors' 
and app developers' life easier in this respect a minimal necessary subset of 
all the APIs provided by the OS (at particular time) is defined that is 
guaranteed to be universally available in some time frame. Feel free 
(encouraged!) to use any other dependencies, even those completely missing in 
the OS (yet), bundling these together with your application! Only where this is 
not possible and/or implies an excessive effort and/or adds dozens of megabytes 
etc. it is worth to wait for Harbour rules to change.

BR,
Martin

[1] 
https://www.sqlite.org/howtocompile.html#amalgamation_versus_individual_source_files


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of rinigus 
[rinigus@gmail.com]
Sent: Saturday, March 04, 2017 2:46 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] SQLite linking

Hi,

thank you very much for the response and explanation. Looking forward to see 
the new whitelist / harbour rules. Its fine to take time to do it properly, 
thanks for the feedback.

Best wishes,

Rinigus

On Sat, Mar 4, 2017 at 3:15 PM, Andrew Branson 
>
 wrote:
Hi,

I've had a look internally about this, and it's caught up in a larger overhaul 
of the whitelist and harbour rules aiming to make development more attractive 
to developers while remaining maintainable. This is part of the reason you 
haven't had any feedback yet, but also everyone's got caught up in the huge 
amount of work lately that you've now seen some news about.

It's not great when external PRs and bugs on the merproject bugzilla appear to 
look dead because they're blocked internally but not visibly, especially when 
someone's taken the time and trouble to investigate and submit something. Sorry 
about that. Even if the internal progress on such things can't be made public, 
an acknowledgement would be nice. The apparent silence doesn't mean your 
efforts aren't appreciated nor influential.

Hope that helps a bit,

Andrew

On Saturday, 4 March 2017, rinigus wrote:
> Re OpenRepos: Sure, and I do. And through bundling I am publishing @Harbour. 
> But the main issue is the lack of response for a rather simple request. Even 
> a negative response is a response.
>
>
> Sorry for complains. Enjoy the weekend and let's see if Jolla devs would 
> respond during the work hours :)
>
>
> rinigus
>
>
> On Sat, Mar 4, 2017 at 2:22 PM, Marcin Mielniczuk 
> >
>  wrote:
>
> You can always use OpenRepos...
>
>
>
> On March 4, 2017 8:50:37 AM GMT+01:00, rinigus 
> >
>  wrote:
> Hi,
>
>
> one month + 10 days later - no response for PR nor SQLite linking from 
> Harbour / Jolla devs. Already had to ship few versions with SQLite bundled 
> with application as well. I'd say its rather poor response times already now 
> (with the response time not reached yet).
>
>
> Rinigus
>
>
>
>
> On Wed, Jan 18, 2017 at 4:30 PM, rinigus 
> >
>  wrote:
>
> Slava,
>
>
> thank you for this constructive suggestion. I submitted PR 
> https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/pull/86
>  to add sqlite into the list of allowed libraries. Hopefully, it will be 
> accepted.
>
>
> Best wishes,
>
>
> Rinigus
>
>
> On Wed, Jan 18, 2017 at 3:29 PM, Slava Monich 
> >
>  wrote:
>
> I believe rpm automatically detects the 

Re: [SailfishDevel] SDK 1701-1 translation files problem on compile

[Martin Kampas]

Hi Rudi Timmermans,

What you observe seems to be simply result of using whitespace in your project 
path. It is possible you were lucky enough that it worked in your particular 
case before. (Compare e.g. with 
https://bugreports.qt.io/browse/QTCREATORBUG-11190).

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Rudi Timmermans 
[rudi.tim...@gmx.us]
Sent: Saturday, April 15, 2017 11:12 AM
To: Sailfish Developers Mailinlist
Subject: [SailfishDevel] SDK 1701-1 translation files problem on compile


Hi,

I have a problem with compile the translation files on the lasted release of 
the SDK 1701-1

lupdate error: File '/home/mersdk/share/Sailfish' does not exist. lrelease 
error: Cannot open /home/mersdk/share/Sailfish: No such file or directory 
install -m 644 -p /home/mersdk/share/Sailfish\ 
Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-de.qm
 /home/deploy/installroot/usr/share/harbour-sailbook/translations/ install: 
cannot stat /home/mersdk/share/Sailfish 
Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-de.qm':
 No such file or directory make: [install_qm] Error 1 (ignored) install -m 644 
-p /home/mersdk/share/Sailfish\ 
Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-fi.qm
 /home/deploy/installroot/usr/share/harbour-sailbook/translations/ install -m 
644 -p /home/mersdk/share/Sailfish\ 
Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-nl.qm
 /home/deploy/installroot/usr/share/harbour-sailbook/translations/ install -m 
644 -p /home/mersdk/share/Sailfish\ 
Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-it.qm
 /home/deploy/installroot/usr/share/harbour-sailbook/translations/ install: 
cannot stat/home/mersdk/share/Sailfish 
Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-fi.qm':
 No such file or directory make: [install_qm] Error 1 (ignored) install: cannot 
stat /home/mersdk/share/Sailfish 
Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-nl.qm':
 No such file or directory make: [install_qm] Error 1 (ignored) install -m 644 
-p /home/mersdk/share/Sailfish\ 
Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-fr.qm
 /home/deploy/installroot/usr/share/harbour-sailbook/translations/ cp -f -R 
/home/mersdk/share/Sailfish\ Development/harbour-sailbook/qml 
/home/deploy/installroot/usr/share/harbour-sailbook/ install: cannot 
stat/home/mersdk/share/Sailfish 
Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-it.qm':
 No such file or directory make: [install_qm] Error 1 (ignored) install: cannot 
stat `/home/mersdk/share/Sailfish 
Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-fr.qm':
 No such file or directory make: [install_qm] Error 1 (ignored)

System: Linux Mint, so basically Ubuntu.

Steps taken (done a few times to be sure):

SDK installation:

uninstalled previous installation via SDK Maintenance Tool
removed ~/.config/SailfishOS-SDK
installed with default settings

But i can not solve the problem any idea's ?

--

Vriendelijke groeten - Best regards,

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

Re: [SailfishDevel] SDK 1701-1 translation files problem on compile

[Martin Kampas]

Hi Rudi Timmermans,

Renaming your directory "Sailfish Development" so that it does not contain 
whitespace characters (e.g. to "Sailfish_Development" or "SailfishDevelopment") 
should fix it.

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Rudi Timmermans 
[rudi.tim...@gmx.us]
Sent: Tuesday, April 18, 2017 9:57 AM
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] SDK 1701-1 translation files problem on compile

Hi Martin,

Thanks for the info, but how can i fix this? Info: i'm running on Linux..

Thanks

Op Dinsdag 18 april 2017 schreef Martin Kampas:
> Hi Rudi Timmermans,
>
> What you observe seems to be simply result of using whitespace in your 
> project path. It is possible you were lucky enough that it worked in your 
> particular case before. (Compare e.g. with 
> https://bugreports.qt.io/browse/QTCREATORBUG-11190).
>
> BR,
> Martin
>
> 
> From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Rudi Timmermans 
> [rudi.tim...@gmx.us]
> Sent: Saturday, April 15, 2017 11:12 AM
> To: Sailfish Developers Mailinlist
> Subject: [SailfishDevel] SDK 1701-1 translation files problem on compile
>
>
> Hi,
>
> I have a problem with compile the translation files on the lasted release of 
> the SDK 1701-1
>
> lupdate error: File '/home/mersdk/share/Sailfish' does not exist. lrelease 
> error: Cannot open /home/mersdk/share/Sailfish: No such file or directory 
> install -m 644 -p /home/mersdk/share/Sailfish\ 
> Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-de.qm
>  /home/deploy/installroot/usr/share/harbour-sailbook/translations/ install: 
> cannot stat /home/mersdk/share/Sailfish 
> Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-de.qm':
>  No such file or directory make: [install_qm] Error 1 (ignored) install -m 
> 644 -p /home/mersdk/share/Sailfish\ 
> Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-fi.qm
>  /home/deploy/installroot/usr/share/harbour-sailbook/translations/ install -m 
> 644 -p /home/mersdk/share/Sailfish\ 
> Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-nl.qm
>  /home/deploy/installroot/usr/share/harbour-sailbook/translations/ install -m 
> 644 -p /home/mersdk/share/Sailfish\ 
> Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-it.qm
>  /home/deploy/installroot/usr/share/harbour-sailbook/translations/ install: 
> cannot stat/home/mersdk/share/Sailfish 
> Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-fi.qm':
>  No such file or directory make: [install_qm] Error 1 (ignored) install: 
> cannot stat /home/mersdk/share/Sailfish 
> Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-nl.qm':
>  No such file or directory make: [install_qm] Error 1 (ignored) install -m 
> 644 -p /home/mersdk/share/Sailfish\ 
> Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-fr.qm
>  /home/deploy/installroot/usr/share/harbour-sailbook/translations/ cp -f -R 
> /home/mersdk/share/Sailfish\ Development/harbour-sailbook/qml 
> /home/deploy/installroot/usr/share/harbour-sailbook/ install: cannot 
> stat/home/mersdk/share/Sailfish 
> Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-it.qm':
>  No such file or directory make: [install_qm] Error 1 (ignored) install: 
> cannot stat `/home/mersdk/share/Sailfish 
> Development/build-harbour-sailbook-MerSDK_SailfishOS-armv7hl-Release/translations/harbour-sailbook-fr.qm':
>  No such file or directory make: [install_qm] Error 1 (ignored)
>
> System: Linux Mint, so basically Ubuntu.
>
> Steps taken (done a few times to be sure):
>
> SDK installation:
>
> uninstalled previous installation via SDK Maintenance Tool
> removed ~/.config/SailfishOS-SDK
> installed with default settings
>
> But i can not solve the problem any idea's ?
>
> --
>
> Vriendelijke groeten - Best regards,
>
> Rudi Timmermans.
>

--

---
Best regards,
Rudi Timmermans.
___
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] cannot install package on engine target any more

[Martin Kampas]

Hi Jerome,

Thank you for reporting this.

Before this is fixed, please try to log in into the engine and install/remove 
packages manually from command line, using

   sdk-manage --target --list
   sdk-manage --devel --list  []
(installed packages have ",i" at the end of line)
   sdk-manage --devel --install  
   sdk-manage --devel --remove  

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of jerome levreau 
[levreau.jer...@vostoksystem.eu]
Sent: Thursday, September 07, 2017 11:35 AM
To: Sailfish OS Developers
Subject: [SailfishDevel] cannot install package on engine target any more

hi, I' running qtcreator 4.0.1, sdk 1707 (2.1.1).
I can build apps, log in into the engine, but I cannot install new package on 
engine target any more, for example nemonotification :

(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: warning: 
/var/cache/zypp/packages/jolla/mw/armv7hl/nemo-qml-plugin-notifications-qt5-1.1.0-1.17.2.armv7hl.rpm:
 Header V3 DSA/SHA1 Signature, key ID 3647af9c: NOKEY
error: Unable to open current directory: No such file or directory

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

Synchronising target to host
Sync completed


I tried to create a new ssh key for mersdk (after cleaning up 
private_keys/engine), removed my .ssh dir, even tried to install new target 
(earlyaccess)

Not much help on the web, but look like on my target there's some certificate 
missing

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

Re: [SailfishDevel] Installing Nemo Notification C++ in EA SDK

[Martin Kampas]

You are welcome.

BTW there should be no need to install required packages manually. You should 
list them in your .spec as BuildRequires and they will be installed 
automatically when you build your package. Or did I miss something?

BR,
Martin


From: Dylan Van Assche [dylan.van.ass...@protonmail.com]
Sent: Wednesday, September 13, 2017 8:58 AM
To: Martin Kampas
Subject: RE: [SailfishDevel] Installing Nemo Notification C++ in EA SDK

That worked! Thanks!



 Original Message 
Subject: RE: [SailfishDevel] Installing Nemo Notification C++ in EA SDK
Local Time: 13 September 2017 8:52 AM
UTC Time: 13 September 2017 06:52
From: martin.kam...@jolla.com
To: Dylan Van Assche <dylan.van.ass...@protonmail.com>, Sailfish OS Developers 
<devel@lists.sailfishos.org>


Hi Dylan,

You are supposed to log in as the 'mersdk' user instead of 'nemo'.

BR,
Martin




From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Dylan Van Assche 
via Devel [devel@lists.sailfishos.org]
Sent: Wednesday, September 13, 2017 8:44 AM
To: Sailfish OS Developers mailing list
Subject: Re: [SailfishDevel] Installing Nemo Notification C++ in EA SDK

Hi Martin,

I already tried that, I get this then:

[nemo@SailfishSDK ~]$ sdk-manage --target --list
/home/nemo/.scratchbox2 missing, create some targets with sb2-init!
[nemo@SailfishSDK ~]$ sdk-manage --devel --install SailfishOS-armv7hl 
nemo-qml-plugin-notifications-qt5
Target SailfishOS-armv7hl is not a valid Scratchbox2 target

Building apps isn't an issue so I don't get why the SDK can't find the target.

Kind regards,
Dylan Van Assche



 Original Message 
Subject: RE: [SailfishDevel] Installing Nemo Notification C++ in EA SDK
Local Time: 13 September 2017 8:28 AM
UTC Time: 13 September 2017 06:28
From: martin.kam...@jolla.com
To: Dylan Van Assche <dylan.van.ass...@protonmail.com>, Sailfish OS Developers 
<devel@lists.sailfishos.org>


Hi Dylan,

Please find the answer in this thread 
https://lists.sailfishos.org/pipermail/devel/2017-September/007991.html

BR,
Martin




From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Dylan Van Assche 
via Devel [devel@lists.sailfishos.org]
Sent: Wednesday, September 13, 2017 8:22 AM
To: Sailfish OS Developers mailing list
Subject: [SailfishDevel] Installing Nemo Notification C++ in EA SDK

Hi,

For some reason I can't install the Nemo Notification plugin in the EA SDK. I 
would like to use it in my C++ code.
This is what I get when installing a package:

finished: installing packages - exited with status 0

(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: warning: 
/var/cache/zypp/packages/jolla/mw/armv7hl/nemo-qml-plugin-notifications-qt5-1.1.0-1.17.2.armv7hl.rpm:
 Header V3 DSA/SHA1 Signature, key ID 3647af9c: NOKEY
error: Unable to open current directory: No such file or directory


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

Synchronising target to host
Sync completed



I don't know why it's aborted or can't find it's packages... It worked before.
Running on OpenSUSE Tumbleweed X64

Kind regards,
Dylan Van Assche

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

Re: [SailfishDevel] Installing Nemo Notification C++ in EA SDK

[Martin Kampas]

Hi Dylan,

You are supposed to log in as the 'mersdk' user instead of 'nemo'.

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Dylan Van Assche 
via Devel [devel@lists.sailfishos.org]
Sent: Wednesday, September 13, 2017 8:44 AM
To: Sailfish OS Developers mailing list
Subject: Re: [SailfishDevel] Installing Nemo Notification C++ in EA SDK

Hi Martin,

I already tried that, I get this then:

[nemo@SailfishSDK ~]$ sdk-manage --target --list
/home/nemo/.scratchbox2 missing, create some targets with sb2-init!
[nemo@SailfishSDK ~]$ sdk-manage --devel --install SailfishOS-armv7hl 
nemo-qml-plugin-notifications-qt5
Target SailfishOS-armv7hl is not a valid Scratchbox2 target

Building apps isn't an issue so I don't get why the SDK can't find the target.

Kind regards,
Dylan Van Assche



 Original Message 
Subject: RE: [SailfishDevel] Installing Nemo Notification C++ in EA SDK
Local Time: 13 September 2017 8:28 AM
UTC Time: 13 September 2017 06:28
From: martin.kam...@jolla.com
To: Dylan Van Assche , Sailfish OS Developers 



Hi Dylan,

Please find the answer in this thread 
https://lists.sailfishos.org/pipermail/devel/2017-September/007991.html

BR,
Martin




From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Dylan Van Assche 
via Devel [devel@lists.sailfishos.org]
Sent: Wednesday, September 13, 2017 8:22 AM
To: Sailfish OS Developers mailing list
Subject: [SailfishDevel] Installing Nemo Notification C++ in EA SDK

Hi,

For some reason I can't install the Nemo Notification plugin in the EA SDK. I 
would like to use it in my C++ code.
This is what I get when installing a package:

finished: installing packages - exited with status 0

(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: warning: 
/var/cache/zypp/packages/jolla/mw/armv7hl/nemo-qml-plugin-notifications-qt5-1.1.0-1.17.2.armv7hl.rpm:
 Header V3 DSA/SHA1 Signature, key ID 3647af9c: NOKEY
error: Unable to open current directory: No such file or directory


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

Synchronising target to host
Sync completed



I don't know why it's aborted or can't find it's packages... It worked before.
Running on OpenSUSE Tumbleweed X64

Kind regards,
Dylan Van Assche

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

Re: [SailfishDevel] Installing Nemo Notification C++ in EA SDK

[Martin Kampas]

Hi Dylan,

Please find the answer in this thread 
https://lists.sailfishos.org/pipermail/devel/2017-September/007991.html

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Dylan Van Assche 
via Devel [devel@lists.sailfishos.org]
Sent: Wednesday, September 13, 2017 8:22 AM
To: Sailfish OS Developers mailing list
Subject: [SailfishDevel] Installing Nemo Notification C++ in EA SDK

Hi,

For some reason I can't install the Nemo Notification plugin in the EA SDK. I 
would like to use it in my C++ code.
This is what I get when installing a package:

finished: installing packages - exited with status 0

(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: warning: 
/var/cache/zypp/packages/jolla/mw/armv7hl/nemo-qml-plugin-notifications-qt5-1.1.0-1.17.2.armv7hl.rpm:
 Header V3 DSA/SHA1 Signature, key ID 3647af9c: NOKEY
error: Unable to open current directory: No such file or directory


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

Synchronising target to host
Sync completed



I don't know why it's aborted or can't find it's packages... It worked before.
Running on OpenSUSE Tumbleweed X64

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

Re: [SailfishDevel] QT String issue

[Martin Kampas]

Hi Dylan,

The backslashes you see in the output are only added when you print the string, 
not actual characters of the string:

"\"Intex Aqua Fish\""

So what you need is to replace just the doublequotes - try data.replace("\"", 
"") or better data.remove('"').

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Dylan Van Assche 
via Devel [devel@lists.sailfishos.org]
Sent: Tuesday, September 12, 2017 2:23 PM
To: Sailfish OS Developers mailing list
Subject: Re: [SailfishDevel] QT String issue

Hi Dmitriy,

For some reason, it doesn't work...

QString data = line.split('=', QString::SkipEmptyParts).at(1);

data.replace("\\\"", "");

dataList.append(qMakePair(querry, data));

This is my code now, but the result is still the same for some reason.
I think I do something still wrong :(

Cheers,
Dylan

 Original Message 
Subject: Re: [SailfishDevel] QT String issue
Local Time: 12 September 2017 2:13 PM
UTC Time: 12 September 2017 12:13
From: dylan.van.ass...@protonmail.com
To: Sailfish OS Developers mailing list 

Hi Dmitriy,

Thanks for the information! I just started to learn QT C++ :)

Cheers,
Dylan



 Original Message 
Subject: Re: [SailfishDevel] QT String issue
Local Time: 12 September 2017 12:41 PM
UTC Time: 12 September 2017 10:41
From: dpur...@gmail.com
To: Dylan Van Assche , Sailfish OS Developers 


Hi Dylan,
trimmed() removes whitespaces only. You need to replace \" with an empty string 
and "escape" both \ and ". You need escaping because this is how string 
literals in C/C++ work. Try calling str.replace("\\\"", ""), where str an 
object of QString.

Also note that trimmed() is a const method and does not change the object for 
which it was called. I.e.

QString str1 = "  a  ";
str1.trimmed();
// str1 is unchanged but returns a QString object which is "a"

Cheers
Dmitriy


On Tue, Sep 12, 2017 at 12:25 PM, Dylan Van Assche via Devel 
>
 wrote:
Hi,

I'm reading the sfos-release and the hw-release file in /etc from C++ but for 
some lines I get this in my strings as output:




"\"Intex Aqua Fish\""

I tried trimmed() and remove() but I can't figure out how to clean it 
correctly. The \" characters are annoying.

Kind regards,
Dylan Van Assche


___
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] Qt creator fails to connect to virtual machines

[Martin Kampas]

Hello Peter,

Unfortunately this is because your OS is too "stable" :) VirtualBox 4.x support 
has been broken since Sailfish OS SDK 1707.

As a workaround until this is fixed you can create the following wrapper for 
VBoxManage:

cat > ~/SailfishOS/bin/VBoxManage <&2
exit 1
fi

if [[ $1 == "showvminfo" ]]; then
"$real" "$@" |sed '/^Session type:/ { p; s/type:/name:/ }'
else
"$real" "$@"
fi
END
chmod +x ~/SailfishOS/bin/VBoxManage

And then use this to launch the IDE

PATH="$HOME/SailfishOS/bin:$PATH" ~/SailfishOS/bin/qtcreator

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Peter Albrecht 
[pa-...@gmx.de]
Sent: Wednesday, November 01, 2017 6:36 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Qt creator fails to connect to virtual machines

Hello list,

I wanted to work on SailfishOS applications, so I installed the "SailfishOS
Application SDK" on my linux desktop.
Everything went fine, but when I wanted to start "Sailfish OS Build Engine" or
"Sailfish OS Emulator" from within Qt Creator, the "General Messages"-Tab of Qt
Creator tells me:

* Error connecting to "Sailfish OS Build Engine" virtual machine: Failed to
  start virtual machine "Sailfish OS Build Engine"
* Error connecting to "Sailfish OS Emulator" virtual machine: Failed to start
  virtual machine "Sailfish OS Emulator"

In file "~/.xsession-errors" I can read:

* MerConnection: "Failed to start virtual machine \"Sailfish OS Build Engine\""
* MerConnection: "Failed to start virtual machine \"Sailfish OS Emulator\""

But nothing more about the Application SDK.


The virtual machines seem to start up:
VirtualBox is telling me that they are running.
The emulator is showing me a SailfishOS GUI, which I can use by swiping like my
Jolla device. And to the Build Engine I can connect via ssh using:
> ssh -i /opt/sailfishos-sdk/vmshare/ssh/private_keys/engine/root -p  
> root@localhost


Do you have any ideas, what might be the problem? Or which log-files to check?


Versions in use:

 * SDK: SailfishOSSDK-Beta-1709-Qt5-linux-64-offline.run
 * Debian Linux 8 Jessie
 * VirtualBox 4.3.36

Regards,
Peter
___
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] Qt creator fails to connect to virtual machines

[Martin Kampas]

Hello Peter,

Good to hear it helped you! I added it to Known Issues 
https://sailfishos.org/wiki/Application_SDK_Known_Issues#General

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Peter Albrecht 
[pa-...@gmx.de]
Sent: Thursday, November 02, 2017 10:17 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Qt creator fails to connect to virtual machines

Hello Martin,

thank you for your answer! Nice to hear, it does not fail, because I messed
something up... ;)

Your wrapper script did fix my problem. Thanks a lot!


Should the documentation be updated? Both sites:
> https://sailfishos.org/wiki/Application_SDK
and
> https://sailfishos.org/wiki/Application_SDK_Installation
list under "pre-requisites" the text "Oracle’s VirtualBox version 4.1.18 or
higher". So I thought, I am fine with debian's VirtualBox of version 4.3.36.

Best regards,
Peter


On 02.11.2017 08:41, Martin Kampas wrote:
> Hello Peter,
>
> Unfortunately this is because your OS is too "stable" :) VirtualBox 4.x 
> support has been broken since Sailfish OS SDK 1707.
>
> As a workaround until this is fixed you can create the following wrapper for 
> VBoxManage:
>
> cat > ~/SailfishOS/bin/VBoxManage < #!/bin/bash
>
> real=$(which -a "$(basename "$0")" |sed -n 2p)
> if [[ ! $real ]]; then
> echo "Broken PATH?" >&2
> exit 1
> fi
>
> if [[ $1 == "showvminfo" ]]; then
> "$real" "$@" |sed '/^Session type:/ { p; s/type:/name:/ }'
> else
> "$real" "$@"
> fi
> END
> chmod +x ~/SailfishOS/bin/VBoxManage
>
> And then use this to launch the IDE
>
> PATH="$HOME/SailfishOS/bin:$PATH" ~/SailfishOS/bin/qtcreator
>
> BR,
> Martin
>
> 
> From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Peter Albrecht 
> [pa-...@gmx.de]
> Sent: Wednesday, November 01, 2017 6:36 PM
> To: devel@lists.sailfishos.org
> Subject: [SailfishDevel] Qt creator fails to connect to virtual machines
>
> Hello list,
>
> I wanted to work on SailfishOS applications, so I installed the "SailfishOS
> Application SDK" on my linux desktop.
> Everything went fine, but when I wanted to start "Sailfish OS Build Engine" or
> "Sailfish OS Emulator" from within Qt Creator, the "General Messages"-Tab of 
> Qt
> Creator tells me:
>
> * Error connecting to "Sailfish OS Build Engine" virtual machine: Failed to
>   start virtual machine "Sailfish OS Build Engine"
> * Error connecting to "Sailfish OS Emulator" virtual machine: Failed to start
>   virtual machine "Sailfish OS Emulator"
>
> In file "~/.xsession-errors" I can read:
>
> * MerConnection: "Failed to start virtual machine \"Sailfish OS Build 
> Engine\""
> * MerConnection: "Failed to start virtual machine \"Sailfish OS Emulator\""
>
> But nothing more about the Application SDK.
>
>
> The virtual machines seem to start up:
> VirtualBox is telling me that they are running.
> The emulator is showing me a SailfishOS GUI, which I can use by swiping like 
> my
> Jolla device. And to the Build Engine I can connect via ssh using:
>> ssh -i /opt/sailfishos-sdk/vmshare/ssh/private_keys/engine/root -p  
>> root@localhost
>
>
> Do you have any ideas, what might be the problem? Or which log-files to check?
>
>
> Versions in use:
>
>  * SDK: SailfishOSSDK-Beta-1709-Qt5-linux-64-offline.run
>  * Debian Linux 8 Jessie
>  * VirtualBox 4.3.36
>
> Regards,
> Peter
> ___
> 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] SDK auto setter/getter

[Martin Kampas]

Hi Dylan,

Tried with Sailfish OS SDK 1709 on Linux. It works for me. Whenever I had 
cursor on the identifier (not after semicolon or before preceding space) the 
menu popped up on ALT+ENTER. It didn't pop up when the getter and setter 
already existed.

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Dylan Van Assche 
via Devel [devel@lists.sailfishos.org]
Sent: Friday, October 27, 2017 6:03 PM
To: Sailfish OS Developers mailing list
Subject: [SailfishDevel] SDK auto setter/getter

Hi,

I'm rewriting my Sailfish OS apps with a C++ backend by following the 
encapsulation rules.
This implies that I need a get/set for each C++ class so I searched online if 
QtCreator cannot generate these automatically and it should do it: 
https://stackoverflow.com/questions/21142940/how-to-make-getter-and-setter-methods-in-qt-creator-automatically
However, the Sailfish OS QtCreator doesn't seem to do this when I press ALT + 
ENTER on a member variable, the same for the Refactor option.

Is it disabled or am I doing something wrong?
Writing each setter/getter myself takes a lot of time...

Kind regards,
Dylan Van Assche




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

Re: [SailfishDevel] ConfigurationValue default path

[Martin Kampas]

Hi João,

The storage backend is dconf https://wiki.gnome.org/Projects/dconf

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of joao morgado via 
Devel [devel@lists.sailfishos.org]
Sent: Friday, May 18, 2018 6:54 AM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] ConfigurationValue default path

Hi

Where does ConfigurationValue saves the data ? I didnt find nothing in 
"/home/nemo/.config" related to my app.
In desktop and android  I sucessfully used the equivalent qml Settings to save 
my stuff, but in sailfish nothing is being saved using ConfigurationValue.

Cheers
João



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

Re: [SailfishDevel] ConfigurationValue default path

[Martin Kampas]

Hi João,

I think you need ConfigurationGroup instead of ConfigurationValue if you want 
to use it this way, and I am unsure that it is supposed to work with alias 
properties.

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of joao morgado via 
Devel [devel@lists.sailfishos.org]
Sent: Monday, May 21, 2018 6:45 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] ConfigurationValue default path

Hi Martin

Thanks for your replay.
I did a very small example, trying to save a rectangle color, but if fails. 
When starting, it's always red. Am I missing something ?



Rectangle {

id: mycolor

color: "red"

//color: mysettings.saveColor

anchors.fill: parent


MouseArea {

anchors.fill: parent

onClicked: {

mycolor.color = Qt.colorEqual(mycolor.color, "red") ? "blue" : 
"red"

hello === "I'm red" ? hello = "I'm blue" : hello = "I'm red"

}


}

Text {

text: hello

}

}


property string hello: "I'm red"



ConfigurationValue {

id: mysettings

property alias saveColor: mycolor.color

property alias mystring: page.hello

//property color saveColor: "red"

}


/*Component.onCompleted: console.log("initial color: "+mysettings.saveColor)

Component.onDestruction: {

mysettings.saveColor = mycolor.color

console.log("destruction color: "+mysettings.saveColor)

}*/


Cheers
João


Em sexta-feira, 18 de maio de 2018 06:04:27 GMT+1, Martin Kampas 
<martin.kam...@jolla.com> escreveu:


Hi João,

The storage backend is dconf https://wiki.gnome.org/Projects/dconf

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of joao morgado via 
Devel [devel@lists.sailfishos.org]
Sent: Friday, May 18, 2018 6:54 AM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] ConfigurationValue default path

Hi

Where does ConfigurationValue saves the data ? I didnt find nothing in 
"/home/nemo/.config" related to my app.
In desktop and android  I sucessfully used the equivalent qml Settings to save 
my stuff, but in sailfish nothing is being saved using ConfigurationValue.

Cheers
João



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

Re: [SailfishDevel] SDK version 1804 (2.2.0) is released to Early Access

[Martin Kampas]

Fixed, thank you!
-Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Zhang Bird 
[0312birdzh...@gmail.com]
Sent: Saturday, June 09, 2018 4:13 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] SDK version 1804 (2.2.0) is released to Early 
Access

The download link is wrong.

Sailfish OS SDK 1804
Linux 
32<http://releases.sailfishos.org/sdk/installers/1804/SailfishOSSDK-Beta-1801-Qt5-linux-32-offline.run>
   Linux 
64<http://releases.sailfishos.org/sdk/installers/1801/SailfishOSSDK-Beta-1804-Qt5-linux-64-offline.run>
OS 
X<http://releases.sailfishos.org/sdk/installers/1801/SailfishOSSDK-Beta-1804-Qt5-mac-offline.dmg>

Windows<http://releases.sailfishos.org/sdk/installers/1801/SailfishOSSDK-Beta-1804-Qt5-windows-offline.exe>
It shuould be 
http://releases.sailfishos.org/sdk/installers/1804/SailfishOSSDK-Beta-1804-Qt5-*-offline.*


Martin Kampas mailto:martin.kam...@jolla.com>> 
于2018年6月8日周五 下午11:01写道：
Hello,

Today (Jun 8th) at 15:00 UTC we made the Sailfish OS SDK 1804 available to all 
users. Please, check out the in depth release notes from below or at 
https://sailfishos.org/wiki/Application_SDK#Release_Notes.

The installers for this release of the SDK are now available at 
http://sailfishos.org/wiki/Application_SDK#Latest_SDK_Release. If you have an 
older beta release of the SDK, you should see an update notification in the 
Sailfish OS IDE.

If you have any questions, feel free to either send an email to this mailing 
list: devel at lists.sailfishos.org<http://lists.sailfishos.org>, write it up 
in http://together.jolla.com and tag your issue with 'sdk' or send an e-mail to 
developer-care at jolla.com<http://jolla.com>.

Happy hacking,
Jolla SDK Team

On 6 Jun 2018, at 17:24:08 CEST Martin Kampas wrote:
> Hello,
>
> Today (Jun 6th) at 15:00 UTC we have published new installers and
> repositories of the Sailfish OS SDK. This SDK release is called 1804 and it
> matches Jolla Release 2.2.0.
>
> Please, read the following notes about the Early Access SDK:
> - By using the Early Access SDK developers can test their Sailfish OS apps a
> week before the Sailfish OS release is made public - During the early
> access time the Early Access SDK should not be used for submitting apps to
> the Jolla Harbour - The installers for this release of the SDK are
> available at
> http://sailfishos.org/wiki/Application_SDK_Early_Access#Latest_Early_Access
> _SDK_Release - Instructions for adding the early access repository into the
> SDK can be found from
> http://sailfishos.org/wiki/Application_SDK_Early_Access#Receiving_Early_Acc
> ess_SDK_Updates_Automatically
>
> If you add the early access repository into your SDK and have an older beta
> release of the SDK, you should see an update notification in the Sailfish
> OS IDE. Otherwise, you will see an update notification in the Sailfish OS
> IDE, when the Jolla Release 2.2.0 is publicly available to all users.
>
> SDK content matches Jolla Release 2.2.0.29 (Mouhijoki). 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
> reinstalled 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. - Package repository contents
> have been updated and consequently using a previous SDK version with these
> package repositories is not supported. - For more information, please see
> the Application SDK known issues list at
> https://sailfishos.org/wiki/Application_SDK_Known_Issues.
>
>
> Release Content
>
> SDK 1804
>
> SDK Installer/Maintenance Tool
> - Removed the need to run with LIBOVERLAY_SCROLLBAR=0 on some Ubuntu systems
> - On Linux and macOS the SDK Maintenance Tool now uses HTTPS to access the
> online repository by default. On Windows plain HTTP is still the only
> option.
>
> SDK IDE (Qt Creator, Qt QmlLive)
> - Refreshed API documentation available in the Help mode (Ctrl+7) in Qt
> Creator to Jolla release 2.2.0.29 level - QmlLive Bench now limits the
> number of file-change watches. Higher limit can be set with a command line
> option. - QmlLive Bench now connects automatically also when application
&

[SailfishDevel] SDK version 1804 (2.2.0) is released to Early Access

[Martin Kampas]

Hello,

Today (Jun 6th) at 15:00 UTC we have published new installers and repositories 
of the Sailfish OS SDK. This SDK release is called 1804 and it matches Jolla 
Release 2.2.0.

Please, read the following notes about the Early Access SDK:
- By using the Early Access SDK developers can test their Sailfish OS apps a 
week before the Sailfish OS release is made public
- During the early access time the Early Access SDK should not be used for 
submitting apps to the Jolla Harbour
- The installers for this release of the SDK are available at 
http://sailfishos.org/wiki/Application_SDK_Early_Access#Latest_Early_Access_SDK_Release
- Instructions for adding the early access repository into the SDK can be found 
from 
http://sailfishos.org/wiki/Application_SDK_Early_Access#Receiving_Early_Access_SDK_Updates_Automatically

If you add the early access repository into your SDK and have an older beta 
release of the SDK, you should see an update notification in the Sailfish OS 
IDE. Otherwise, you will see an update notification in the Sailfish OS IDE, 
when the Jolla Release 2.2.0 is publicly available to all users.

SDK content matches Jolla Release 2.2.0.29 (Mouhijoki). 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 
reinstalled 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.
- Package repository contents have been updated and consequently using a 
previous SDK version with these package repositories is not supported.
- For more information, please see the Application SDK known issues list at 
https://sailfishos.org/wiki/Application_SDK_Known_Issues.


Release Content

SDK 1804

SDK Installer/Maintenance Tool
- Removed the need to run with LIBOVERLAY_SCROLLBAR=0 on some Ubuntu systems
- On Linux and macOS the SDK Maintenance Tool now uses HTTPS to access the 
online repository by default. On Windows plain HTTP is still the only option.

SDK IDE (Qt Creator, Qt QmlLive)
- Refreshed API documentation available in the Help mode (Ctrl+7) in Qt Creator 
to Jolla release 2.2.0.29 level
- QmlLive Bench now limits the number of file-change watches. Higher limit can 
be set with a command line option.
- QmlLive Bench now connects automatically also when application startup is 
interrupted by debugger
- Added controls that allow to change SSH and HTTP ports used by SDK Build 
Engine (Options > Sailfish OS) and SSH port used by Emulator (Options > Devices)

SDK Build Engine
- Build targets refreshed to Jolla release 2.2.0.29 level
- RPM binaries are not tainted with unsatisfied dependency on 
rpmlib(ShortCircuited) anymore
- Fixed deployment to a device on local network when used with restricted 
access to the Internet
- Control Centre now uses HTTPS by default for downloading SDK Targets and 
Toolings on all platforms

Emulator
- Emulator packages refreshed to Jolla release 2.2.0.29 level
- Fixed lengthy shutdowns

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

Happy hacking,
Jolla SDK Team


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

Re: [SailfishDevel] Compile without Scratchbox2 environment

[Martin Kampas]

Hi Yuvraaj,

I think you mistakenly consider "Sailfish OS Platform SDK" and Scratchbox2 for 
the same thing. Sailfish OS Platform SDK is a root filesystem image with 
Scratchbox2 and other tools preinstalled. In theory you could install sb2 
directly on your workstation but the SDK exists for your convenience. chroot 
and bind mount is used to enter the SDK but sb2 itself is not a chroot nor bind 
mount based - sb2 runs with normal user privileges.

Normally you enter the SDK using the /mer-sdk-chroot script which basically 
does bind mount and chroot. I am quite sure it is possible to repackage the SDK 
as a Docker image without the need for superuser privileges. Look into 
mer-sdk-chroot to learn what is needed to enter the SDK.

You can read more about the various components of Sailfish OS SDK e.g. here 
https://sailfishos.org/wiki/Platform_SDK_Target_Installation#Platform_SDK_Targets_and_Toolings

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Yuvraaj Kelkar 
[yuvr...@gmail.com]
Sent: Sunday, December 31, 2017 12:21 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Compile without Scratchbox2 environment

The plan is to package up each Sailfish target into a Docker image to be used 
in a CI system.
For my purposes, Docker is a easy-to-use chroot that's also easy to share and 
deploy as compared to a virtual machine with a toolchain in sb2.

I do know that sb2 is more than just a chroot with bind mounts, but thats all I 
really need: a pre-populated chroot with bind mounts. Docker fits that bill 
quite nicely.

No, I don't want multiple targets in the same image.
No, I don't need the management of multiple build targets within the same 
Docker image.
I don't want any of the other sb2 features: I dont need Xephyr, I don't need to 
automagically run the compiled binary under qemu, etc.

Necessity is the mother of this re-invention.
Can you help?

Thanks,
-Yuvraaj

On Sat, Dec 30, 2017 at 2:23 PM, Tone Kastlunger 
>
 wrote:
I have personally nothing against docker.
I think however what you are trying to do is a bit unusual, to say the least.
Intending to use (at least as I understood it) docker as a substitute for SB2 
is "wrong" (if you pass me the word).
sb2 is more than "just" a virtualization layer bind-mounting directories. It 
manages build targets, for one, which docker does not know about,
and never will. Yes, of course you can have a single docker image for a single 
build target, with all the replica which comes with it;
or you can have one docker image with multiple toolchains / target envs; but 
then you have rolled your own sb2.

I cant but recall the words : those who do not understand Unix, are doomed to 
reinvent it, poorly.

Best,
tortoisedoc

On Fri, Dec 22, 2017 at 10:09 AM, Yuvraaj Kelkar 
>
 wrote:
I want to create a Docker image for Sailfish development.
I know it is possible to create a Docker image with sb2 in it; I've done that 
for other sb2 toolchains - Maemo and Harmattan.
However, those images can only run as privileged Docker containers because of 
sb2 bind mounts (I think).

I'd like to avoid being forced to run privileged Docker containers.
Also, running sb2 inside a Docker container seems like inception.

If it is possible to install the Sailfish toolchain without sb2, it should be 
possible to capture that into a non-privileged Docker image. (I hope)

The documentation for anything related to scratchbox is either hard to google 
or has broken links to 
maemo.org
 or is just non-existant.

As to why Docker and not sb2: "Why not?" and "Better documentation"

Thanks,
-Yuvraaj

On Thu, Dec 21, 2017 at 11:56 PM, Tone Kastlunger 
>
 wrote:
Out of curiosity, what's blocking you from using scratchbox?

On Fri, Dec 22, 2017 at 7:53 AM, Yuvraaj Kelkar 
>
 wrote:
Ha!
Any other ideas?

Thanks,
-Yuvraaj

On 12/21/17 8:08 PM, Juice wrote:
Yuvraaj Kelkar kirjoitti torstai 21. joulukuuta 2017:
Hi all,

Is it possible to compile for sailfish without using scratchbox2?

Thanks,
-Yuvraaj

Sure, just compile in the device itself... :)

   - juice -



___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to 

Re: [SailfishDevel] Route media sound stream to FIFO

[Martin Kampas]

Hi Michael,

Maybe editing /etc/pulse/xpolicy.conf could help you. Sources and possibly more 
information can be found here 
https://github.com/mer-hybris/droid-hal-configs/tree/master/sparse/etc/pulse .

BR,
Martin

From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Michael Fuchs 
[mic...@gmx.at]
Sent: Thursday, February 01, 2018 6:16 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Route media sound stream to FIFO

Hi,

I built snapcast for SailfishOS [2]. Snapcast is a "Synchronous multi-room
audio player". [1]

Everything works as expected now. Next step is the integration into Sailfish
user experience. It should be simple to create a GUI, which starts/stops the
snapclient.

But I don't know how to solve the server part of snapcast. Snapserver reads
audio data from a FIFO buffer and broadcasts it to the network.
Creating a pulseaudio FIFO sink is clear to me. Either you write it into the
config file pulse audio config file or load it via pacmd:

$ pacmd load-module module-pipe-sink file=/tmp/snapfifo 
sink_name=Snapcast
$ pacmd update-sink-proplist Snapcast device.description=Snapcast

But how do I route the media streams from the default sink to the FIFO-sink as
soon as snapserver is running? (Like when you plug in a headphone or connect
to a bluetooth device.)

Thanks for any advice.

cheers, Michael.



[1] https://github.com/badaix/snapcast
[2] https://build.merproject.org/package/show/home:fooxl:sailfish/snapcast


___
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] "Unnamed application is not responding" - How to respond from C and python?

[Martin Kampas]

Hi Jonas,

This example might help you 
https://github.com/sailfishos/sdk-sdl-project-example .

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Jonas Aaberg 
[c...@lithops.se]
Sent: Tuesday, January 30, 2018 11:24 AM
To: Zhang Bird
Cc: Sailfish OS Developers
Subject: Re: [SailfishDevel] "Unnamed application is not responding" - How to 
respond from C and python?

Yes, some help would be great!

Maybe create a wrapper util? Like

--
sfos_wrap "python3 mypygame.py"
--

Although, a flag in .desktop is probably prettier.

BR,
 Jonas


On Sat, 27 Jan 2018 16:47:48 +0800
Zhang Bird <0312birdzh...@gmail.com> wrote:

> To be honest, "harbour-pygame_breakout.cpp" is uglycode.
> I had the same question with you, and i didn't have a perfect
> solution so i used uglycode :(
>
> I tried pyotherside 
> with qml, but it not support for SDL2 currently.
> So, we need some help ;)
>
>
> 2018-01-27 14:58 GMT+08:00 Jonas Aaberg :
>
> >
> >
> > Hi,
> >
> > I tested two of my programs on SailfishOS:
> >  - texttv (https://bitbucket.org/gmelchett/texttv) written in
> > python, using pygame_sdl2
> >  - endlessman (https://bitbucket.org/gmelchett/endlessman/) written
> > in C using SDL2 (Needs some CFLAG changes to compile on Xperia X
> > due to gcc 4.x)
> >
> > Both works nicely on SailfishOS, except that I repeatedly get
> > "Unnamed application is not responding" with a some seconds in
> > between. Is there a way to respond from python and C? Or can I
> > somehow mark my programs as "don't communicate" with them to make
> > SailfishOS ignore them? Special option in .desktop?
> >
> > Or must there be some kind of wrapper, like this one:
> >
> > https://github.com/0312birdzhang/harbour-pygame_breakout/blob/master/src/
> > harbour-pygame_breakout.cpp
> >
> >
> > Btw, I didn't manage to get it to compile, to me the error looks
> > like the code is outdated (I'm completely green to QT and C++.. So
> > some help then would be appreciated!)
> >
> >
> > Best regards,
> >  Jonas
> > ___
> > SailfishOS.org Devel mailing list
> > To unsubscribe, please send a mail to devel-unsubscribe@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] GDB in the SailfishSDK

[Martin Kampas]

Hi Dylan,

Debugger component is selected by default during installation of the SDK, in 
which case GDB binaries for use with i486 and armv7hl devices are installed and 
preconfigured for use with the kits. There should be no extra steps required in 
order to enable their use with the kits. Did you exclude it during installation?

On the device side it should be enough to enable developer mode in settings and 
all packages necessary to enable debugging should be installed with this. Was 
it different in your case?

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Dylan Van Assche 
via Devel [devel@lists.sailfishos.org]
Sent: Tuesday, August 07, 2018 7:55 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] GDB in the SailfishSDK

Never mind, forgot to enable it in the kits...

Kind regards,
Dylan Van Assche


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On 7 August 2018 5:35 PM, Dylan Van Assche via Devel 
 wrote:

Hi,

I'm having some troubles installing GDB in the SailfishSDK...

What I already did:
- Install GDB in my OS
- Install GDB server and a Qt package as described by the SailfishSDK known 
issues
- QtCreator sees my GDB on the host OS

When I click on 'Start debugging' I get this after launching the debugging app:


Checking available ports...

Found 101 free ports

Starting gdbserver...

Starting gdbserver...

Waiting for gdbserver...


Listening on port 10001

Unknown debugger type "No engine"

Unable to create a debugging engine of the type "No engine"

The debugging engine required for combined QML/C++ debugging could not be 
created: %1

Unable to create a debugging engine of the type "QML C++ engine"

Anyone experience with GDB and the SailfishSDK?

Kind regards,
Dylan Van Assche


Sent with ProtonMail Secure Email.


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

Re: [SailfishDevel] Mer PIM build questions

[Martin Kampas]

Hi Lukáš,

First of all it may be worth noting that there is a "slight" difference between 
Ubuntu and Mer/Sailfish OS operating systems :) This has at least two 
implications: 1) not all Mer packages can be build against Ubuntu without 
modifications and 2) packages built against Ubuntu are not likely to work when 
deployed to a device running Mer/Sailfish OS.

If you are on Linux, get Sailfish OS Platform SDK [1]. If you are on Windows or 
Mac or if you want to use a Qt Creator based IDE on whichever platform, get 
Sailfish OS Application SDK [2].

There may be some hiccups while building these lower level packages with the 
application SDK but the workaround [3] pointed out by Chris shouldn't be needed 
unless I miss something. I tried to build buteo-sync-plugin-caldav with 
application SDK on Linux and Windows and the file permissions listed with `rpm 
-qlvp RPMS/*` seemed correct. The Qt Creator based IDE only works with qmake 
driven projects.

A frequent issue with these lower level packages is that they do not use the 
magic qtc_* macros in their RPM .spec files. See this example project to learn 
how to use these macros [4] (referred by [5]). Without these macros the build 
tool `mb2` (used directly or indirectly via Qt Creator) cannot separate qmake 
and make execution and more. You can start your contribution by adding these 
macros to buteo-sync-plugin-* packages for your own convenience :)

You don't need to bother with dependencies. All dependencies will be installed 
automatically upon the first build.

BR,
Martin

[1] https://sailfishos.org/wiki/Platform_Development
[2] https://sailfishos.org/wiki/Application_Development
[3] You don't need this 
https://sailfishos.org/wiki/CalDAV_and_CardDAV_Community_Contributions#Development_With_The_Sailfish_OS_Application_Developer_SDK
[4] https://github.com/sailfishos/cppqml-sample/blob/master/rpm/cppqml.spec
[5] https://sailfishos.org/wiki/Tutorial_-_Combining_C%2B%2B_with_QML



From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Lukáš Karas 
[lukas.ka...@centrum.cz]
Sent: Thursday, January 18, 2018 4:35 PM
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] Mer PIM build questions

Dne čtvrtek 18. ledna 2018 15:05:19 CET Pekka Vuorela napsal(a):
> On Thu, 2018-01-18 at 12:57 +0100, Lukáš Karas wrote:
> > Now the main question - when I try to build mer-core/timed, there are
> > few
> > `*.type` files that should be compiled by `iodata-qt5-type-to-c++`
> > tool.
> > But how this should be done in the build? In
> > src/server/server.pro:17
> > is defined IODATA_TYPES with list of these files, but there is
> > nothing about
> > it in generated Makefile. There is some qmake plugin or preparison
> > step
> > that I overlook?
>
> server.pro: CONFIG += iodata-qt5
> Suppose that picks up above. libiodata there:
> https://git.merproject.org/mer-core/libiodata
>
> Do wonder a bit where's the need for timed compilation, though.

Timed is required by mKCal, see:
https://git.merproject.org/mer-core/mkcal/blob/master/src/src.pro#L44

I do something wrong probably, I already have iodata in image:
https://github.com/Karry/mer-devel/blob/master/pim-docker/Dockerfile

>
> ___
> 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] Reproducible builds | RPM version

[Martin Kampas]

Hi Takimata,

Yes, upgrade of RPM is on the roadmap. I cannot be more specific about the 
schedule.

BR,
Martin


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of takimata 
[takim...@gmx.de]
Sent: Friday, March 30, 2018 1:05 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Reproducible builds | RPM version

Hi,

I would like to allow reproducible builds for my apps.
RPM 4.14.0 adds support for SOURCE_DATE_EPOCH, which allows to set the
"Build Date" contained inside the .rpm thus making the rpm non-reproducible.

(see https://reproducible-builds.org/specs/source-date-epoch/)

However,

"[mersdk@SailfishSDK /]$ rpm --version
RPM version 4.9.1.2"

which is quite old - from 2011! [2]


Can we expect a newer rpm version in a reasonable time frame for the
Sailfish SDK?

Thanks,
takimata

[1] http://rpm.org/wiki/Releases/4.14.0
[2] http://rpm.org/timeline.html
___
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] Command line arguments and DBus integration for QML/Python apps

[Martin Kampas]

Hi Rinigus,

libcontentaction might be what you are looking for https://
git.merproject.org/mer-core/libcontentaction

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

[SailfishDevel] SDK version 1.23 (Sailfish OS 3.0.0) is released to all users

[Martin Kampas]

Hello,

Today (Nov 19th) at 14:00 UTC we published new installers and repositories of 
the Sailfish OS SDK. This SDK release is called 1.23 and among other changes it 
enables development for Sailfish OS Release 3.0.0.

With this release we are switching from the YYMM versioning scheme to the 
X.Y[.Z] versioning. We are starting with the version 1.23 as this is the 23th 
regular release since the version 1312 which was retroactively designated as 
1.0.

The installers for this release of the SDK are available at 
http://sailfishos.org/wiki/Application_SDK#Latest_SDK_Release. If you have an 
older beta release of the SDK, you should see an update notification in the 
Sailfish OS IDE.

The Emulator and the latest Build Targets match Sailfish OS Release 3.0.0.8 
(Lemmenjoki). Build Targets for several older Sailfish OS releases remain 
available. 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 
reinstalled 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.
- Package repository contents have been updated and consequently using a 
previous SDK version with these package repositories is not supported.
- For more information, please see the Application SDK known issues list at 
https://sailfishos.org/wiki/Application_SDK_Known_Issues.


Release Content

SDK 1.23

SDK Installer/Maintenance Tool
- Added possibility to install Build Targets
  - Build Targets installed this way can be further configured through the SDK 
Control Centre as before
- Fixed installation under non-default installation path

SDK IDE (Qt Creator, Qt QmlLive)
- Refreshed API documentation available in the Help mode (Ctrl+7) in Qt Creator 
to Sailfish OS release 3.0.0.8 level
- Fixed issue with adding Qt creator to favorites on Ubuntu 18.04
- Fixed unwanted loading of Android plugin
- Added Qt Linguist component, available by right clicking a translation file 
(.ts) in an open project in Qt Creator and choosing Open With > Qt Linguist
  - If you are upgrading from a previous SDK release, you need to add the 
component manually

SDK Build Engine
- Preinstalled Build Targets refreshed to Sailfish OS release 3.0.0.8 level
- Extended sdk-assistant and sdk-manage with support for Tooling and Target 
images in the .tar.7z format used by installer
- mb2: Added --no-deps option to prevent updating dependencies

Emulator
- Emulator packages refreshed to Sailfish OS release 3.0.0.8 level
- Fixed display issues with e.g. application thumbnails when the scaled-down 
mode is used

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

Happy hacking,
Jolla SDK Team


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

Re: [SailfishDevel] Sailfish SDK 2.1 has been released to all users

[Martin Kampas]

Hi Lukáš,

Unfortunately this is a bug with the Harbour rules - please folow this report 
on TJC https://
together.jolla.com/question/206727/harbour-is-rejecting-rpm-package-build-by-latest-sdk/

BR,
Martin

On čtvrtek 30. května 2019 8:11:40 CEST Lukáš Karas wrote:
> Hi Sailors.
> 
> When I build my cmake-based project with recent SDK, everything works fine,
> but Harbour is refusing generated packages with this error message:
> 
>   No OS version and packages satisfy package requirements:
>   Requirement libstdc++.so.6(CXXABI_1.3.8) not available
>   Requirement libstdc++.so.6(GLIBCXX_3.4.20) not available
> 
> I am doing something wrong, or just some whitelist should be updated
> in the Harbour?
> 
> Lukas
> 
> Dne úterý 14. května 2019 15:02:02 CEST Jarkko Lehtoranta napsal(a):
> > Hello,
> > 
> > Today (May 14th) at 13:00 UTC the Sailfish SDK 2.1 has been released to
> > all
> > users. Please, check out the release notes from
> > https://together.jolla.com/question/204832/.
> > 
> > The installers for this SDK release are now available at
> > https://sailfishos.org/wiki/Application_SDK#Latest_SDK_Release. If you
> > have
> > an older beta release of the SDK, you should see an update notification in
> > the Sailfish OS IDE. The 2.1 Early Access SDK users will get an update
> > notification about the new Emulator and Build Targets.
> > 
> > If you have any questions, feel free to either send an email to this
> > mailing list: devel at lists.sailfishos.org, write it up in
> > http://together.jolla.com and tag your issue with ‘sdk’ or send an e-mail
> > to developer-care at jolla.com.
> > 
> > Happy hacking,
> > Jolla SDK Team
> > ___
> > 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] Harbour validator bug? RPM validation fails on QtSensors 5.2

[Martin Kampas]

Hi Tamas,

The issue with RPM validation inside SDK is now under 
investigation. Please try to submit you app to the Harbour again 
- the failure there might be related to https://together.jolla.com/
question/206727 which was fixed recently and so possibly fixed 
as well.

BR,
Martin

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

Re: [SailfishDevel] [python/qml] packaging issues

[Martin Kampas]

Hi Eli,

> 1. The package that gets built includes python bytecode files (*.pyc and
> *.pyo)

That's desired AFAIK

> 2. The package is architecture specific instead of "noarch"

You can add the following to your .yaml:

  BuildArch: noarch

> [...] which the SDK wants to
> autogenerate based on the .pro and the .yaml files as far as I understand.

Just the .yaml is consulted when generating the .spec.

> Also does harbour accept mpris now or does the fact that the SDK screams
> about that mean I have no chance of updating?

The two FAQ items https://harbour.jolla.com/faq#2.16.0 and 
https://harbour.jolla.com/faq#6.1.0 
refer to the list of allowed dependencies - mpris is not listed there. You 
should be able to 
package mpris with you package to avoid the dependency on system mpris - such 
an approach 
is allowed of course.

BR,
Martin

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

Re: [SailfishDevel] SyncML profile Nokia Services what is the difference

[Martin Kampas]

Hi,

It is not the '-d' flag that fixes it - this is a shortcut for '--enable-debug' 
:) Just the path to the 
source directory '..' is enough.

BR,
Martin

On pondělí 15. července 2019 13:20:40 CEST deloptes wrote:
> Tone Kastlunger wrote:
> > [mersdk@SailfishSDK build]$ mb2  -t SailfishOS-3.0.3.9-armv7hl -s
> > ../rpm/buteo-syncfw-qt5.spec build
> 
> when you try to build from within a build directory, you have to specify the
> root directory with -d flag
> 
> I use following
> 
> mb2 -t SailfishOS-3.0.2.8-armv7hl -s ../rpm/buteo-syncfw-qt5.spec \
>  build -j4 -d ../
> HERE ->^^
> 
> regards
> 
> PS: also you do not need the bluez4, but bluez5
> 
> ___
> 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] Error installing .desktop file

[Martin Kampas]

On úterý 20. srpna 2019 11:11:57 CEST Thomas Tanghus wrote:
> "Martin Kampas"  – 20. august 2019 11:00
> 
> > The .desktop file must exist in the same directory where the .pro file
> > that
> > uses CONFIG+=sailfishapp exists.
> 
> It is.

It isn't :)

https://github.com/tanghus/currency-converter-qml/blob/eaa6112c1c8e072f229b6c295c71e3f2a25fab11/harbour-currencyconverter.pro#L19
 - here the config is commented out.

https://github.com/tanghus/currency-converter-qml/blob/eaa6112c1c8e072f229b6c295c71e3f2a25fab11/src/src.pro#L8
 - here the config is effective.

https://github.com/tanghus/currency-converter-qml/blob/eaa6112c1c8e072f229b6c295c71e3f2a25fab11/harbour-currencyconverter.desktop
 - so this should be next to src.pro

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

Re: [SailfishDevel] Error installing .desktop file

[Martin Kampas]

Hi,

The .desktop file must exist in the same directory where the .pro file that 
uses 
CONFIG+=sailfishapp exists.

Note that the subdirs template does not require you actually put stuff to 
subdirectories - you 
can specify a .pro file that exists in the same directory instead of a 
subdirectory https://
doc.qt.io/qt-5/qmake-variable-reference.html#subdirs. This way you should be 
able to keep the 
standard layout with .desktop and other files in the root directory and yet use 
the subdirs 
template to split the build.

BR,
Martin

On úterý 20. srpna 2019 10:44:38 CEST Thomas Tanghus wrote:
> "Thomas Tanghus"  – 20. august 2019 09:24
> 
> > It's in the underlying 'src' directory:
> > Maybe this isn't the best way to organize it? It has worked for me in
> > another app, but I thing there has been a new SDK release since that.
> 
> This is the current state of the app (bear with me, it's in a deconstructive
> state. First app I wrote so it's much of a rewrite.)
> 
>   https://github.com/tanghus/currency-converter-qml
> 
> This is the app with a very similar build setup, and which actually builds
> and deploys ok with the newest SDK.
> 
>   https://github.com/tanghus/kitchen-timer-qml
> 
> --
> /Thomas
> 
> A: Because it breaks the logical sequence of discussion
> Q: Why is top posting bad?
> 
> ___
> 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] Importing my own QML plugin. Take two...

[Martin Kampas]

Hi Thomas,

> On the other hand, I couldn't even explain how I did it 4 years 
ago[2] :P

This way https://github.com/tanghus/kitchen-timer-qml/blob/
master/src/harbour-kitchentimer.cpp#L74 :)

BR,
Martin

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

[SailfishDevel] Sailfish SDK 2.2 has been released to all users

[Martin Kampas]

Hello,

Today (July 31th) at 07:00 UTC the Sailfish SDK 2.2 has been released to all 
users. Please, check out the release notes from https://together.jolla.com/
question/210749/.

The installers for this SDK release are now available at 
https://sailfishos.org/wiki/
Application_SDK#Latest_SDK_Release. If you have an older release of the SDK 
installed, you should see an update notification in the Sailfish OS IDE.

If you have any questions, feel free to either send an email to this mailing 
list: 
devel at lists.sailfishos.org, write it up in http://together.jolla.com and tag 
your 
issue with ‘sdk’ or send an e-mail to developer-care at jolla.com.

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

Re: [SailfishDevel] Error starting build Engine

[Martin Kampas]

Hi Iosif,

> Under Win10 during installation I get the following error: SSH timeout.
> 
> If I press retry I continuously get the same error. If I press ignore I get
> the same error for all targets. At some time the installation succeeds, but
> cannot start the build engine

The installation is likely to be broken, but still it may be in a state that 
can be used to debug the 
connection issue more conveniently that during the installation, so let's 
continue with that.

Could you please try if you can SSH to the build engine from command line using 
something like 
this from the Git Bash? (Start the VM first, using VBox interface.)

ssh -p  -i /c/SailfishOS/vmshare/ssh/private_keys/engine/mersdk 
mersdk@localhost

If this fails, try with one or more '-v' to increase SSH's verbosity.

Next, could you please collect the debug output from Qt Creator? You should be 
able to enable 
the necessary logging categories by creating the file 
C:\SailfishOS\bin\QtProject\qtlogging.ini 
with the following content:

[Rules]
mer.vms*.debug=true
qtc.ssh.debug=true

(Check https://doc.qt.io/qt-5/qloggingcategory.html#configuring-categories for 
more info)

AFAIK on Windows you will also need to run Qt Creator under debugger in order 
to see the 
console output. I use WinDbg for that, in File -> Open Executable choose C:
\SailfishOS\bin\qtcreator.exe and also file Start directory in the same dialog 
as C:\SailfishOS\bin 
(important!).

BR,
Martin

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

Re: [SailfishDevel] Error starting build Engine

[Martin Kampas]

Hi Thomas,

All the errors in the log you shared are expected errors, they do not cause any 
issue.

The error "Another instance for VM "Sailfish OS Emulator 3.1.0.12" already 
exists" is also unrelated to your issues.

The errors from qt.network.ssl are something I would be worry about, but again 
it is not related 
to your issues.

What I bet is (was) the source of your issues is the content of your 
VirtualBox.xml.

>  
> src="/home/tol/SailfishOS/mersdk/Sailfish OS Build Engine/Sailfish
> OS Build Engine.vbox"/>>   
>  
> src="/home/tol/SailfishOS/emulator/Sailfish OS Emulator/Sailfish OS
> Emulator.vbox"/>>   
>  
> src="/home/thomas/SailfishOS/mersdk/MerSDK/MerSDK.vbox"/>
>   
>  
> src="/home/thomas/SailfishOS/mersdk/Sailfish OS Build
> Engine/Sailfish OS Build Engine.vbox"/>>   
>  
> src="/home/thomas/SailfishOS/emulator/Sailfish OS Emulator
> 3.1.0.12/Sailfish OS Emulator 3.1.0.12/Sailfish OS Emulator
> 3.1.0.12.vbox"/>> 
> 

Did you change your user name in past or so?

There are two entries with "/home/tol/" as the home directory, while the others 
have "/home/
thomas/". One of them is for a "Sailfish OS Build Engine" from some older SDK 
installation that I 
believe is not available anymore on that path under /home/tol, which would be a 
possible reason 
to end with VBOX_E_INVALID_OBJECT_STATE. Qt Creator uses VM names instead of 
UUIDs, so 
which VM would it be trying to start with `vboxmanage startvm 'Sailfish OS 
Build Engine'`? The 
existing one under /home/thomas or the unavailable one under /home/tol?

BR,
Martin

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

Re: [SailfishDevel] Question about connecting a Sailfish phone to Ubuntu Linux box

[Martin Kampas]

Hello Sahlan,

> [...] I did that in QtCreator and chose the Build / Deploy option, and it
> told me RPMs had been created OK, but, under the Issues tab, I get the
> message "No RPM validation suite is available for the current Sailfish
> OS build target, the package will not be validated"
> 
>   Then I clicked Debug / Start and Break on Main, but nothing happens.
> I've searched for info on how to debug on Sailfish with QtCreator but
> haven't found anything. Can anyone suggest a url for a step by step page
> of instructions?

Check https://sailfishos.org/wiki/Application_SDK_Your_First_App, scroll down 
to "Set ARM Kit to 
Deploy to Device" and read through the end of the page (known issue: the page 
layout is 
somehow broken right now).

By default the "Build RPM Package for Manual Deployment" deployment method 
includes the 
"RPM Validation" step. Your build targets (3.0.0.8) are too old and does not 
come with any RPM 
validation suite, hence the warning. Try with a more recent build target after 
you upgrade 
your phone.

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

Re: [SailfishDevel] SDK versioning

[Martin Kampas]

Hi Eli,

does the Android SDK version match the Android OS version?
does the macOS SDK version match the macOS version?
does the Windows SDK version match the Windows OS version?
does the Qt Creator version match the Qt version?
...

The universal answer is No, simply because the SDK and the platform are two 
different products 
with their own life cycles.

Each Sailfish SDK version supports multiple Sailfish OS versions. Currently 
this means the latest 
OS version published to all users + some older OS versions. Soon, we will start 
releasing also 
build targets for the latest OS version published to EA users.

You can be sure the links published on https://sailfishos.org/wiki/
Application_SDK#Latest_SDK_Release always point to the latest SDK release, so 
unless you dig 
them out yourself, you cannot download older installers by mistake.

Enjoy using the latest greatest SDK and forget about version numbers, they 
become important 
only when dealing with issues :)

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

Re: [SailfishDevel] Sailfish SDK 2.2 has been released to all users

[Martin Kampas]

Hi Damien,

It is likely you do not see an update available because you 
have no Early Access Build Target installed. Please check the 
TJC post linked before for instructions on installing Early 
Access Build Targets and more information.

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

Re: [SailfishDevel] SDK again, again...

[Martin Kampas]

Hi Thomas,

The error messages in the tool tip shown when the *-armv7hl kit is hovered tell 
you the 
device selected in kit configuration is architecture incompatible with the kit. 
The kit 
supports armv7hl devices while the device (Sailfish OS Emulator) is an x86 
device. You can 
still use the kit to build RPM packages for the armv7hl architecture, you will 
just not be 
able to run those directly from Qt Creator. For that you need to provide a 
hardware device 
with that architecture and configure the kit to use that instead of the 
emulator. Use the *-
i486 kit if you want to run your software under the Sailfish OS Emulator.

The installation log currently contains information that is mostly useful to 
someone with 
knowledge of SDK installer internals. An error message appearing there is not 
necessary 
meaning something wrong. The installer would complain verbosely if an 
installation error 
really occurred.

The SSL-related errors are not likely to affect SDK functions regularly 
involved in Sailfish 
OS application development.

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

[SailfishDevel] Sailfish SDK 2.4 has been released to all users

[Martin Kampas]

Hello,
 
Today (Dec 2nd) at 14:00 UTC the Sailfish SDK 2.4 was released to all users. 
Please, check out the release notes from 
https://together.jolla.com/question/218412/[1].
 
The installers for this SDK release are now available at 
https://sailfishos.org/wiki/Application_SDK#Latest_SDK_Release[2]. If you have 
an older release of the SDK installed, you should see an update notification in 
the Sailfish IDE.

If you have any questions, feel free to either send an email to this mailing 
list: devel at lists.sailfishos.org, write it up in 
http://together.jolla.com[3] and tag your issue with ‘sdk’ or send an e-mail to 
developer-care at jolla.com.
 
Happy hacking,
Jolla SDK Team


[1] https://together.jolla.com/question/218412/
[2] https://sailfishos.org/wiki/Application_SDK#Latest_SDK_Release
[3] http://together.jolla.com
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Sailfish SDK 2.2 has been released to all users

[Martin Kampas]

Hello,

Today (Nov 1) at 14:00 UTC we published an update to the Early Access Build 
Targets. These 
match the Sailfish OS release 3.2.0.12 (Torronsuo) now.

More details can be found under "Update #1" headline at 
https://together.jolla.com/question/
210749/release-notes-sailfish-sdk-22/[1] .

Happy hacking, 
Jolla SDK Team


On Wed 31 Jul 2019 10:11:39 CET Martin Kampas wrote:
> Hello,
> 
> Today (July 31th) at 07:00 UTC the Sailfish SDK 2.2 has been released to all
> users. Please, check out the release notes from https://together.jolla.com/
> question/210749/.
> 
> The installers for this SDK release are now available at
> https://sailfishos.org/wiki/ Application_SDK#Latest_SDK_Release. If you
> have an older release of the SDK installed, you should see an update
> notification in the Sailfish OS IDE.
> 
> If you have any questions, feel free to either send an email to this mailing
> list: devel at lists.sailfishos.org, write it up in
> http://together.jolla.com and tag your issue with ‘sdk’ or send an e-mail
> to developer-care at jolla.com.
> 
> Happy hacking,
> Jolla SDK Team




[1] https://together.jolla.com/question/210749/release-notes-sailfish-sdk-22/
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Error with libstdc++.so.6(CXXABI_1.3.8)

[Martin Kampas]

Hi,

> You're using an SDK targeted at newer releases [...]

More correctly it is the "built target" (under Qt Creator this 
corresponds to "kit") which is incompatible with your older Sailfish OS 
release. You can install build targets (as well as emulators) matching 
older Sailfish OS releases using the SDK Maintenance Tool.

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

Re: [SailfishDevel] Sailfish SDK 3.0 has been released to Early Access

[Martin Kampas]

Hello,

Today (Apr 3rd) at 14:00 UTC we published an update to the Early Access Build 
Targets. These now match the Sailfish OS release 3.3.0.14 (Rokua).

More details can be found under "Update #2" headline at 
https://together.jolla.com/question/220011[1] .

If you have any questions, feel free to either send an email to this mailing 
list: devel at lists.sailfishos.org, write it up in 
http://together.jolla.com[2] and tag your issue with ‘sdk’ or send an e-mail to 
developer-care at jolla.com. 

Happy hacking,
Jolla SDK Team



[1] https://together.jolla.com/question/220011
[2] http://together.jolla.com
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Sailfish SDK 3.1 has been released to Early Access

[Martin Kampas]

Hi Thomas,

> I first tried the online installer, but the repository couldn't be found.

In your later email you continue:

> Because I didn't read the release notes properly...

Right after your first email I thought it was just a temporary error in your 
download 
location, but now that you write about reading release notes properly I am 
curious what 
was the issue more specifically? Maybe it was something we should highlight 
more there.

> libtinfo5 is in Ubuntu 19.10 described as "legacy version", so maybe the SDK
> should link against a newer version; at least when Ubuntu 20.04 LTS is
> released. Isn't it by now, btw?

Sailfish SDK links against older libraries in order to support older operating 
systems, which 
is often the case of corporate users. Listed here https://sailfishos.org/wiki/
Application_SDK_Known_Issues[1] .

> Anyways, I installed the legacy version and it seems to work, but I don't
> even know what Clang does to start with ;)

You can start by reading e.g. 
https://www.qt.io/blog/2018/06/05/qt-creators-clang-code-model[2] .

BR,
Martin


[1] https://sailfishos.org/wiki/Application_SDK_Known_Issues
[2] https://www.qt.io/blog/2018/06/05/qt-creators-clang-code-model
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Sailfish SDK 3.1 has been released to Early Access

[Martin Kampas]

Hi Thomas,

Switching the updates/updates-ea repositories is actually only needed to 
subscribe for 
future EA updates. The installation is not affected by this change (unless you 
use an 
older installer at the time an EA update is already available).

So it seems it was really just a temporary download error which disappeared by 
the time 
your tried again after changing repository settings.

> Now I just have to figure why some QML modules can't be imported...

If you mean that there are red highlights etc. in the source code opened in Qt 
Creator, 
then this is likely because the QML modules are not installed in the (active) 
build target. 

If the QML modules are provided by packages pulled in as BuildRequires in 
.spec, all you 
should need to do is rebuilding the project (or just running qmake).

If the QML modules are not pulled in as BuildRequires, you need to install them 
manually 
into the build target using Options > Sailfish OS > Build Engine > Manage Build 
Targets > 
Manage Packages under Qt Creator or from command line using `sfdk tools package-
install`.

Should you still have troubles fixing that, it would be nice to get more info 
about the 
modules and the content of your .spec at least.

BR,
Martin

On pátek 1. května 2020 13:42:52 CEST Thomas Tanghus wrote:
> On Friday, 1 May 2020 13.19 Martin Kampas wrote:
> > Right after your first email I thought it was just a temporary error in
> > your download location, but now that you write about reading release
> > notes properly I am curious what was the issue more specifically? Maybe
> > it was something we should highlight more there.
> 
> You have actually made it quite clear in in the linked notes. Reading them
> does help ;)
> https://sailfishos.org/wiki/Application_SDK_Early_Access#Installing_the_Ear
> ly_Access_SDK
> 
> 1. Open the Sailfish OS SDK Installer
> 2. Click Settings
> 3. Go to the Repositories page
> 4. Uncheck (Disable) the updates repository
> 5. Check (Enable) the updates-ea repository
> 6. Click OK and continue with the installation instructions
> 
> > > libtinfo5 is in Ubuntu 19.10 described as "legacy version", so maybe the
> > > SDK should link against a newer version; at least when Ubuntu 20.04 LTS
> > > is released. Isn't it by now, btw?
> > 
> > Sailfish SDK links against older libraries in order to support older
> > operating systems, which is often the case of corporate users. Listed
> > here https://sailfishos.org/wiki/Application_SDK_Known_Issues[1] .
> 
> I had not seen that. Thanks.
> 
> > > Anyways, I installed the legacy version and it seems to work, but I
> > > don't even know what Clang does to start with ;)
> > 
> > You can start by reading e.g.
> > https://www.qt.io/blog/2018/06/05/qt-creators-clang-code-model[2] .
> 
> Yes, I was being lazy ;) Julien also explained. Thanks to both.
> 


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

Re: [SailfishDevel] ContextKit not installed?

[Martin Kampas]

Hi Thomas,

> it isn't recognized in the
> editor, "QML module does not contain information about components 
contained
> in the plugins".

I checked that now and I confirm this is a bug - the package does not provide 
the 
QML type information. 
You can work this around by using qmlplugindump on your device to generate a 
plugins.qmltypes file and copy it into the corresponding plugin directory under 
~/
SailfishOS/mersdk/targets//usr/lib/qt5/qml/.

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

Re: [SailfishDevel] sfdk deploy, building for wrong architecture

[Martin Kampas]

Hi Chris,

This bug will be fixed with the upcoming SDK release 3.1 
(soon).

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

[SailfishDevel] Sailfish SDK 3.1 has been released to Early Access

[Martin Kampas]

Hello,

Today (Apr 30th) at 10:00 UTC the Sailfish SDK 3.1 was released to Early Access 
users. 
Please, check out the release notes from 
https://together.jolla.com/question/226423/[1] .

The installers for this SDK release are now available at 
https://sailfishos.org/wiki/
Application_SDK_Early_Access#Latest_Early_Access_SDK_Release[2] . If you have 
an older 
Early Access release of the SDK installed, you should see an update 
notification in the 
Sailfish IDE.

If you have any questions, feel free to either send an email to this mailing 
list: devel at 
lists.sailfishos.org, write it up in http://together.jolla.com[3] and tag your 
issue with ‘sdk’ 
or send an e-mail to developer-care at jolla.com. 

Happy hacking,
Jolla SDK Team


[1] https://together.jolla.com/question/226423/
[2] https://sailfishos.org/wiki/
Application_SDK_Early_Access#Latest_Early_Access_SDK_Release
[3] http://together.jolla.com
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Docker build engine

[Martin Kampas]

Hi George,

As long as you list all your dependencies in the .spec file (you seem to do so 
in the 
linked sources), you do not need to do anything to get them installed. 
Installing 
build time dependencies happens automatically as part of the build process.

Should you need to manage packages under build targets for some reason, you may 
use either Qt Creator > Options > Sailfish OS > Build Engine > Manage Build 
Targets > 
Manage packages, or achieve the same on command line with `sfdk tools package-
install` and related commands. Find sfdk in the bin subdirectory of Sailfish 
SDK 
installation directory.

BR,
Martin


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

Re: [SailfishDevel] Fwd: Docker build engine

[Martin Kampas]

Hello Schorsch,

> error: failed to replace old database with new database!
> error: replace files in /var/lib/rpm with files from
> /var/lib/rpmrebuilddb.4682 to recover

Looks like https://bugzilla.redhat.com/show_bug.cgi?id=1680124[1] .

I would try doing what the message advices. WRT the information from comment #4 
under the bug report, simply renaming the directories may not work, so possibly 
removing files in /var/lib/rpm and then copying files from 
/var/lib/rpmrebuilddb.4682 
could work.

BR,
Martin



[1] https://bugzilla.redhat.com/show_bug.cgi?id=1680124
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Fwd: Docker build engine

[Martin Kampas]

Hello Schorsch,

OK, let's see if we can reproduce it. What is your host OS 
and Docker version please?

BR,
Martin

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

Re: [SailfishDevel] Sailfish SDK 3.1 has been released to all users

[Martin Kampas]

Hello,


Today (May 7th) at 11:00 UTC the Sailfish SDK 3.1 has been released to all 
users. Please, check out the in depth release notes from 
https://together.jolla.com/question/226423/.


The installers for this release of the SDK are now available at 
http://sailfishos.org/wiki/Application_SDK#Latest_SDK_Release. If you have an 
older release of the SDK, you should see an update notification in the Sailfish 
IDE.


If you have any questions, feel free to either send an email to this mailing 
list: devel at lists.sailfishos.org<http://lists.sailfishos.org>, write it up 
in http://together.jolla.com and tag your issue with 'sdk' or send an e-mail to 
developer-care at jolla.com<http://jolla.com>.


Happy hacking,

Jolla SDK Team



From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Martin Kampas 
[martin.kam...@jolla.com]
Sent: Thursday, April 30, 2020 12:49 PM
To: Sailfish OS Developers
Subject: [SailfishDevel] Sailfish SDK 3.1 has been released to Early Access


Hello,



Today (Apr 30th) at 10:00 UTC the Sailfish SDK 3.1 was released to Early Access 
users. Please, check out the release notes from 
https://together.jolla.com/question/226423/ .



The installers for this SDK release are now available at 
https://sailfishos.org/wiki/Application_SDK_Early_Access#Latest_Early_Access_SDK_Release
 . If you have an older Early Access release of the SDK installed, you should 
see an update notification in the Sailfish IDE.



If you have any questions, feel free to either send an email to this mailing 
list: devel at lists.sailfishos.org, write it up in http://together.jolla.com 
and tag your issue with ‘sdk’ or send an e-mail to developer-care at jolla.com.



Happy hacking,

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

Re: [SailfishDevel] Docker build engine

[Martin Kampas]

Hi Schorsch,

> it finds only the already installed lib.

So that's a bug - the repositories are not refreshed automatically in the 
Docker-based build 
engine.

You can fix that simply by using Qt Creator > Options > Sailfish OS > Build 
Engine > 
Manage Build Targets > Refresh or from command line with `sfdk tools update` 
for each 
build target.

BR,
Martin

On úterý 12. května 2020 7:08:21 CEST george b wrote:
> Thank you both for your comments. One step closer, but does not solve my
> issue.
> 
> If I use the GUI way to search for the devel headers, it finds only the
> already installed lib.
> 
> SSH into the mer docker build engine results in similar output:
> > ssh -p  -i
> 
> ~/bins//SailfishOS317/vmshare/ssh/private_keys/engine/mersdk
> mersdk@localhost
> 
> > sb2 -t SailfishOS-3.3.0.16-armv7hl -m sdk-install -R zypper up
> 
> Loading repository data...
> Reading installed packages...
> 
> Nothing to do.
> 
> > sb2 -t SailfishOS-3.3.0.16-armv7hl -m sdk-install -R zypper se *ssl*
> 
> Loading repository data...
> Reading installed packages...
> 
> S | Name | Summary |
> Type
> --+--+-+
>  i | openssl-libs | A general purpose cryptography library with TLS i->
> | package
> 
> > ls
> 
> /host_install/mersdk/targets/SailfishOS-3.3.0.16-armv7hl/usr/include/openssl
> * ls: cannot access
> '/host_install/mersdk/targets/SailfishOS-3.3.0.16-armv7hl/usr/include/openss
> l': No such file or directory
> 
> It seems to me that the openssl-devel package is not available in the repo,
> neither installed in the system. Same issue for libxml2-devel.
> 
> Further suggestions are welcome :-).
> 
> Best regards
> Schorsch
> 
> Am Mo., 11. Mai 2020 um 22:14 Uhr schrieb Martin Kampas <
> 
> martin.kam...@jolla.com>:
> > Hi George,
> > 
> > 
> > 
> > As long as you list all your dependencies in the .spec file (you seem to
> > do so in the linked sources), you do not need to do anything to get them
> > installed. Installing build time dependencies happens automatically as
> > part
> > of the build process.
> > 
> > 
> > 
> > Should you need to manage packages under build targets for some reason,
> > you may use either Qt Creator > Options > Sailfish OS > Build Engine >
> > Manage Build Targets > Manage packages, or achieve the same on command
> > line
> > with `sfdk tools package-install` and related commands. Find sfdk in the
> > bin subdirectory of Sailfish SDK installation directory.
> > 
> > 
> > 
> > BR,
> > 
> > Martin


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

Re: [SailfishDevel] Sailfish SDK 3.1 has been released to all users

[Martin Kampas]

Hello Damien,

> I guess Harbour scripts will be upgraded soon. At the moment, 
when
> uploading a newly built package, it complains that no OS matches 
the
> requirements.

Thank you for reporting. Please try again now.

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

Re: [SailfishDevel] Sailfish SDK 3.2 has been released to Early Access

[Martin Kampas]

Hi,

> Am I correct in understanding that the mailing list is being shut down?

Yes, see https://blog.jolla.com/new-forum-for-sailfish-os-discussion/[1] .

> Also does a normal forum also mean we now get a normal bug tracker?

This question is too general for a quick answer I am afraid. Maybe you can 
answer yourself after checking the activity in the Bug Reports category https://
forum.sailfishos.org/c/bug-reports/13[2] .

BR,
Martin


[1] https://blog.jolla.com/new-forum-for-sailfish-os-discussion/
[2] https://forum.sailfishos.org/c/bug-reports/13
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org