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
