Kaynaktan Derleme: configure, make ve make install

Package managers like apt and dnf cover most needs, but sometimes you must build software from source: a newer version, a missing distro package, or custom compile options.

Most source projects follow the same ritual:

• ./configure checks your system
• make compiles the code
• make install copies files into place

Source usually arrives as a compressed tarball, which ties back to the archiving skills you already learned.

You need a compiler and make. On Debian/Ubuntu the meta-package build-essential provides them.

./configure probes for libraries and generates a Makefile. The --prefix option chooses where it will install.

make reads the Makefile and compiles. Use -j to parallelize across CPU cores for speed.

make install copies binaries and data into the prefix. Installing to system paths usually needs root.

If configure complains about a missing library, install its -dev package, which provides headers needed for compiling.

make clean removes compiled objects so you can rebuild from scratch.

Source installs are not tracked by your package manager. Many projects offer make uninstall, or you can install to /usr/local to keep them separate from packaged software.

Prefer packages when possible: they handle dependencies and updates. Build from source only when you need control or a version your distro lacks.

Which step actually compiles the program?

You can build software the classic way:

• Extract the tarball with tar
• ./configure --prefix=... sets up the build
• make -j compiles, sudo make install installs
• Install -dev packages for missing headers

Reach for source builds only when packages cannot meet your needs.