![]() Preparing for compilationįirst of all, we need to decide where do we want to install the alternative version of GIMP. But if we install GIMP at a different location, we need to configure the environment variables so that the correct versions of libraries will be found and used, both for compilation and for running GIMP. We don’t want to compile GIMP and install it in the default location, because then it may conflict with our existing installation. What’s the problem with environment variables? So, in order for us to install and use libraries in other locations we need to update this variable to point to the directory leading to these libraries. The executables search for these libraries inside some directories which are considered as “default”. One example which you should know (if you are a Linux user) is Gtk+ – the library which is used by many applications (including GIMP) to create the user interface. Many executables used files which are called shared libraries – these files contain functionality that should be shared between executables. This environment variable tells the pkg-config tool (a tool which is used to resolve most dependencies in GIMP’s compilation) where to look for the config files (which are used by pkg-config) for installed libraries. The order of directories inside the path does matter! Directories which are listed first, are searched first! PKG_CONFIG_PATH usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/usr/local32/bin.Īs you can see, the path is composed out of a list of paths to directories, separated by ':' signs. When you type "gimp" in the command line, all the directories inside the path will be searched. There are 3 environment variables which we should get to know when compiling things on Linux, and we’ll now present them: PATHįirst of all, this environment variable specifies where to look for executables. The main "problem" (don't worry, it's solvable) with compiling gimp on Linux, is environment variables. Through this guide, I’m going to use the bash shell for executing stuff from the command line – it’s usually located in /bin/bash. It will explain how to install GIMP to a custom location so that it won’t conflict with your existing GIMP installation. This guide will explain you how to install GIMP, even without root/admin permissions/privileges. I’m not responsible for any damage caused to your computer by following any part of this guide. Warning: Installing software and making changes to your system, is risky, especially if you don't know what you are doing! This guide is written in hope that it will be helpful, but it's without any guarantee that it will work or that it won't damage your computer. Instructions for compiling on windows from git, will be posted later. ![]() Perl was also extracted to the wrong place, but it didn’t affect the compilation).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |