[SailfishDevel] Sailfish OS SDK February update available now
Hello again, Today (March 3rd) 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 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.2.16 (Yliaavanlampi). 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 Sailfish Silica help documentation, default template and examples SDK Build engine: - Build targets refreshed to Jolla release 1.1.2.16 level Emulator: - Emulator packages refreshed to Jolla release 1.1.2.16 level Harbour/Rpmvalidator: - Note: Harbour Store QA will take the new rpmvalitator into use 04. March 2015. - New allowed libraries: - libsndfile - libbz2 - SDL2 with various modules see: https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/commit/d542eee0da4a0c2959fc6ed30073de984454af58 - be aware that applications using SDL_Renderer will not work yet, see: https://harbour.jolla.com/faq#9.4.0 - New check that vendor field in RPM is not set, see FAQs: https://harbour.jolla.com/faq#2.18.0 , https://harbour.jolla.com/faq#2.19.0 and https://harbour.jolla.com/faq#2.20.0 If you have any questions, feel free to either send an email to this mailing list: mailto:devel@lists.sailfishos.org, write it up in http://together.jolla.com and tag your issue with 'sdk' or send an e-mail to developer-c...@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] Harbour: Allow more libraries to link against
Hi, On 28.12.2013 18:56, Ruediger Gad wrote: Hi, thanks for the reply. It's good to know that this is the right channel and that you are listening. :) Unfortunately, I discovered two more libs some other apps I may try to port would rely on: - libsndfile libsndfile, is now allowed in Harbour. Rpmvalidator allowing it is part of SDK 1502: https://lists.sailfishos.org/pipermail/devel/2015-March/005771.html br Reto - qt5-qtconnectivity-qtbluetooth Those are the package names and not the actual library names but I hope that's sufficient. Both seem also to be available already for SailfishOS. libsndfile is even already installed on my Jolla by default. I don't want to sound demanding but I am really motivated to push apps to Harbour and those are the libs I would need to link against. Best regards, Ruediger PS: In some cases statically linking or shipping a lib with an app might solve the issue. However, it feels kind of wrong to do this when a lib is available anyhow. And there may be other cases in which you end up in a long dependency chain such that these workarounds are not practical. Furthermore, to me as a developer, adding such workarounds is an additional overhead and takes time I'd prefer to invest somewhere else, like actually improving an app or writing/porting a new one. Please do not mistake me, I don't want to sound rude but just want to explain my situation. PPS: As people start to develop more apps now (hopefully ;)), I assume that even more people will come up with requests for libs to link against. Would it make sense to have a more centralized place to discuss this or to collect requests? I mean to have a place for devs as well as for you to quickly see which libs had already been requested and to possible vote for libs. E.g., would it make sense to use together.jolla.com for this and maybe add a tag like #harbour-lib-request or something? On 12/27/2013 06:04 PM, Reto Zingg wrote: Hi, On 27.12.2013 18:48, Ruediger Gad wrote: I hope this is the right channel to address this request to. If not, please redirect me in the appropriate direction. for once a nice request and not just ranting :-) this is the right channel. We heard you and will look into it, but I can't promise any time frame when will finally decide whenever we will allow it or not. br Reto ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
