asked 2020-01-03 23:14:27 +0200
Running 'sfdk check' on windows 10 (whether under cmd or powershell) results in weird encoding issues like:
[32mPASSED[0m
Also you can only 'sfdk check' a file in the same directory that is registered as the projects directory, if you try to point it to .\build... it will say file not found, you have to manually copy the file into the dir for it to work
answered 2020-01-08 11:43:08 +0200
sfdk is of limited use under Windows CMD/PowerShell. Prefer using Git Bash instead.
Git Bash comes with Git, which you installed as a prerequisite of Sailfish SDK - check All Programs > Git > Git Bash under Start menu.
Should you need to use sfdk under CMD/PowerShell for some reason, local paths need to use forward slashes: sfdk check ./build/RPMS/foo-1-0.i486.rpm works while sfdk check .\build\RPMS\foo-1-0.i486.rpm doesn't.
wow thanks, wasn't aware git came with its own mingw, pretty cool (and thanks for cleaning the question up, was just a low effort quick report of cosmetic issues I noticed playing with the new tool as building/checking from sdk worked fine, so was mostly just to put it out there)
szopin ( 2020-01-08 17:22:53 +0200 )editAsked: 2020-01-03 23:14:27 +0200
Seen: 169 times
Last updated: Jan 08 '20
The weird encoding is actually called ANSI escape sequences and is interpreted by "proper" terminals. I'd even expect Windows Terminal (Preview) to handle this correctly. As @martyone answered below, CMD.exe or a plain PowerShell window won't work too well.
Maus ( 2020-01-08 21:49:26 +0200 )edit