Bug 386757

Summary: Python error with craftenv.ps1
Product: [Unmaintained] Craft Reporter: uwestoehr <uwestoehr>
Component: CoreAssignee: Hannah von Reth <vonreth>
Status: RESOLVED FIXED    
Severity: normal CC: windows-bugs-null
Priority: NOR    
Version First Reported In: stable   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description uwestoehr 2017-11-11 18:36:16 UTC 
I installed the latest craft following these guidelines:
https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Windows

At first there is a bug in the desription because
craftenv.ps1
is not under
C:\KDEROOT\craft\
but under
C:\CraftRoot\craft

I use CMake 3.9.5, Python 3.6.3, Qt 5.9.2 and ECM 5.39.0

I run now a powershell and entered

C:\CraftRoot\craft\craftenv.ps1

then I get a Python error:

python.exe : Craft Root          : C:\CraftRoot
At C:\CraftRoot\craft\craftenv.ps1:80 char:2
+ (& $env:CRAFT_PYTHON ([IO.PATH]::COMBINE("$env:CraftRoot", "bin", "Cr ...
+  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Craft Root          : C:\CraftRoot 
   :String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
 
Craft               : R:\
Version             : master
ABI                 : windows-msvc2015_64-cl
Svn directory       : C:\CraftRoot\download\svn
Git directory       : Q:\
Download directory  : C:\CraftRoot\download

In my CraftSettings.ini I read
Python = C:\Program Files (x86)\Python36-32
so Python was correctly detected.
Comment 1 uwestoehr 2017-11-12 00:22:35 UTC 
Hmm, I again set up craft now from scratch and now trhe problem is gone. It might be that I received the problem because following
https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Windows
I used
kdeenv.ps1 then I got a deprecation warning and switched to craftenv.ps1.
https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Windows
was fixed in this respect already, so onec the wrong KDEROOT path is there replaced with Craftroot I think this bug can be closed.