Re: [SailfishDevel] Qt Kits broken on Windows?
Hi Gabriel, sorry to hear about the problems. Although we are aware of problems with whitespace and special chars, there's no easy solution in sight. We'll have to put more effort into finding a solution for this problem. Unfortunately there's no file that points to the deploy command. It's hard coded in Qt Creator's code. To see the SailfishOS project, Qt Creator must have functional kits, otherwise it filters out the projects that it cannot build. Best regards, Juha On 19.04.2014 20:56, Gabriel Böhme wrote: Hi again, I could isolate the problem a bit, it seems that my user name is (again) a problem. In Windows 7 it was me, naming it to my full name, including special char (ö) and space, but Windows 8 did it itself by using my Microsoft account name. If I create a new user (just few chars) everything works as you would expect. For the real user (with issues) it is possible to change the paths to this new users ...AppData/Roaming/SailfishAlpha4... folder. Doing this, I get working compilers and kits, but can't deploy because I have not found the file (there seems to be no option) that points to the deploy.cmd file. Changing that could fix the issue. Also with the problematic user, I don't see/get the option for a SailfishOS project, as new project. Maybe this is easy to fix, I hope that will help! Thanks, Gabriel. Am 19.04.2014 00:48, schrieb Gabriel Böhme: Hi Sailors, I've switched to Win8.1 Pro and one of the first things to do was to install the latest SDK (fresh). ;) But now my Qt Kits shown as broken in the settings (red warning sign). In the next tab the QtVersions seems to be the problem, because it says that qmake can't be found or is not executable. But the qmake, make, deploy ... *.cmd files are there in AppData/Roaming where the path want's them. Any idea, hint, or known problem? Thanks, Gabriel. ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
[SailfishDevel] SDK 1404 and translations
Did I hit a bug with the newly added translations support?
This two lines in .pro (I just changed the lang code in standard .pro file
created by sialfishapp/qtquick app wizard) file:
CONFIG += sailfishapp_i18n
TRANSLATIONS += translations/harbour-yourproject-it.ts
produce the following error at buld time:
lrelease error: Cannot open
/home/mersdk/share/Projects/SailfishOS/harbour-yourproject/translations/harbour-yourproject-it.ts:
No such file or directory
Looking at sailfishapp_i18n.prf it seems it generates
harbour-yourproject.ts file only, not all the *.ts files specified in your
.pro file.
lupdate command is invoked as per directive:
update_translations.commands += mkdir -p translations lupdate
$${TRANSLATION_SOURCES} -ts $${TS_FILE}
where $${TS_FILE} is defined beforehand as follows:
TS_FILE = $${_PRO_FILE_PWD_}/translations/$${TARGET}.ts
Shouldn't it cycle through every file in $${TRANSLATIONS} instead and run
lupdate accordingly?
Something like this (beware: I'm in no way a cmake expert!!!):
for(ts_file, TRANSLATIONS) {
update_translations.commands += lupdate $${TRANSLATION_SOURCES} -ts
$$ts_file
}
Did I get something wrong or is it really a bug?
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] Qt Kits broken on Windows?
Hi Juha, first of all - thanks for your fast answer! Secondary: it's not a big problem in my case, cause my main system is Linux and there is everything working fine. Also creating another user in Windows, may not be perfect, but also not too much effort. ;) But maybe it could help, if you allow to change the deploy path. Or the path of the SailfishAlphaX folder itself. Because linking to the new user solved the problem with the Qt Kits, what means it's building the project, only deploy is not working. So the user (or the installer checks) could change it to pure C:\ or something else the user wants? Or is there something preventing this? Thanks again, Gabriel. Am Dienstag, den 22.04.2014, 10:12 +0300 schrieb Juha Kallioinen: Hi Gabriel, sorry to hear about the problems. Although we are aware of problems with whitespace and special chars, there's no easy solution in sight. We'll have to put more effort into finding a solution for this problem. Unfortunately there's no file that points to the deploy command. It's hard coded in Qt Creator's code. To see the SailfishOS project, Qt Creator must have functional kits, otherwise it filters out the projects that it cannot build. Best regards, Juha On 19.04.2014 20:56, Gabriel Böhme wrote: Hi again, I could isolate the problem a bit, it seems that my user name is (again) a problem. In Windows 7 it was me, naming it to my full name, including special char (ö) and space, but Windows 8 did it itself by using my Microsoft account name. If I create a new user (just few chars) everything works as you would expect. For the real user (with issues) it is possible to change the paths to this new users ...AppData/Roaming/SailfishAlpha4... folder. Doing this, I get working compilers and kits, but can't deploy because I have not found the file (there seems to be no option) that points to the deploy.cmd file. Changing that could fix the issue. Also with the problematic user, I don't see/get the option for a SailfishOS project, as new project. Maybe this is easy to fix, I hope that will help! Thanks, Gabriel. Am 19.04.2014 00:48, schrieb Gabriel Böhme: Hi Sailors, I've switched to Win8.1 Pro and one of the first things to do was to install the latest SDK (fresh). ;) But now my Qt Kits shown as broken in the settings (red warning sign). In the next tab the QtVersions seems to be the problem, because it says that qmake can't be found or is not executable. But the qmake, make, deploy ... *.cmd files are there in AppData/Roaming where the path want's them. Any idea, hint, or known problem? Thanks, Gabriel. ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list signature.asc Description: This is a digitally signed message part ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] SDK 1404 and translations
you should create translations/harbour-yourproject-it.ts yourself.
QtCreating not making translations for you, it just generates source
translation and compiling existing translations.
22.04.2014 19:47, Luca Donaggio ?:
Did I hit a bug with the newly added translations support?
This two lines in .pro (I just changed the lang code in standard .pro
file created by sialfishapp/qtquick app wizard) file:
CONFIG += sailfishapp_i18n
TRANSLATIONS += translations/harbour-yourproject-it.ts
produce the following error at buld time:
lrelease error: Cannot open
/home/mersdk/share/Projects/SailfishOS/harbour-yourproject/translations/harbour-yourproject-it.ts:
No such file or directory
Looking at sailfishapp_i18n.prf it seems it generates
harbour-yourproject.ts file only, not all the *.ts files specified in
your .pro file.
lupdate command is invoked as per directive:
update_translations.commands += mkdir -p translations lupdate
$${TRANSLATION_SOURCES} -ts $${TS_FILE}
where $${TS_FILE} is defined beforehand as follows:
TS_FILE = $${_PRO_FILE_PWD_}/translations/$${TARGET}.ts
Shouldn't it cycle through every file in $${TRANSLATIONS} instead and
run lupdate accordingly?
Something like this (beware: I'm in no way a cmake expert!!!):
for(ts_file, TRANSLATIONS) {
update_translations.commands += lupdate $${TRANSLATION_SOURCES} -ts
$$ts_file
}
Did I get something wrong or is it really a bug?
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] Weekly meeting about SailfishOS, open source, collaboration, way forward @ 22 April, 15:00 UTC
Reminder: meeting starts in 50 min! Also see statement below before meeting! On 04/20/2014 04:01 PM, Thomas B. Rücker wrote: I haven't seen a meeting invitation/announcement by Jolla yet, so I'm stepping in. My apologies if it was already sent and I missed it. The next meeting has been agreed for: 2014-04-22T15:00 UTC That's 17:00 CEST (most of Europe) and 18:00 EEST (easternmost parts of Europe, including Finland) Meeting duration: 90min It will take place on #mer-meeting of Freenode IRC. Those without an IRC client can access it here: http://webchat.freenode.net?channels=mer-meeting The already known topics are: - community open source package repository for sailfish apps I'd like to emphasize, that this is an important topic, it has been brought up as early as March 2013 (sic!) on this mailing list. Also given Jolla's claim to continue Maemo/MeeGo heritage carries such things implicitly. Maemo had extras, MeeGo had COBS and Harmattan had AppsForMeeGo. Up until when I wrote the invitation mail there was zero public statement from Jolla, the company, to people asking for such a repository. This has been brought up on Jolla's community interaction / co-creation platform: https://together.jolla.com/question/13605/visible-open-source-app-community-supported-by-jolla/ This was also discussed during the community round-table at FOSDEM, again no statement from Jolla the company had been made then. The offer stands for months now, we're in a holding pattern as people are not willing to commit countless hours of their private time towards something that Jolla maybe doesn't even want. This is essentially free work that would deliver significant value to Jolla's proposition. I urge Jolla, the company, to make a public commitment, during that meeting, to support the open source app community. David summarized the minimum viable way on the device on IRC: 1) Settings - Untrusted SW - tick Allow, tick Install Chum client. Done 2) Store - Chum client and select install - Untrusted SW - tick Allow. Done There are other aspects which will need to be agreed, but Jolla needs to indicate that it is willing to consider this and what needs to be done by the community for the mentioned above integration to be allowed. - closed bits of SailfishOS - why/where/how and relation to open source parts - plans on SailfishOS for Android The meeting chair will be Carol 'Cybette' Chen, Jolla Community Chief. Please familiarize yourself with the topics. Should you have agenda proposals or need for upfront discussion, please reply to this email on the mailing list. Logging and meeting management will be done through a MeetBot (MerBot). I'd recommend that everyone familiarizes themselves with the common commands the MeetBot understands: https://wiki.debian.org/MeetBot (Howto, commands for everyone) Previous meeting minutes and follow up discussion: https://lists.sailfishos.org/pipermail/devel/2014-April/003925.html Cheers Thomas a community member PS: We're _currently_ sticking with the 1500z slot and weekly on Tuesday. This should be brought up in a /separate/ discussion. The current time does not fit potential Australian participants very well. Cheers Thomas ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] SDK 1404 and translations
On 22.04.2014 16:47, Luca Donaggio wrote: Did I hit a bug with the newly added translations support? This two lines in .pro (I just changed the lang code in standard .pro file created by sialfishapp/qtquick app wizard) file: CONFIG += sailfishapp_i18n TRANSLATIONS += translations/harbour-yourproject-it.ts produce the following error at buld time: lrelease error: Cannot open /home/mersdk/share/Projects/SailfishOS/harbour-yourproject/translations/harbour-yourproject-it.ts: No such file or directory Looking at sailfishapp_i18n.prf it seems it generates harbour-yourproject.ts file only, not all the *.ts files specified in your .pro file. Did I get something wrong or is it really a bug? You did nothing wrong. It is a bug. The translation support was very lightly tested and could fail in a number of ways. This support was changed and fixed over the Easter weekend. If you want to try the changes and know what to do, you can replace the sailfishapp_18n.prf file in the sb2 targets with the latest from here: https://github.com/sailfish-sdk/libsailfishapp/blob/master/data/sailfishapp_i18n.prf Or as a workaround you can copy the existing .ts file to harbour-yourproject-it.ts in the project's translations folder. The changes will be released after the next device software release. Best regards, Juha ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Qt Kits broken on Windows?
On 22.04.2014 16:55, Gabriel Böhme wrote: Hi Juha, first of all - thanks for your fast answer! Secondary: it's not a big problem in my case, cause my main system is Linux and there is everything working fine. Also creating another user in Windows, may not be perfect, but also not too much effort. ;) But maybe it could help, if you allow to change the deploy path. Or the path of the SailfishAlphaX folder itself. Because linking to the new user solved the problem with the Qt Kits, what means it's building the project, only deploy is not working. So the user (or the installer checks) could change it to pure C:\ or something else the user wants? Or is there something preventing this? Hi, I'm able to reproduce the problem here on my test environment, so I can now try to fix it too :-) Changing the configuration folder path is not trivial. Only the SailfishAlphaX part can be changed easily (and that at compile time only), but the rest of the path is sort of part of Qt Creator's core code, which I don't want to touch. These config directories work for other programs just fine, so I'll just have to fix this one to work properly too. I've made a small change now to how the small cmd scripts set the path in Windows (use \ instead of / as path separator) and the remaining issue seems to be the character encoding of 'ö' and presumably other non-ascii chars. So, somewhere those chars are handled as Latin1 and elsewhere as UTF-8. After that's fixed, it should work just fine. Best regards, Juha ___ SailfishOS.org Devel mailing list
[SailfishDevel] [Minutes] SailfishOS community meeting: open source, collaboration, way forward. 22 April 2014, 15:00 UTC
Hi, Thanks to everyone who attended today's meeting and contributed to another great discussion. Details in the minutes/logs: Minutes: http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-04-22-15.00.html Minutes (text): http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-04-22-15.00.txt Log: http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-04-22-15.00.log.html Next meeting will be on 2014-04-29. I will send a separate email to discuss the timing and topics, and follow that with meeting invitation. Reply to this thread for follow-up discussion on this meeting's topics. Cheers, Carol -- Carol cybette Chen Community Chief @ Jolla http://jolla.com +358403502527 @ SMS,PSTN,WeChat cybette @ FreenodeIRC,Twitter,Weibo,LinkedIn,Skype ___ SailfishOS.org Devel mailing list
[SailfishDevel] Next weekly meeting on 29-Apr: SailfishOS, open source, collaboration and way forward
Hi again! Now let's nail down some specifics for the next meeting. We need at least these items: 1. Time slot to accommodate different members in the community 2. Topics to be discussed 3. Meeting Chair I've created a pirate pad: http://piratepad.net/SailfishOSSMeeting-20140429 You can add your suggestions to the pad, or reply to this email and I will add the details there. I'll lock down the meeting time by this Friday to send out meeting invites over the weekend so make sure you indicate your preferences by then. Thanks and look forward to the next meeting! Hope I can wear a hat then, and not be so tired from moving -- leading to typos/errors. Now I need to go find one of my Jollas in one of the 50 moving boxes (I thought I heard it beep...) Cheers, Carol. -- Carol cybette Chen Community Chief @ Jolla http://jolla.com +358403502527 @ SMS,PSTN,WeChat cybette @ FreenodeIRC,Twitter,Weibo,LinkedIn,Skype ___ SailfishOS.org Devel mailing list
