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
