maemo.org - Talk
Page 7 of 8 « First 56 7 8
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)
-   -   Sailfish SDK version 1608 (2.0.2) Qt5 released (https://talk.maemo.org/showthread.php?t=89294)

swamp 2014-01-11 21:43
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by solbrit (Post 1400720)
Okay, getting desperate here. Trying to run the SDK on Debian Wheezy.
Sailfish SDK Alpha 1312 works on Debian Wheezy LXDE.

rcolistete 2014-01-15 15:29
Re: Sailfish SDK Alpha 1312 Qt5 released
 
This Sailfish SDK update doesn't have a new download, it installs inside the SDK.

[SailfishDevel] SailfishOS SDK January update available today.
Quote:
Jarko Vihriala jarko.vihriala at jolla.com
Wed Jan 15 15:24:18 UTC 2014

Hello again,

Today at 16:00 UTC we are publishing a little update on SailfishOS SDK. The update itself touches only the Build Engine.

What you need to do is to boot up the Build Engine after the updates have been published (i.e. click the sdk icon in Qt Creator) and wait 10 minutes while it refreshes its repositories. Then access the SDK Control Center Updates view and you should see that Engine updates are available.

Release note:
- SDK Control Center

* - Download and reinstall build targets (i.e.) sysroots. This is done using the new pull-down menu called 'Pre-configured targets' in 'Targets' view of Control Center.

* - Provide a tool to verify that basic submission criterias are fulfilled with Harbour intake requirements. This is done from the new view called 'Harbour Tools' in Control Center.

If you have any questions, you can either send email to this mailing list: devel at lists.sailfishos.org or write it up on together.jolla.com and tag your issue with 'sdk'.

Happy hacking,
Jolla SDK Team.

rcolistete 2014-01-28 16:45
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Another Sailfish SDK update in January, which is installed inside the SDK :
[SailfishDevel] SailfishOS SDK January update 2 available today
Quote:
Juha Kallioinen juha.kallioinen at jolla.com
Tue Jan 28 11:06:29 UTC 2014

Hello,

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

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

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

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

Happy hacking,
Jolla SDK Team.
There is also an update for rpmvalidator package :
Quote:
Hi,

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

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

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

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

Best regards,
Juha

droll 2014-02-07 01:52
Re: Sailfish SDK Alpha 1312 Qt5 released
 
folks - how do i Qt Creator to deploy to the actual Jolla device? I have already configured Tools->Options->Devices. i selected
1. Add
2. Select "Generic Linux Device" (I only see option for this and "Mer Emulator Device")
3. Configured the options for IP address, user name, etc.

Then I tested the configuration by clicking on "Test" button on the right. Test works / passes successfully.

Now how do I deploy my sample project to the phone? each time i try to deploy it says "Could not connect to SailfishOS Emulator Virtual Machine".

help?

evk 2014-02-07 07:27
Re: Sailfish SDK Alpha 1312 Qt5 released
 
I don't remember the specifics, but you have to add your device under tools->options->devices.

droll 2014-02-07 23:17
Re: Sailfish SDK Alpha 1312 Qt5 released
 
tried that. i have it added already but everytime i compile and deploy, it always targets the emulator. how do i change that?

junnuvi 2014-02-08 00:30
Re: Sailfish SDK Alpha 1312 Qt5 released
 
As I have understood it will always require working emulator to compile and build packages / binaries. After that you can make it automatically deploy rpm or binaries to actual device.

To enable possibility to deploy to device you need to have kit defined under projects where actual device is defined as Device.

More professionals can correct in case I'm talking ********. But this is how I use it :)

evk 2014-02-08 07:52
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Under the projects tab, you choose your build and run target.

There's two "emulators" or virtual machines. One build engine that's running mer; that one is required. And one sailfish emulator, that's not necessary.

mariusmssj 2014-02-08 08:56
Re: Sailfish SDK Alpha 1312 Qt5 released
 
-First of all you don't add Generic Linux Device but add Mer ARM Device Tools->Options->Devices->Add

-Your PC needs to be on 192.168.2.X sub domain, thus your local IP need to begin with 192.168.2.

- In project tabs you will need to add a MerSDK_SailfishOS_armv7hl kit if not already there

- And then pick deployment target like on the image below
http://i.imgur.com/fsCwu6n.png

If I get some time I will make a full guide

evk 2014-02-08 09:11
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by mariusmssj (Post 1411632)
-Your PC needs to be on 192.168.2.X sub domain, thus your local IP need to begin with 192.168.2.
To clarify, that's for the the usb device. You probably do not want to change your LAN address.

droll 2014-02-11 19:20
Re: Sailfish SDK Alpha 1312 Qt5 released
 
@mariusmssj

thank you for the screenshots. i will try that in a while.

in the meantime, does anyone know how i can build a console application for Sailfish that uses Qt? i only want to use certain Qt classes with no UI.

i must be missing something in my .pro file as the compiler is complaining about unresolved symbols? i created a new project under Qt Creator as C++ application.

i also tried creating a SailfishOS project and in main.cpp I have my code added in. I commented out

Quote:
//Sailfish::showView(view.data());
//return app->exec();
same thing. still complaining about unresolved symbols. i am trying to use QFeedbackHapticsEffect and QFeedbackActuator. my #include section looks like this

#include <QtFeedback/QFeedbackActuator>
#include <QtFeedback/QFeedbackHapticsEffect>
#include <QGuiApplication>
#include <QQuickView>

droll 2014-02-11 19:24
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by mariusmssj (Post 1411632)
-First of all you don't add Generic Linux Device but add Mer ARM Device Tools->Options->Devices->Add

-Your PC needs to be on 192.168.2.X sub domain, thus your local IP need to begin with 192.168.2.

- In project tabs you will need to add a MerSDK_SailfishOS_armv7hl kit if not already there

...
wait a sec. i don't see Mer ARM Device in the list. I only see Generic Linux Device and Mer Emulator Device.

tried updating the SDK via control panel (yes, i develop on Windows) and it only found an updated maintenance tool.

edit: i think i'll uninstall the SDK and download a copy. i had mine installed before Mer ARM Device support was added sometime around mid Dec last year.
??

mariusmssj 2014-02-11 19:29
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by droll (Post 1412285)
wait a sec. i don't see Mer ARM Device in the list. I only see Generic Linux Device and Mer Emulator Device.

tried updating the SDK via control panel (yes, i develop on Windows) and it only found an updated maintenance tool.

edit: i think i'll uninstall the SDK and download a copy. i had mine installed before Mer ARM Device support was added sometime around mid Dec last year.
??
So you don't see this?
http://i.imgur.com/Y5lvivN.png

droll 2014-02-11 19:48
Re: Sailfish SDK Alpha 1312 Qt5 released
 
nope, don't see it.

i just uninstalled, downloaded a new copy , and installed the new copy.

i see it now. :) thanks!

droll 2014-02-11 19:58
Re: Sailfish SDK Alpha 1312 Qt5 released
 
so does anyone know why i'm getting all these unresolved symbols.... :(

evk 2014-02-11 20:28
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by droll (Post 1412296)
so does anyone know why i'm getting all these unresolved symbols.... :(
Which symbols do the linker complain about? Probably something missing to the QT or QTPLUGIN variable in the .pro file.

droll 2014-02-11 23:37
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Code:
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:17: error: undefined reference to `QFeedbackActuator::actuators()'
C:\Users\xxx\Documents\Jolla\TestVibraUI\main.cpp:24: error: undefined reference to `QFeedbackActuator::name() const'
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:40: error: undefined reference to `QFeedbackHapticsEffect::QFeedbackHapticsEffect(QObject*)'
C:\Users\xxx\Documents\Jolla\TestVibraUI\main.cpp:42: error: undefined reference to `QFeedbackHapticsEffect::setIntensity(double)'
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:43: error: undefined reference to `QFeedbackHapticsEffect::setDuration(int)'
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:44: error: undefined reference to `QFeedbackHapticsEffect::setActuator(QFeedbackActuator*)'
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:45: error: undefined reference to `QFeedbackEffect::start()'
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:46: error: undefined reference to `QFeedbackEffect::stop()'
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:46: error: undefined reference to `QFeedbackHapticsEffect::~QFeedbackHapticsEffect()'
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:46: error: undefined reference to `QFeedbackHapticsEffect::~QFeedbackHapticsEffect()'
it's not even at the linker yet....

szopin 2014-03-21 14:52
Re: Sailfish SDK Alpha 1312 Qt5 released
 
from twitter:
@locusf: Sailfish SDK Qt Creator sources are now online in: https://t.co/H0bqRKHQpD Might reveal a lot of interesting stuff.

Trying to build on device, qt5-qmake, qt5-qtconcurrent-devel and qt5-qtcore-devel all install fine. Qtgui and widgets sadly don't:

Code:
Fatal error: qt5-qtgui-devel-5.1.0+git31-1.12.8.armv7hl requires qt5-qtopengl-devel, but this requirement cannot be provided
qt5-qtwidgets-devel-5.1.0+git31-1.12.8.armv7hl requires pkgconfig(Qt5Gui), but this requirement cannot be provided
qtgui needs qtopengl that needs libEGL, the only similar pckg is mesa-llvmpipe-libEGL, but that conflicts with libhybris. Anyone has an idea how to get it to compile/working?

w00t 2014-03-21 18:59
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by szopin (Post 1417965)
qtgui needs qtopengl that needs libEGL, the only similar pckg is mesa-llvmpipe-libEGL, but that conflicts with libhybris. Anyone has an idea how to get it to compile/working?
Here be dragons.

As a whole stack, we build against Mesa's libEGL, but at runtime, we then pick a different - hardware-dependent libEGL implementation (which exactly depends on what hardware we're running on: on the Jolla, it's libhybris', on the N9 there's ti-omap3-sgx-wayland-wsegl's wrapper around the SGX drivers, etc). They're all - obviously - ABI/API compatible.

On the whole, I'd just recommend not building on device, because there is a way-too-easy chance you can wipe out your EGL libraries if you accidentally answer "yes" at the wrong prompt.

Why not use the SDK, out of interest?

szopin 2014-03-21 19:50
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by w00t (Post 1417999)
Here be dragons.

As a whole stack, we build against Mesa's libEGL, but at runtime, we then pick a different - hardware-dependent libEGL implementation (which exactly depends on what hardware we're running on: on the Jolla, it's libhybris', on the N9 there's ti-omap3-sgx-wayland-wsegl's wrapper around the SGX drivers, etc). They're all - obviously - ABI/API compatible.

On the whole, I'd just recommend not building on device, because there is a way-too-easy chance you can wipe out your EGL libraries if you accidentally answer "yes" at the wrong prompt.

Why not use the SDK, out of interest?
Couple of reasons. First is pleasure to have a fully fledged PC in your pocket (like when flashing one N900 with another, who needs desktop, right?). Second, most of my free-to-tinker time is on bus rides to/from work and similar. If I need a quick fix/modification I can perform it on the go instead of waiting 10h (if I get the idea on the morning ride) to see if it works. Not expecting to have a full build/deploy-to-harbour env on the phone, but for a quick recompile I hope we can make it work (especially now with HWKB OH)


edit: good news, at least tohkbd can be tweaked/tinkered with on the go, qmake generates Makefile correctly, make succeeds, no need for qtcreator

meShell 2014-03-21 20:05
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by w00t (Post 1417999)
Here be dragons.

As a whole stack, we build against Mesa's libEGL, but at runtime, we then pick a different - hardware-dependent libEGL implementation (which exactly depends on what hardware we're running on: on the Jolla, it's libhybris', on the N9 there's ti-omap3-sgx-wayland-wsegl's wrapper around the SGX drivers, etc). They're all - obviously - ABI/API compatible.

On the whole, I'd just recommend not building on device, because there is a way-too-easy chance you can wipe out your EGL libraries if you accidentally answer "yes" at the wrong prompt.

Why not use the SDK, out of interest?


Oh great, that is something that is a problem for me, too, may I jump in?

I wanted to use a QT-Plugin on the phone but have a similar problem, that qt-libs conflict with libhybris, don't know why it has to be conflicting at all?

w00t: "i'm a Qt expert and happy Jolla sailor." <-- perfect combination for my problem, too ? :)

Could you have a short view on this, if you see any posibillity to get it running?

Code:
qt5-qtplatformsupport-devel-5.1.0+git28-1.10.2.armv7hl requires pkgconfig(Qt5Gui), but this requirement cannot be provided
  uninstallable providers: qt5-qtgui-devel-5.1.0+git28-1.10.2.armv7hl[jolla]
 Solution 1: Following actions will be done:
  deinstallation of libhybris-sbj-0.0.0.33-10.8.1.jolla.armv7hl
  deinstallation of libhybris-sbj-libEGL-0.0.0.33-10.8.1.jolla.armv7hl
.....
.....
Full story here:

TMO t=92352&p=1406152

w00t 2014-03-21 20:47
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by szopin (Post 1418008)
Couple of reasons. First is pleasure to have a fully fledged PC in your pocket (like when flashing one N900 with another, who needs desktop, right?).
My recommendation would probably be to set up a chroot with a completely seperate package environment. You can then trash that one to install whatever you need (e.g. Mesa's EGL) and build happily in an environment kind of similar to the one the SDK uses.

szopin 2014-03-21 20:51
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by w00t (Post 1418012)
My recommendation would probably be to set up a chroot with a completely seperate package environment. You can then trash that one to install whatever you need (e.g. Mesa's EGL) and build happily in an environment kind of similar to the one the SDK uses.
Thanks, apparently Al13n started a thread on TJC, though there are some quirks: https://together.jolla.com/question/...building-apps/, hopefully we can get it to work

solbrit 2014-03-23 16:45
Re: Sailfish SDK Alpha 1312 Qt5 released
 
What's the difference between launching an app on the device from the SDK and launching it from the desktop file on the device?
I'm working on an app that gets output from at text file and edits it through Python (PyOtherSide) and when launched from the SDK (by copying binaries or deploying as RPM) it works as expected without any errors, but when I try to run it from the created desktop file nothing happens.

Edit:
Never mind, a reboot solved it. I thought reboots only updated the launcher icon displayed, but I guess it affects some other things too... :D

szopin 2014-03-23 22:40
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by solbrit (Post 1418200)
What's the difference between launching an app on the device from the SDK and launching it from the desktop file on the device?
I'm working on an app that gets output from at text file and edits it through Python (PyOtherSide) and when launched from the SDK (by copying binaries or deploying as RPM) it works as expected without any errors, but when I try to run it from the created desktop file nothing happens.
I think main diff is the SDK provides background libs (probably incorrect, but started working on porting Qgo (game client for the game of go), in order to see what is missing on the right hand side had to DL/setup standard QtCreator with VS and modify the source, result is: build/run -> working program with net connectivity and all, running the resulting binary outside of creator cries lack of Qtxxx.dll), expecting the same, though rpm should probably have the correct dependencies in place. Check what error msg is thrown when you exectute it on the phone from fingerterm

szopin 2014-03-31 20:30
Re: Sailfish SDK Alpha 1312 Qt5 released
 
It works!
http://i.imgur.com/Heobtmw.jpg

In case someone also wants to run Sailfish QtCreator on Jolla:

start with setting up chroot - https://together.jolla.com/question/...building-apps/
once it is setup install any libhybris breaking package into it (be sure to install it into the chroot!!! 'zypper --root /chroot/base install qt5-qtgui-devel' should do the trick), that will substitute hybris stuff with the llvmpipe libs

in chroot:

install all needed qt(-devel) libs (I did zypper install qt*-devel and it still missed some of the non-devel, thought they are dependent, apparently not, lrelease is in qt5-qttools-linguist)

git clone https://github.com/sailfish-sdk/sailfish-qtcreator

inside it 'qmake -r'

apply patch from here to botan.cpp/.h: https://bugreports.qt-project.org/br...REATORBUG-8107

go to src/plugins/imageviewer and modify Makefile adding -DQT_NO_SVG to defines

make

(few first runnings it was going going into 'not responding', with qthelp/qt5-qttools-qtdesigner qtpackages it finally loaded fine... well, like any pure qt app on Jolla fine is far from perfect, File/Edit etc dialogs pop up a new window that doesn't close gracefully, entry in text fields works after 2nd or third click and the SWKB is super-light/high-gamma... not sure how to describe, still, should be functional once it is setup to use libs from chroot for compiling (or maybe run from chroot? hmm... probably not as chroot has no libhybris, will need some tweaking))

Have fun!

rcolistete 2014-05-12 01:17
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Updated 1st post with Sailfish SDK release Alpha 1404, released in April 16th 2014.

rcolistete 2014-06-12 12:57
Re: Sailfish SDK Alpha 1404 Qt5 released
 
I've received email on SailfishDevel mailing list announcing Sailfish SDK Alpha 1406, to be released today (June 12th 2014), 13:00 UTC in Sailfish.org site :
Quote:
Juha Kallioinen juha.kallioinen at jolla.com
Thu Jun 12 06:59:30 UTC 2014

Previous message: [SailfishDevel] Lack of padding
Next message: [SailfishDevel] rpminstall signal packageStatusChanged
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello again,

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

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

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

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

A couple of things you should be aware of:
- As before, in this update the build engine, emulator and targets are
re-installed so you will lose all changes you may have made in those -
however, if your application packaging is done correctly, rebuilding
your projects should reinstall the packages you have been using.
- All customization done to SDK (adding new package repositories, adding
custom targets, additional source paths) will be removed during the
installation process so make your own backup of those before starting
the update.
- If you import existing projects made with a previous version of
theSailfish OS SDK, make sure toselect the correct kit in the project
configuration step. Both ARM and i486 kits are available.
- Windows users need to install VC10 runtime from
http://www.microsoft.com/en-us/downl...aspx?id=8328or the
Installer will ask for admin rights during installation.
- Package repository contents have been updated and consequently using a
previous SDK version with these package repositories is not supported.
- Supported host platforms can be found from:
https://sailfishos.org/alpha_qt5_sdk_release_notes.html
- For more information, please see the SDK Alpha-Qt5 known issues list
at: https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.

Here is the summary of changes:

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

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

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

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

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

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

Happy hacking,
Jolla SDK Team.

rcolistete 2014-07-14 15:59
Re: Sailfish SDK Alpha 1406 Qt5 released
 
Sailfish SDK Alpha-1407-Qt5 announced on SailfishDevel mailing list, to be released tomorrow (July 15th) at 12:00 UTC in Sailfish.org site :
Quote:
Hello again,

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

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

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

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

A couple of things you should be aware of:
- As before, in this update the build engine, emulator and targets are re-installed so you will lose all changes you may have made in those - however, if your application packaging is done correctly, rebuilding your projects should reinstall the packages you have been using.
- Any customization done to SDK (adding new package repositories, adding custom targets, additional source paths) will be removed during the installation process so make your own backup of those before starting the update.
- If you import existing projects made with a previous version of the Sailfish OS SDK, make sure to select the correct kit in the project configuration step. Both ARM and i486 kits are available.
- Windows users need to install VC10 runtime from http://www.microsoft.com/en-us/downl...n.aspx?id=8328 or the Installer will ask for admin rights during installation.
- Package repository contents have been updated and consequently using a previous SDK version with these package repositories is not supported.
- Supported host platforms can be found from https://sailfishos.org/alpha_qt5_sdk_release_notes.html
- For more information, please see the SDK Alpha-Qt5 known issues list at:https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.

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

SDK IDE (Qt Creator)
- Fix bugs related to handling symlinked home directory or project directory. This change affects only Linux and Mac hosts.
- Updated component gallery sources in the Example projects
- Updated Sailfish Silica help documentation

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

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

SDK Control Center:
- No updates

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

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

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

Happy hacking,
Jolla SDK Team.

rcolistete 2014-10-27 15:55
Re: Sailfish SDK Beta 1410 Qt5 released
 
Sailfish SDK Beta-1410-Qt5 (U9-Opt-in) announced on SailfishDevel mailing list :
Quote:
Hello again,

Today (October 27) at 13:00 UTC we have published new installers for the
first Beta version of the Sailfish OS SDK.

The installers for this opt-in release of the SDK are available at
http://www.sailfishos.org.

SDK content has been updated to match Jolla Release 1.1.0.38. As the
1.1.0.38 is an opt-in release, we decided to make this version of the
SDK available only as an active download. It means you will *not* get an
update notification of this SDK version. Please see below for detailed
information of the changes.

Important things you should be aware of:
- Most of our users still use the Jolla Release 1.0.8.21 (Update 8), so
please use this SDK release primarily to fix applications not working in
Update 9 and feature testing.
- Both versions of the SDK (1410 and 1407) cannot be installed as a same
user at the same time.
- Apps that are built using this SDK release will first be tested
against Update 8 in the Harbour. In case a test fails, they will be
separately checked against Update 9, which will cause a delay in the
approval process (~ 1 Week). If you have any questions, don't hesitate
to contact developer-care at jolla.com.
- Targets meant for this SDK release are marked with "1410/U9" in the
pre-configured targets list. These targets will not work with older SDK
releases.

A couple of other 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/beta_qt5_sdk_release_notes.html.

- For more information, please see the SDK Beta-Qt5 known issues list
at: https://sailfishos.org/wiki/SDK_Beta_Qt5_Known_Issues.

Upgrading Qt Creator to version 3 makes this release the first Beta
version of the SDK. Qt Creator 3 is the current live version of the
upstream Qt Creator and is thus a good platform for improving and
creating new features for the Sailfish OS SDK.

SDK IDE (Qt Creator)
- Qt Creator version updated to 3.1.2
- Fix several issues with starting and stopping the virtual machines
- Fix stopping GDB debugging session in Windows

SDK Build engine:
- Build targets refreshed to Jolla release 1.1.0.38 level.
- Qt version 5.2

Emulator:
- Emulator packages refreshed to Jolla release 1.1.0.38 level.
- Qt version 5.2

Jolla Together thread for discussion and other information:
https://together.jolla.com/question/...1410-released/.

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

Happy hacking,
Jolla SDK Team
See also the Release Notes of Sailfish SDK 1410.

juiceme 2014-10-27 16:51
Re: Sailfish SDK Alpha 1407 Qt5 released
 
Quote:
SDK content has been updated to match Jolla Release 1.1.0.38. As the
1.1.0.38 is an opt-in release, we decided to make this version of the
SDK available only as an active download. It means you will *not* get an
update notification of this SDK version. Please see below for detailed
information of the changes.
heh, no wonder I was hitting the reload button on SDK update manager with no success, it's an opt-in-option :D

rcolistete 2014-12-25 18:56
Re: Sailfish SDK Alpha 1407 Qt5 released
 
The new Sailfish SDK will be released in January 5th 2015 :
[Release notes] Software version 1.1.1.27, Vaarainjärvi.
Quote:
The corresponding SDK release will be available on the 5th of January 2015. It will include the updated rpmvalidator which allows the new libraries to be used in Store as announced in the community meeting from 25th of November 2014.
Harbour testing team will start using the new rpmvalidator from 7th of January 2015 onwards (note that 6th of January 2015 is a public holiday in Finland).
[SailfishDevel] Harbour & Jolla Developer Care delays during holiday season
Quote:
As mentioned in the release notes for Update 10[1], we will release the corresponding SDK on 5. Jan 2015 and Harbour testing will start using the new rpmvalidator allowing more libraries[2] 7. Jan 2015.

Lobster 2014-12-27 17:38
Re: Sailfish SDK Beta 1410 Qt5 released
 
Hi. I have got a question. I am trying to write app that uses poppler lib to render pdf documents. If I understand correctly, first I must install poppler at sailfish build engine to be able to compile my apps with poppler at arm platform. I opened SailfishOS->Targets->Sailfish-i486 and installed poppler, poppler-glib, poppler-qt5 and poppler-utils packets. However I don't understand where I can find those packets? I searched in /usr directory at build engine ("find /usr -name "*poppler*"") with no success. So where is those installed packets?

P.S. I am new at packet system and unix platform, so I am sorry for that may be silly question

rcolistete 2015-01-05 15:48
Re: Sailfish SDK Beta 1410 Qt5 released
 
Sailfish SDK Beta "1412" announced today on SailfishDevel mailing list, it is already available in Sailfish.org site :
Quote:
Hello again,

Today (January 5th) at 14:00 UTC we have published new installers and repositories of the Sailfish OS SDK.

The installers for this release of the SDK are available at http://www.sailfishos.org. If you have an older beta or alpha 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.1.26. 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/beta_qt5_sdk_release_notes.html
- For more information, please see the SDK Beta-Qt5 known issues list at: https://sailfishos.org/wiki/SDK_Beta_Qt5_Known_Issues.

SDK IDE (Qt Creator):
- Qt Creator version 3.1.2, which is the same as used in the October opt-in release
- Updated Sailfish Silica help documentation

SDK Build engine:
- Build targets refreshed to Jolla release 1.1.1.26 level
- Updated rpmvalidator, which allows the new libraries to be used in Store ( http://merproject.org/meetings/mer-m...-25-15.00.html )

Emulator:
- Emulator packages refreshed to Jolla release 1.1.1.26 level

Installer / SDK Control Center:
- Several bugfixes in the updated Installer Framework

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

Happy hacking,
Jolla SDK Team

rcolistete 2015-02-03 16:47
Re: Sailfish SDK Beta 1410 Qt5 released
 
So developers will have Sailfish OS updates before mainstream :
Quote:
[SailfishDevel] Early access to SailfishOS releases
Tue Feb 3 14:30:23 UTC 2015
https://lists.sailfishos.org/piperma...ry/005595.html
Hi all,

From now on we'll make updates available a short time before releasing
for developers, details at together:

https://together.jolla.com/question/...shos-releases/

This is a first step towards a developer program & early feedback
gathering.

Bernd

antviro 2015-11-13 09:12
Re: SDK Beta 1412 Qt5 released
 
I have a very newbie question about using merSDK.

I want to compile a compiler (ocalm) or something needed to compile another package. I did in the "traditional" way (make -> make install -> make clean). But then I realised that what I need is such compiler for the two different targets, so I should do it with mb2. I have never used mb2... what should i do? something like (for instance for the pc emulator i486):
mb2 -t SailfishOS-i486 build (or mb2 -t SailfishOS-i486 make?)
and then
mb2 -t SailfishOS-i486 install (or make install)
?

Is there any wiki or documentation that I can read about?

coderus 2015-11-13 09:17
Re: SDK Beta 1412 Qt5 released
 
sb2 to your different targets and make && make install here.

antviro 2015-11-13 09:21
Re: SDK Beta 1412 Qt5 released
 
Quote:
Originally Posted by coderus (Post 1488080)
sb2 to your different targets and make && make install here.
What a fast answer!!

You mean something like:
mb2 -t SailfishOS-i486 make
[everything was fine and then]
mb2 -t SailfishOS-i486 make install
Dont you?

Ive never used mb2 (and it has no man page at least in sdk)

antviro 2015-11-13 09:25
Re: SDK Beta 1412 Qt5 released
 
sb2 -t SailfishOS-i486

ah,, and then
make
make install


thanks for your response, before I read it too fast, and i didnt realized you meant sb2 and not mb2

coderus 2015-11-13 09:38
Re: SDK Beta 1412 Qt5 released
 
sb2 -t SailfishOS-armv7hl -m sdk-install -R
sb2 -t SailfishOS-i486 -m sdk-install -R

and seems you need to read this one: https://sailfishos.org/develop/tutor...ages-manually/


All times are GMT. The time now is 13:12.
Page 7 of 8 « First 56 7 8
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8