If you follow the guide closely, install correct dependencies and make sure your PATH doesn’t contain anything unwanted, there should be no issues. This is also more difficult than building Krita on Linux, so you need to pay attention to details. Note that you will do all your work in a CMD command window. If you decide to build all the dependencies yourself, this will take a long time. On Windows, you can either reuse the dependencies from the KDE Binary Factory, or build the dependencies yourself. One example is where a plugin is removed from Krita the plugin will be in your install dir, and won’t get updated when Krita’s internals change. Sometimes, changes in Krita’s source code from git revision to git revision make it necessary to make your installation and/or build dir empty and build from scratch. A library got updated, and you need to remove the CMakeCache.txt file in your build dir and run cmake again. You can also have a successful build, then update your linux installation, and then find that Krita no longer builds. You might need to update your Linux installation to a newer version. CMake will report when the version of a dependency is too old. A missing dependency is not an “error” that you need to report to the other Krita developers.Ī dependency can also be too old. The most common problem is a missing dependency. Outside of the source being unstable, there’s the following common problems: :~/kritadev/krita> git checkout master :~/kritadev/krita> git pull Common problems ¶ Note: type in what’s shown after ‘>’ in the following commands We will call the “kritadev” folder your build root. $HOME/kritadev/install – the location where you install krita to and run krita from $HOME/kritadev/build – the location where you compile krita The most convenient layout is as follows: Building on Linux ¶ Preparing your development environment ¶ Building Krita is a technical task and demands accuracy in following instructions and intelligence in understanding what happens. On all operating systems, you need to be familiar with using a terminal. On Windows you can either reuse the dependencies from the KDE Binary Factory, or build the dependencies yourself. Building the dependencies manually is recommended because we have a number of changes to the source for libraries to make them function better with Krita. On macOS you can use tools like homebrew to get the dependencies, or build the dependencies manually. For an easy guide to building Krita see Building Krita on Linux for Cats. Linux is the easiest operating system to build Krita on because all the libraries that Krita needs are available on most recent Linux distributions. The libraries Krita needs (for instance to load and save various image types) are called dependencies. You can build Krita on Linux, Windows, macOS and on Linux for Android. Using prebuilt dependencies from the binary factory
0 kommentar(er)
