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 Gabriel, I just noticed that Qt Creator has a commandline option '-settingspath' that can be used to tell where it should save/load its settings from. If you set it to for example C:\SailfishOS\mysettings then Qt Creator will use that as its settings directory. This should avoid the problem with non-ascii chars. In principle we could use this as a default for all windows installations, which is something we'll have to consider. If you want to try this, you should add the -settingspath option to the SailfishOS IDE shortcut, which you use to launch the IDE. Fixing the non-ascii chars in the bat files is proving to be a bit more involved than I had hoped. Best regards, Juha ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Qt Kits broken on Windows?
Hi Juha, thanks again, I'll give it a try asap (just at work) and let you know the result. Thanks, Gabriel. 2014-04-23 10:16 GMT+02:00 Juha Kallioinen juha.kallioi...@jolla.com: 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 Gabriel, I just noticed that Qt Creator has a commandline option '-settingspath' that can be used to tell where it should save/load its settings from. If you set it to for example C:\SailfishOS\mysettings then Qt Creator will use that as its settings directory. This should avoid the problem with non-ascii chars. In principle we could use this as a default for all windows installations, which is something we'll have to consider. If you want to try this, you should add the -settingspath option to the SailfishOS IDE shortcut, which you use to launch the IDE. Fixing the non-ascii chars in the bat files is proving to be a bit more involved than I had hoped. Best regards, Juha ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Qt Kits broken on Windows?
Hi Juha, great news - it's working perfectly. Also all Kit, Compiler paths are set correctly by default. :) And now - as you said - SailfishOS project is also shown in the settings. Thank you very much for this great hint! Gabriel. Am 23.04.2014 10:16, schrieb Juha Kallioinen: 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 Gabriel, I just noticed that Qt Creator has a commandline option '-settingspath' that can be used to tell where it should save/load its settings from. If you set it to for example C:\SailfishOS\mysettings then Qt Creator will use that as its settings directory. This should avoid the problem with non-ascii chars. In principle we could use this as a default for all windows installations, which is something we'll have to consider. If you want to try this, you should add the -settingspath option to the SailfishOS IDE shortcut, which you use to launch the IDE. Fixing the non-ascii chars in the bat files is proving to be a bit more involved than I had hoped. Best regards, Juha ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Qt Kits broken on Windows?
Oh what I forgot: some additional information, if you want a shortcut on the Windows 8 App Menu with the changed command line option, just create a shortcut on your normal desktop, add the command line option and name the shortcut to your prefered name. Now right click and select the show at start option and delete the shortcut on the normal Desktop. :) Gabriel. Am 23.04.2014 21:45, schrieb Gabriel Böhme: Hi Juha, great news - it's working perfectly. Also all Kit, Compiler paths are set correctly by default. :) And now - as you said - SailfishOS project is also shown in the settings. Thank you very much for this great hint! Gabriel. Am 23.04.2014 10:16, schrieb Juha Kallioinen: 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 Gabriel, I just noticed that Qt Creator has a commandline option '-settingspath' that can be used to tell where it should save/load its settings from. If you set it to for example C:\SailfishOS\mysettings then Qt Creator will use that as its settings directory. This should avoid the problem with non-ascii chars. In principle we could use this as a default for all windows installations, which is something we'll have to consider. If you want to try this, you should add the -settingspath option to the SailfishOS IDE shortcut, which you use to launch the IDE. Fixing the non-ascii chars in the bat files is proving to be a bit more involved than I had hoped. Best regards, Juha ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
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
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] 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
Re: [SailfishDevel] Qt Kits broken on Windows?
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
[SailfishDevel] Qt Kits broken on Windows?
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
