![]() |
Re: Sailfish SDK Alpha Qt5 released
What's wrong with having lots of libraries in the repos: it doesn't have any downsides - size.dynamic <= size.static
And you don't have out of date libs statically |
Re: Sailfish SDK Alpha Qt5 released
Quote:
If there are thousands of outdated libraries that doesn't compile anymore, for example when gcc toolchain or glibc updates, then you are easily in a mess. |
Re: Sailfish SDK Alpha Qt5 released
Quote:
But yes having also PyQt is a good things ! |
Re: Sailfish SDK Alpha Qt5 released
Quote:
|
Re: Sailfish SDK Alpha Qt5 released
Quote:
And when they do all libs has to be recompiled and that is probadly not as easy as when done on a X86. |
Re: Sailfish SDK Alpha Qt5 released
Regarding the rebuilding of libraries, Sailfish is based on Mer, which uses the Open Build Service to build everything.
OBS makes re/building stuff for multiple architectures very easy once you have all the targets, builders and related infrastructure setup. You basically just upload a new source tarball & a spec file and the package and all packages depending on it are automatically rebuilt. It also supports personal side subprojects and sending packages between project with a review step. Sou you can for example configure your own subproject against the Mer core repo, make sure your library builds fine on all the Mer architecture target and then send submit the package for review. So while ARM indeed is currently more prone for exotic build failures, the rebuilding logistics itself should not be an issue for Sailfish due to OBS. PS.: I kinda expect that once a Sailfish device is publicly released that either a public Sailfish OBS shows up or a Sailfish target will be added to the Mer OBS. Like the Harmattan target on the late COBS. |
Re: Sailfish SDK Alpha Qt5 released
#SailfishOS SDK upgrade comming Today 13.00 UTC
from mailinglist: Hello again, Today 13:00 UTC we will publish new installers and repositories for our SailfishOS SDK, Alpha-Qt5-update2 to be exact. If you have Alpha-Qt5 you should see updates available icon in Qt Creator. If you don't have SailfishOS SDK installed, you can get the latest installers from www.sailfishos.org. This update is a major step before the launch of the Jolla device as it brings ARM package building to developers. A couple of things you should be aware of: - In this update the build engine, emulator and targets are re-installed so you will lose any 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 customizations done to SDK (adding new zypper repositories, adding custom targets, additional source paths) will be removed during installation process so make your own backup of those before starting the update. - If you import existing project made with a previous version of the SailfishOS SDK, make sure you select the correct kit in project configuration step. Both ARM and i486 kits will now be available. - Windows users need to install VC10 runtime from http://www.microsoft.com/en-us/downl...n.aspx?id=8328 or Installer will ask for admin rights during installation. - For more information, please see SDK Alpha-Qt5 known issues list at: https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues Update itself is performed like the previous one using SDK Maintenance tool with three following steps: 1. maintenance tool itself is updated first. In SailfishOS SDK IDE click on help->start updater->next->next->Update 2. maintenance tool needs to restarted to update the rest of the SDK, click Restart on the UI. 3. once updater has restarted, it asks for the next action, just click Next to proceed ('Update components' is selected by default). Updater lists all the items that are being updated, click Next->Update to proceed. Here's the release note for this update: SailfishOS SDK IDE: * Qt Creator updated to 2.8.1 version. * Building RPM packages for ARM target is introduced. This is done by selecting ARM kit and running deployment. Deployment to real ARM devices is not supported yet. * MerSDK VM starts without UI (if MerSDK is to be accessed, UI can be activated from tools->options->mer menu) * If MerSDK VM is running when Qt Creator is shut down - a prompt is displayed to close it. * QML profiling is enabled. Templates/examples: * SailfishOS application template is updated. The current template does not have so-called boilerplate and is easier to use. * SailfishOS application examples are updated to build with the latest template. SDK Maintenance Tool: * Whole installer framework is based on version 1.4. * bug fixes, no new functionality. Documentation: * Documentations are updated with latest available versions. Build Engine: * Support for ARM target introduced * Support to deploy to emulator using PackageKit * Lots of fixes to build toolchain. SailfishOS Emulator: * Emulator is built from updated Jolla baseline. * QML profiling support introduced. * Bug in QML debugging fixed. * Emulator screen size matches the upcoming Jolla phone. * Application icon texts are displayed when application grid is pushed up. SailfishOS Target(s): * ARM target introduced. * Both i486 and ARM target builds done on updated Jolla baseline. If you encounter any issues, please report them to Sailfish developers mailing list at devel@lists.sailfishos.org Happy hacking! Best regards, Jolla Sailfish SDK Team _______________________________________________ SailfishOS.org Devel mailing list |
Re: Sailfish SDK Alpha Qt5 released
Yeah it's a nice update, but didn't some repo disappear in the process? I had wget before without much ado but now I had to hunt it down in some nemo devel repo. Other than that it seems to work just fine.
Edit: Code:
zypper ar http://repo.merproject.org/obs/nemo:/devel:/apps/latest_i586/nemo:devel:apps.repo |
Re: Sailfish SDK Alpha Qt5 released
Quote:
also the emulator does not have sound anymore. Or maybe I forgot that I tweeked VM to get that too work last time hmm |
Re: Sailfish SDK Alpha Qt5 released
Your sound problem could be because you're not using pulseaudio! Try to switch to alsa instead, it's a switch in vbox.
And damn the gui is slooooow for me. Is it possible to make it faster somehow. install some drivers or something ... |
Re: Sailfish SDK Alpha Qt5 released
Quote:
|
Re: Sailfish SDK Alpha Qt5 released
Was someone impatient and put it on their sony device here?
http://forum.xda-developers.com/show....php?t=2389240 |
Re: Sailfish SDK Alpha Qt5 released
Quote:
Code:
gst-launch-0.10 playbin uri='file:///home/nemo/Music/song.mp3' |
Re: Sailfish SDK Alpha Qt5 released
Quote:
BUT just realized could be my kubuntu dist upgrade done last week that had ****ed up the soundsystem to not work with VM as before hmm... EDIT tested below: gst-launch-0.10 playbin uri='file:///usr/share/sounds/jolla-ambient/stereo/pulldown_highlight.wav' and that worked hmm |
Re: Sailfish SDK Alpha Qt5 released
Try to switch to alsa in vbox, settings -> Audio.
|
Re: Sailfish SDK Alpha Qt5 released
Quote:
(if you did see my post before edit I first got an error with gst-launch but that was because I was stupid and run gst-launch as root) |
Re: Sailfish SDK Alpha Qt5 released
But now that you're mentioning it, the UX sounds seems to have disappeared ...
|
Re: Sailfish SDK Alpha Qt5 released
Quote:
If that works and looks reasonable, then you're probably looking at something being funky with pulseaudio or something fun. The involved codepath is the libcanberra-using plugin of ngfd: https://github.com/nemomobile/ngfd/b...berra/plugin.c |
Re: Sailfish SDK Alpha Qt5 released
Quote:
[nemo@SailfishEmul ~]$ killall -sUSR1 ngfd ngfd: no process found [nemo@SailfishEmul ~]$ ngfd -v test file open: No such file or directory [0.058] ERROR: ffmemless: Could not find a device file [0.061] ERROR: core: sink 'ffmemless' failed to initialize |
Re: Sailfish SDK Alpha Qt5 released
Its a known issue that ui sounds are not working in current sdk release. Will be hopefully fixed on next release.
|
Re: Sailfish SDK Alpha Qt5 released
Quote:
You could always try build it yourself, for fun: https://github.com/nemomobile/ngfd/c...a980a1f007aba5 should be the fix for this... |
Re: Sailfish SDK Alpha Qt5 released
And just noticed that they've added a proper os-release too: :)
Code:
[nemo@SailfishEmul ~]$ cat /etc/os-release |
Re: Sailfish SDK Alpha Qt5 released
SailfishOS SDK December update available today.
Quote:
|
Re: Sailfish SDK Alpha Qt5 released
Downloading Sailfish SDK Alpha-1312-Qt5 :cool: ... done.
Read the SDK Alpha Qt5 Known Issues about some changes. I've updated the 1st post with new features of Sailfish SDK Alpha-1312-Qt5 : need to set the password in Settings, no pre-installed gcc and zypper, use of pkcon, etc. |
Re: Sailfish SDK Alpha Qt5 released
Backup of 1st post from 2013-08-26, useful to compare the differences between the Sailfish SDK versions.
Sailfish SDK releases : - Alpha (Qt4 & X11) in February 25th 2013 (for Linux), then updated in April 5th 2013 with Windows and Mac OS, see the release notes; - Alpha (Qt5 & Wayland) August 1st 2013, see Develop section of the Sailfish.org site to download, how to install, etc. This topic is intended to discuss Sailfish SDK installation and use. Sailfish SDK Alpha Qt5 release notes : "SailfishOS SDK is a collection of tools for developing SailfishOS applications. It includes: - QtCreator integrated development environment (IDE) - Mer build engine for cross compilation - The SailfishOS Emulator - Tutorial, Design and API Documentation - Repositories for additional libraries and open source code This release provides the following programming interfaces : - Sailfish Silica Qt Quick components 1.0 - Standard Qt Quick2 components" Tips & Hints & Info : ================ 1) "Why is the emulator showing a black screen?" Type "<host-key> + H" (host key is "Right Ctrl" by default) in Sailfish Emulator. 2) How do I login into the Sailfish Emulator or Mer SDK ? Start the Emulator and/or Mer-SDK from the SailfishOS IDE, i.e., select a project, then click in "Start SDK" and/or "Start Emulator". Then, to connect to Emulator from your host Linux : $ ssh -p 2223 nemo@localhost with password "nemo". You can uso "sudo" to run root commands like "zypper in <package-name>". Or by pressing "<host-key> + F2" (host key is "Right Ctrl" by default) in Sailfish Emulator you get a terminal login. Password for nemo user is "nemo", but you can also login as root with no password. "<host-key> + F1" comes back to the Saifish Emulator GUI. To connect to Mer-SDK from your host Linux : $ ssh -p 2222 -i ~/SailfishOS/vmshare/ssh/private_keys/engine/mersdk mersdk@localhost or, as root: $ ssh -p 2222 -i ~/SailfishOS/vmshare/ssh/private_keys/engine/root root@localhost Or by pressing "<host-key> + F2" (host key is "Right Ctrl" by default) in Mer SDK you get a terminal login, the root login has no password. "<host-key> + F1" comes back to the Mer SDK initial screen. 3) How do I copy files between host PC and Sailfish SDK Emulator ? The host PC folder "~/SailfishOS/vmshare/" is shared to "/etc/mersdk/share/" in Sailfish Emulator as read-only. So you can copy files and folders from PC to Sailfish Emulator. Be careful to not delete the folder "ssh" and file "devices.xml". From Sailfish Emulator to PC, you can use scp, e.g., "scp -P 2223 nemo@localhost:filename .". 4) What are versions of the Linux kernel, Qt, gcc and Python ? Linux kernel 3.6.11, Qt 5.0.2, gcc 4.6.4 and Python 2.7.3. 5) Useful softwares to install in Sailfish Emulator ? nano, htop, fingerterm : [nemo@SailfishEmul ~]$ sudo zypper in nano htop fingerterm 6) Python development : Python 2.7.3 is already installed. Additional python packages for development : # zypper in python-devel python-setuptools 7) Qt Creator SailfishOS Mode blank window : For some users (including me), the SailfishOS Mode (in left vertical bar of Qt Creator) shows a blank window ("about:blank"). The solution is to type "127.0.0.1:8080" and "<Enter>". 8) Repository list of Sailfish Emulator : In "/etc/zypp/repos.d/" : ssu_adaptation0_release.repo, ssu_jolla_release.repo, ssu_mer-tools_release.repo, ssu_adaptation1_release.repo, ssu_mer-core_release.repo 9) Packages in repositories : There are about 3,400 packages listed in the Sailfish OS repositories. About Python : approx. 90 packages; Qt5 : 800 packages; Wayland : 50 packages; X11 : 80 packages. New features of Sailfish SDK Alpha Qt5 : ================================ - it uses Qt 5.0.2 (almost 5.1) instead of Qt 4.8; - Wayland is used instead of X11 graphical server; - there is no standard Qt Quick components 1.1 (used in MeeGo Harmattan) package; - there is no PySide (Qt 4.8 bindings for Python), as it is not yet ported to Qt5, see the "Python & Qt5 on Sailfish" topic; - so it is now harder to migrate from MeeGo Harmattan to Sailfish, C/C++ developers need to port your Qt 4/Qt Quick 1/Qt Quick components softwares to Qt 5/Qt Quick 2/Silica components. Python developers don't have PySide at all, until now there is only one solution, PyOtherSide, see the "Python & Qt5 on Sailfish" topic; - Sailfish Emulator has no native terminal (there is fingerterm but it has screen size problems). Requested features : ================ Some are already know by Jolla : 1) landscape mode in Sailfish Emulator; 2) Sailfish Emulator more populated with softwares, like web browser (needed to test web interfaces, etc), native Terminal, file manager, etc; 3) Qt Creator capable of creating .rpm packages; 4) repository and Jolla store to place Sailfish especific softwares (using Silica components, etc). |
Re: Sailfish SDK Alpha 1312 Qt5 released
I'm curious as to why the the SDK is still considered to be "Alpha" despite the fact the Jolla device is now available. What else do they plan to chop and change? Is the Silica API considered to be stable?
|
Re: Sailfish SDK Alpha 1312 Qt5 released
Quote:
Can anybody suggest the best linux distro companion for Jolla/Sailfish? (one that would use zypper/pkcon, so desktop experience would be as similar as possible to mobile, like debian/ubuntu with maemo) IIRC OpenSuse used rpms, though haven't used it too long, might be mistaken (still hoping for a HWKB OH and being able to just move files from one to the other and continue tinkering on the bus to work). Qt Creator did work on N900, with more ram/dual core this should be possible with not so outrageous compile times |
Re: Sailfish SDK Alpha 1312 Qt5 released
Quote:
|
Re: Sailfish SDK Alpha 1312 Qt5 released
Latest ugrade failed for me again, because of the VirtualBox issues, so I had to install from scratch.
Dunno if its related to that I had installed my SDK in non standard dir /opt/SailfishOS instead of /home/$USER/SailfishOS |
Re: Sailfish SDK Alpha 1312 Qt5 released
Just sharing my happy experience with Sailfish on Nokia N9. It is a good complement to Sailfish SDK & emulator because it has a more complete Sailfish (with web browser, real ARM CPU, etc) to test softwares. See the Sailfish Wiki on Maemo.org and the "Porting Sailfish to N9 (or other)" TMO topic.
In my case, I've used a Nokia N9 with open mode kernel, followed the Sailfish Wiki (steps 3, 5, 5, 6 and 7), used vgrade-r3 Sailfish image, enabled Jolla Store using ssu.ini from czdosi, set the date in terminal and shared the Harmattan MyDocs with Sailfish. |
Sailfish devs knows why SDK is Alpha. Mostly related to API restrictions for Harbour. When everything good will be whitelisted SDK will get Beta and then Final :)
|
Re: Sailfish SDK Alpha 1312 Qt5 released
Quote:
I personally need a NFC API. Also python/pyotherside should be supported. |
Re: Sailfish SDK Alpha 1312 Qt5 released
Very useful and complete guide (121 pages in PDF !) from Sven Putze :
Developing with SailfishOS - a short introduction. It was announced in the SailfishDevel list, which I also recommend to follow for anyone interested in developing for Sailfish. |
Re: Sailfish SDK Alpha 1312 Qt5 released
In the faq it says that you should log in as user mersdk but the sb2 arm target has no user/group called mersdk. Is this a bug or feature?
Edit: Which means that rpm is complaining about wrong user/group so I have to add them manually on every friggin sdk update. |
Re: Sailfish SDK Alpha 1312 Qt5 released
Quote:
|
Re: Sailfish SDK Alpha 1312 Qt5 released
I don't log in to the arm target. Is that even possible? No I log in to the sdk as user "mersdk" as it says in the faq and then i build rpm packages using the sb2 command. And rpm complains about wrong user/group because user mersdk is missing in the arm target.
|
Re: Sailfish SDK Alpha 1312 Qt5 released
Quote:
i write this on jolla so may remember wrong about -t maybe -T anyway mb is the way for most usercases. |
Re: Sailfish SDK Alpha 1312 Qt5 released
Okay, getting desperate here. Trying to run the SDK on Debian Wheezy. Hitting the "Start Sdk"-button will always give "MerSDK: Timeout waiting for reply from server" though so I get nowhere. I've been looking around at different tutorials and guides but nothing has gotten me anywhere so far.
This was aaall so easy on Harmattan... |
Re: Sailfish SDK Alpha 1312 Qt5 released
I think we've missed this one sorry. Can you elaborate a little bit more? Where exactly do you try to start the SDK? From Virtualbox? I haven't tried the sdk with wheezy but I think it should work without a hitch. Try to install vbox before you install the sdk and then try to start vbox and run the MerSDK image from there.
|
Re: Sailfish SDK Alpha 1312 Qt5 released
Downloaded the SDK to give it a go. While not a dev, I know my ./configure make make install. I anticipated this will be different due to VMs and cross compiling, but I've been scratching my head for two days now, and it's going nowhere... Whenever I try building a project, the compiler just spits out
Code:
Invalid mapping mode: sdk-buildEDIT: Well d'oh and facepalm. Just found out I had a separate copy of scratchbox installed which used the same .scratchbox2 config directory. Removed all remnants of it (including $PATH), reinstalled the SDK and projects started building... |
| All times are GMT. The time now is 13:12. |
vBulletin® Version 3.8.8