Building from source basics in Linux CLI - Step-by-Step Execution

Concept Flow - Building from source basics

Download source code

↓

Extract source files

↓

Configure build options

↓

Compile source code

↓

Install compiled program

↓

Clean up build files

↓

DONE

This flow shows the main steps to build a program from source code on Linux.

Execution Sample

Linux CLI

wget http://example.com/app.tar.gz

tar -xzf app.tar.gz

cd app

./configure

make

sudo make install

make clean

This script downloads, extracts, configures, compiles, installs, and cleans up a program from source.

Execution Table

Step	Command	Action	Result/Output
1	wget http://example.com/app.tar.gz	Download source archive	app.tar.gz downloaded
2	tar -xzf app.tar.gz	Extract files	Source files extracted to ./app
3	cd app	Change directory	Now inside source folder ./app
4	./configure	Prepare build	Checks system, creates Makefile
5	make	Compile source	Builds executable files
6	sudo make install	Install program	Copies files to system folders
7	make clean	Clean build files	Removes temporary build files
8	-	End	Build and install complete

💡 All steps completed successfully, program built and installed.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	After Step 7	Final
Current Directory	/home/user	/home/user	/home/user	/home/user/app	/home/user/app	/home/user/app	/home/user/app	/home/user/app	/home/user/app
Source Archive	None	app.tar.gz	app.tar.gz	app.tar.gz	app.tar.gz	app.tar.gz	app.tar.gz	app.tar.gz	app.tar.gz
Build Files	None	None	Extracted	Extracted	Configured	Compiled	Compiled	Cleaned	Cleaned
Installed Program	No	No	No	No	No	No	Yes	Yes	Yes

Key Moments - 3 Insights

Why do we run './configure' before 'make'?

The './configure' step checks your system and creates the Makefile that 'make' uses to compile. Without it, 'make' won't know how to build the program. See execution_table step 4 and 5.

What happens if we skip 'sudo make install'?

Skipping 'sudo make install' means the program is compiled but not copied to system folders, so you can't run it globally. It stays only in the build folder. See execution_table step 6.

Why do we use 'make clean' at the end?

'make clean' removes temporary build files to free space and keep the folder tidy. It does not remove the installed program. See execution_table step 7.

Visual Quiz - 3 Questions

Look at the execution table, what is the result of running 'tar -xzf app.tar.gz'?

A Source files extracted to ./app

B app.tar.gz downloaded

C Builds executable files

D Copies files to system folders

💡 Hint

Check execution_table row 2 under Result/Output column.

At which step does the program get installed on the system?

A Step 4

B Step 5

C Step 6

D Step 7

💡 Hint

Look at execution_table step 6 and its Action and Result.

If we skip './configure', what will likely happen when running 'make'?

A Compilation will succeed without issues

B Makefile will be missing or incorrect, causing errors

C Program will install automatically

D Source files will not extract

💡 Hint

Refer to key_moments about the role of './configure' before 'make'.

Concept Snapshot

Building from source involves these steps:
1. Download source code archive
2. Extract files with tar
3. Run './configure' to prepare build
4. Compile with 'make'
5. Install with 'sudo make install'
6. Clean build files with 'make clean'

Full Transcript

Building from source means creating a program from its original code. First, you download the source archive file. Then you extract it to get the source files. Next, you run './configure' to check your system and prepare the build instructions. After that, you compile the code using 'make'. Once compiled, you install the program with 'sudo make install' so it can be used system-wide. Finally, you can clean up temporary build files with 'make clean'. Each step must be done in order for the build to succeed.