This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Issue near end of KDEConnect install on Windows

Tags: None
(comma "," separated)
Barrage
Registered Member
Posts
3
Karma
0
Hello everyone,

I am new to this, but very excited to give KDEConnect a try.
I have been following the guide found at https://community.kde.org/KDEConnect/Build_Windows
I believe I have successfully followed the instructions up until I get to the section titled:
BUILDING KDE CONNECT OUT OF LATEST SOURCE CODE

When I open the Craft CraftRoot I automatically get an error as it loads:

Code: Select all
The expression after '&' in a pipeline element produced an object that was not
valid. It must result in a command name, a script block, or a CommandInfo
object.
At C:\CraftRoot\craft\craftenv.ps1:128 char:8
+     (& $env:CRAFT_PYTHON ([IO.PATH]::COMBINE("$env:CraftRoot", "bin",
"CraftSetu ...
+        ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : BadExpression

PS C:\CraftRoot>


and if I attempt to input the next line in the instructions, I get:

Code: Select all
PS C:\CraftRoot> craft --set version=master kdeconnect-kde
The expression after '&' in a pipeline element produced an object that was not
valid. It must result in a command name, a script block, or a CommandInfo
object.
At C:\CraftRoot\craft\craftenv.ps1:84 char:14
+     return & $env:CRAFT_PYTHON ([IO.PATH]::COMBINE("$env:CraftRoot", "bin",
"cra ...
+              ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : BadExpression

PS C:\CraftRoot>


Perhaps someone else has run into this issue and could shed some light on my situation?
I apologize for my newbness, but I will try to be as detailed as possible.
Thank you so much for your help.
Barrage
Registered Member
Posts
3
Karma
0
I seem to have resolved my own issue...thanks though!
For those who might encounter these errors in the future, they mean...
Go update PowerShell. And reboot. That is all. :)

It case it proves useful, I originally had a version 4 powershell. I went the update WMF method to update.
Barrage
Registered Member
Posts
3
Karma
0
Sounded good :P

Another issue emerges!

Image


Bookmarks



Who is online

Registered users: bartoloni, Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]