< Guidelines and HOWTOs | Build from sourceRevision as of 07:43, 30 January 2019 by TheOneRing (talk | contribs)(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff) Craft is a tool to build the sources and its third-party requirements. It is the easy way to build software. Contents 1 Setting up craft 1.1 Installing python 1.2 Setting up a powershell 1.3 Setting up a compiler 1.4 Direct X SDK 1.5 Installing Craft 1.6 Using the stock Qt SDK 2 Using Craft 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 by invocating $PSVersionTable.PSVersion in a Powershell terminal. In case you need a newer one, we recommend Powershell Core. The latest version of the standard powershell can be found here. 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 Start a PowerShell environment. It might be required to run it as administrator. Allow execution of powershell scripts by executing the following command: Set-ExecutionPolicy -Scope CurrentUser RemoteSigned 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')) 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 Then start crafting Retrieved from "https://community.kde.org/index.php?title=Guidelines_and_HOWTOs/Build_from_source/Windows&oldid=82690" Content is available under Creative Commons License SA 4.0 unless otherwise noted.