Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 2 days, 20 hrs ago -
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 4 days, 17 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 5 days, 14 hrs ago - more...
| The Following User Says Thank You to marmistrz For This Useful Post: | ||
|
2013-10-14
, 12:59
|
|
Posts: 1,067 |
Thanked: 2,383 times |
Joined on Jan 2012
@ Finland
|
#202
|
Originally Posted by marmistrz
Someone needs to keep the libraries up-to-date, so if your willing to update your favourite library few times a month for the next few years, then your welcomed to donate your time to mer-project.
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
Good libraries are always welcomed, the problem is to find active maintainers to all the libs.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.
__________________
IRC: jonni@freenode
Sailfish: ¤ Qt5 SailfishTouchExample ¤ Qt5 MultiPointTouchArea Example ¤ ipaddress ¤ stoken ¤ Sailbox (Dropbox client) ¤
Harmattan: ¤ Presence VNC for Harmattan ¤ Live-F1 ¤ BTinput-terminal ¤ BabyLock ¤ BabyLock Trial ¤ QML TextTV ¤
Disclaimer: all my posts in this forum are personal trolling and I never post in any official capacity on behalf of any company.
IRC: jonni@freenode
Sailfish: ¤ Qt5 SailfishTouchExample ¤ Qt5 MultiPointTouchArea Example ¤ ipaddress ¤ stoken ¤ Sailbox (Dropbox client) ¤
Harmattan: ¤ Presence VNC for Harmattan ¤ Live-F1 ¤ BTinput-terminal ¤ BabyLock ¤ BabyLock Trial ¤ QML TextTV ¤
Disclaimer: all my posts in this forum are personal trolling and I never post in any official capacity on behalf of any company.
| The Following 4 Users Say Thank You to rainisto For This Useful Post: | ||
 |
|
2013-10-14
, 13:31
|
|
Posts: 1,012 |
Thanked: 817 times |
Joined on Jul 2007
@ France
|
#203
|
Originally Posted by rcolistete
I'm a python dev, and i'm lazy .... I found that making cross plateform apps is easier with pyotherside (or at least a fork i made of an old version (but don't use it !))
But developers want and need freedom and options. Let remember that many Python mobile developers have only some hours per week or month to develop as a hobby, so if there are tools easier to migrate (from Maemo/MeeGo/PC) to Sailfish, they will want them. Some of the Python softwares could be developed in C/C++, but then it would take more developing time and some would not be finished at all.
And please, stop saying mobile Python developers are lazy. They contributed and will contribute with a lot of free and open source softwares for Maemo, MeeGo, Sailfish, etc.
But yes having also PyQt is a good things !
__________________
Benoît HERVIER, Khertan
KhtEditor - Sdist_Maemo - Khweeteur - PyPackager - KhtSimpleText - KhtNotes - KhtBMA - Wleux - and more ...
Benoît HERVIER, Khertan
KhtEditor - Sdist_Maemo - Khweeteur - PyPackager - KhtSimpleText - KhtNotes - KhtBMA - Wleux - and more ...
| The Following 4 Users Say Thank You to Khertan For This Useful Post: | ||
 |
|
2013-10-14
, 14:01
|
|
Posts: 513 |
Thanked: 651 times |
Joined on Feb 2011
@ Sweden
|
#204
|
Originally Posted by rainisto
Well, libs aren't updated that often, but you're right that they don't package themselves.
Someone needs to keep the libraries up-to-date, so if your willing to update your favourite library few times a month for the next few years, then your welcomed to donate your time to mer-project.
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.
And last time I checked Sailfish used gcc-4.6.x and glibc-2.15 which are pretty old ... but next time there's a major update to gcc/glibc it's common sense to rebuild every package of the distribution. But I'd wager most (if not all) package maintainers already know this.
__________________
But the WM7 "horse" has a blood lineage tracing back to donkeys such as WM6.5, 6.1, 6.0, 5.1 that was fully neglected for too many years and Microsoft did sweet F all to maintain it (still running on Pocket IE4/6!!).
But the WM7 "horse" has a blood lineage tracing back to donkeys such as WM6.5, 6.1, 6.0, 5.1 that was fully neglected for too many years and Microsoft did sweet F all to maintain it (still running on Pocket IE4/6!!).
|
|
2013-10-14
, 18:51
|
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#205
|
Originally Posted by xerxes2
You can't compare GCC on X86 with ARM GCC there is plenty of reasons to be carefully when upgrade those.
Well, libs aren't updated that often, but you're right that they don't package themselves.
And when they do all libs has to be recompiled and that is probadly not as easy as when done on a X86.
__________________
Keep safe and healthy
Keep safe and healthy
Last edited by mikecomputing; 2013-10-14 at 18:54.
|
|
2013-10-15
, 17:31
|
|
Posts: 1,548 |
Thanked: 7,510 times |
Joined on Apr 2010
@ Czech Republic
|
#206
|
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.
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.
__________________
modRana: a flexible GPS navigation system
Mieru: a flexible manga and comic book reader
Universal Components - a solution for native looking yet component set independent QML appliactions (QtQuick Controls 2 & Silica supported as backends)
modRana: a flexible GPS navigation system
Mieru: a flexible manga and comic book reader
Universal Components - a solution for native looking yet component set independent QML appliactions (QtQuick Controls 2 & Silica supported as backends)
| The Following 6 Users Say Thank You to MartinK For This Useful Post: | ||
|
|
2013-10-22
, 11:24
|
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#207
|
#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
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
__________________
Keep safe and healthy
Keep safe and healthy
| The Following 8 Users Say Thank You to mikecomputing For This Useful Post: | ||
|
|
2013-10-22
, 19:33
|
|
Posts: 513 |
Thanked: 651 times |
Joined on Feb 2011
@ Sweden
|
#208
|
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:
Last edited by xerxes2; 2013-10-22 at 20:29.
Edit:
Code:
zypper ar http://repo.merproject.org/obs/nemo:/devel:/apps/latest_i586/nemo:devel:apps.repo
__________________
But the WM7 "horse" has a blood lineage tracing back to donkeys such as WM6.5, 6.1, 6.0, 5.1 that was fully neglected for too many years and Microsoft did sweet F all to maintain it (still running on Pocket IE4/6!!).
But the WM7 "horse" has a blood lineage tracing back to donkeys such as WM6.5, 6.1, 6.0, 5.1 that was fully neglected for too many years and Microsoft did sweet F all to maintain it (still running on Pocket IE4/6!!).
Last edited by xerxes2; 2013-10-22 at 20:29.
|
|
2013-10-22
, 20:33
|
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#209
|
Originally Posted by xerxes2
yeah some wierdness in the X86 target qmsystem5 failed for me to install but when I installed qmsystem5-devel it seems to work..
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
also the emulator does not have sound anymore. Or maybe I forgot that I tweeked VM to get that too work last time hmm
__________________
Keep safe and healthy
Keep safe and healthy
|
|
2013-10-23
, 17:07
|
|
Posts: 513 |
Thanked: 651 times |
Joined on Feb 2011
@ Sweden
|
#210
|
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 ...
And damn the gui is slooooow for me. Is it possible to make it faster somehow. install some drivers or something ...
__________________
But the WM7 "horse" has a blood lineage tracing back to donkeys such as WM6.5, 6.1, 6.0, 5.1 that was fully neglected for too many years and Microsoft did sweet F all to maintain it (still running on Pocket IE4/6!!).
But the WM7 "horse" has a blood lineage tracing back to donkeys such as WM6.5, 6.1, 6.0, 5.1 that was fully neglected for too many years and Microsoft did sweet F all to maintain it (still running on Pocket IE4/6!!).
| The Following User Says Thank You to xerxes2 For This Useful Post: | ||
And you don't have out of date libs statically
If you want to support my work, you can donate by PayPal or Flattr
Projects no longer actively developed: here