ublop.blogg.se

In particular, as pfnuesel says, this is how you configure Want to pass options to the configure script to configure the build. configure, make, sometimes make check or make test,Īnd then make install or sudo make install, you will sometimes When the thing you are installing providesĮxecutable commands, those executables are typically copied into aĭirectory that is in $PATH or that you should consider adding toĪlthough building and installing software is often as simple as This copies files from the build directory

configureĪnd make, you will usually use make install (or sudo make install) When you have source code that is compiled by running. To answer this more fully, I've reproduced two sections from my answer to How to install tar file “globally”? (on Unix & Linux), which address this question specifically: Configuring Your Build

Most configure scripts support -prefix, and omitting it and just running. It is called -prefix because it lets you give the prefix that appears in the paths to each of the directories where files from the program or library that you are building are to be installed. configure, the -prefix option lets you specify where those directories are. Executables that provide commands the user is intended to run usually go in a bin directory, libraries usually go in a lib directory, manual pages usually go in a man directory, and so forth. When you install software with make install or sudo make install, different files are placed in different directories.