Guidelines and HOWTOs/Build from source/Windows: Difference between revisions

From KDE Community Wiki
(→‎Installing Craft: added links to people new to powershell, mentioned 'as admin' (failed for me otherwise), formatted numbered list with subitems, fixed spelling, replaced unreadable character with space.)
(8 intermediate revisions by 3 users not shown)
Line 12: Line 12:


[https://www.microsoft.com/en-us/download/details.aspx?id=50395 Download Powershell]
[https://www.microsoft.com/en-us/download/details.aspx?id=50395 Download Powershell]
or
[https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powershell-core-on-windows?view=powershell-5.1 Download Powershell Core]


=== Setting up a compiler ===
=== Setting up a compiler ===
Line 21: Line 23:


=== Installing Craft===
=== Installing Craft===
* Start a powershell environment.
# [https://docs.microsoft.com/en-us/powershell/scripting/setup/starting-windows-powershell?view=powershell-6 Start a PowerShell environment]. It might be required to run it [https://docs.microsoft.com/en-us/powershell/scripting/setup/starting-windows-powershell?view=powershell-6#with-administrative-privileges-run-as-administrator as administrator].
* Allow execution of powershell scripts.
# Allow execution of powershell scripts by executing the following command:
  Set-ExecutionPolicy -Scope CurrentUser RemoteSigned
#:<pre>Set-ExecutionPolicy -Scope CurrentUser RemoteSigned</pre>
* Install Craft and folow the instructions
# Install Craft and follow the instructions by executing the following command:
iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/KDE/craft/master/setup/install_craft.ps1'))
#: <pre>iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/KDE/craft/master/setup/install_craft.ps1'))</pre>
# Consider adding exception for the entire craft root directory to your antivirus' exceptions, otherwise build of some packages can fail (example: build of <code>frameworks/tier2/kdoctools</code> when AVG is used).
 
=== Using the stock Qt SDK===
This will skip all Qt packages and use the official Qt builds instead.
It will work fine for most CMake based recipes but definitely cause problems with QMake based projects.
You will of course also miss all patches we usually apply to Qt.
This is only recommended when you know what you are doing and you won't get support for in our channel.
 
To activate the SDK mode adapt the [QtSDK] section in your etc/kdesettings.ini to something like:
    [QtSDK]
    ## Whether to use prebuild Qt binaries.
    Enabled = True
    ## The path to the Qt sdk.
    Path = C:\Qt
    ## The version of Qt.
    Version = 5.9
    ## The compiler version, if you are not sure what to use, have a look at the directory set in QtSDK/Path.
    ## The compiler must be of the same type as General/KDECOMPILER.
    ## If you are using mingw please make sure you have installed the mingw using the Qt installer.
    Compiler = msvc2017_64


== Using Craft ==
== Using Craft ==
To use Craft you need to start a Powershell window, point that to <tt>KDEROOT\craft </tt> and run the initalization script. For example:
To use Craft you need to start a Powershell window, point that to <tt>KDEROOT\craft </tt> and run the initalization script. For example:


  C:\KDEROOT\craft\craftenv.ps1
  C:\CraftRoot\craft\craftenv.ps1


This tells Craft about your environment settings (e.g. paths). It will load your configuration from <tt>KDEROOT\etc\kdesettings.ini</tt>. If there are any error messages Craft will not work as expected. The output should look similar to this one (of course with your paths):
This tells Craft about your environment settings (e.g. paths). It will load your configuration from <tt>CraftRoot\etc\CraftSettings.ini</tt>. If there are any error messages Craft will not work as expected. The output should look similar to this one (of course with your paths):


  PS C:\kderoot\craft>.\craftenv.ps1
  PS C:\CraftRoot\craft>.\craftenv.ps1
  Craft Root          : C:\CraftRoot
  Craft Root          : C:\CraftRoot
  Craft              : R:\
  Craft              : R:\
Line 42: Line 64:
  Git directory      : Q:\
  Git directory      : Q:\
  Download directory  : C:\CraftRoot\download
  Download directory  : C:\CraftRoot\download
==Using Craft with Qt Creator==
To compile from within Qt Creator, I need to set up a kit.
This is an example for mingw64.
* Add a cmake if none is set: R:\dev-utils\cmake\bin\cmake.exe
* Add a debugger: R:\mingw64\bin\gdb.exe
* Add a C++ compiler and a C compiler. Both: R:\mingw64\bin\gcc.exe
** Ensure that the ABI is correctly set
* Add a Qt: R:\bin\qmake.exe
* Add a kit with all of the above
* Use the kit on a project

Revision as of 16:40, 3 May 2018

Craft is a tool to build the sources and its third-party requirements. It is the easy way to build software.

Setting up craft

Installing python

While Craft is capable of installing a embedded Python version sufficient for most packages, we recommend a full installation of Python. The current version is 3.6. Download Python 3.6+

Setting up a powershell

Powershell is required to be at least version 5.0. If you're running Windows 10 you most probably won't need to update Powershell.

You can check the version with $PSVersionTable.PSVersion .

Download Powershell or Download Powershell Core

Setting up a compiler

Currently Craft supports both the MinGW and Microsoft Visual Studio (msvc) compiler. While MinGW can be installed by Craft, Visual Studio must be installed independently by the user.

Direct X SDK

If you are using the MinGW compiler, in order to compile the Qt5 qtbase package you will also need to install the Microsoft DirectX SDK. Make sure to open a new command line window after the installation for the environment variables to be set.

Installing Craft

  1. Start a PowerShell environment. It might be required to run it as administrator.
  2. Allow execution of powershell scripts by executing the following command:
    Set-ExecutionPolicy -Scope CurrentUser RemoteSigned
  3. Install Craft and follow the instructions by executing the following command:
    iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/KDE/craft/master/setup/install_craft.ps1'))
  4. Consider adding exception for the entire craft root directory to your antivirus' exceptions, otherwise build of some packages can fail (example: build of frameworks/tier2/kdoctools when AVG is used).

Using the stock Qt SDK

This will skip all Qt packages and use the official Qt builds instead. It will work fine for most CMake based recipes but definitely cause problems with QMake based projects. You will of course also miss all patches we usually apply to Qt. This is only recommended when you know what you are doing and you won't get support for in our channel.

To activate the SDK mode adapt the [QtSDK] section in your etc/kdesettings.ini to something like:

   [QtSDK]
   ## Whether to use prebuild Qt binaries.
   Enabled = True
   ## The path to the Qt sdk.
   Path = C:\Qt
   ## The version of Qt.
   Version = 5.9
   ## The compiler version, if you are not sure what to use, have a look at the directory set in QtSDK/Path.
   ## The compiler must be of the same type as General/KDECOMPILER.
   ## If you are using mingw please make sure you have installed the mingw using the Qt installer.
   Compiler = msvc2017_64

Using Craft

To use Craft you need to start a Powershell window, point that to KDEROOT\craft and run the initalization script. For example:

C:\CraftRoot\craft\craftenv.ps1

This tells Craft about your environment settings (e.g. paths). It will load your configuration from CraftRoot\etc\CraftSettings.ini. If there are any error messages Craft will not work as expected. The output should look similar to this one (of course with your paths):

PS C:\CraftRoot\craft>.\craftenv.ps1
Craft Root          : C:\CraftRoot
Craft               : R:\
Version             : master
ABI                 : windows-msvc2017_64-cl
Svn directory       : C:\CraftRoot\download\svn
Git directory       : Q:\
Download directory  : C:\CraftRoot\download