![]() |
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 ... |
All times are GMT. The time now is 11:42. |
vBulletin® Version 3.8.8