YOUR C LEARNING COMPANION

Kahan se padhein?

Learning path
Program bananaChapter 43 of 73

Linking aur libraries

Object files se executable tak follow karein, small static archive build aur language guarantees versus toolchain conventions distinguish karein.

5 min readIntermediateC17 baseline
Offline reading
Is chapter mein8 sections
0% through this chapter

Alag files ki translation successful ho sakti hai, phir bhi final program link na ho. Linking required definitions ko unke uses se jodti hai. Libraries reusable work package karti hain, lekin compatible names, types aur platform conventions phir bhi matter karte hain.

1. Object files translated pieces hain, C objects nahi

Conventional object file translated code, data, symbol information aur later tools ki relocation information rakhta hai. Yeh C language model ke object, jaise live int, se different hai. Standard translation aur resolution requirements describe karta hai; particular .o format, separately installed linker ya specific machine instruction set require nahi karta.

Conventional toolchain mein do kaam
Compile source files
Visible declarations check; object files produce
Link selected pieces
References ko implementations se connect karein
Link-time optimization jaisi optimizations in conventional boundaries ke across kaam kar sakti hain.

2. Ek interface ko three files mein follow karein

Operation do unsigned values mein larger choose karta hai. Yeh comparison karta hai, overflow-prone arithmetic nahi. Header declaration deta hai; implementation body deti hai; caller values supply aur result check karta hai. Files shown names se save karein.

C17 · project file · choice.h
#ifndef CODEDILE_CHOICE_H
#define CODEDILE_CHOICE_H

unsigned codedile_max(unsigned first, unsigned second);

#endif
C17 · project file · choice.c
#include "choice.h"

unsigned codedile_max(unsigned first, unsigned second)
{
    return first > second ? first : second;
}
C17 · project file · main.c
#include "choice.h"
#include <assert.h>
#include <stdio.h>

int main(void)
{
    unsigned larger = codedile_max(3, 7);
    assert(larger == 7);
    assert(codedile_max(4, 4) == 4);
    printf("larger=%u\n", larger);
    return 0;
}

3. Separately compile karke link karein

Yeh three files wale folder mein Unix-like shell ke example GCC commands hain. Tool commands hain, C statements nahi. -c linking se pehle stop karta hai. Final command mein GCC driver target ka normal startup aur library support bhi arrange karta hai; raw linker directly invoke karne ke liye more platform knowledge chahiye.

GCC / GNU tools · example commands
gcc -std=c17 -Wall -Wextra -c choice.c -o choice.o
gcc -std=c17 -Wall -Wextra -c main.c -o main.o
gcc main.o choice.o -o choice_demo
./choice_demo

Program larger=7 print karta hai. Link command se choice.o omit karein toh choice.h ki declaration se main.c compile ho sakti hai, lekin checked build link time par missing definition report karta hai. Header dobara include karna missing body supply nahi karega. Correct implementation object ya library build mein add karein.

4. Static archive object members package karti hai

Common GNU toolchain par static library object members ki archive hai. Conventional link mein linker needed members select karke unke contents output mein incorporate karta hai. Whole archive file ko simply executable mein copy nahi karta. Special options, members ki dependencies aur later optimizations selected contents affect kar sakti hain.

GCC / GNU tools · example commands
ar rcs libchoice.a choice.o
gcc main.o -L. -lchoice -o choice_archive
./choice_archive

Is example mein sirf archive candidate hai; same-named shared library bhi ho toh search use prefer kar sakti hai. Explicit ./libchoice.a name karne se yeh archive select hoti hai. Yahan GNU ar rcs libchoice.a aur symbol index create/update karta hai. GCC ka -L. current folder search path mein add karta hai; -lchoice platform-appropriate choice library request karta hai. Conventional GNU archive search mein referencing objects ke baad archive rakhein: main.o -lchoice. Reverse order unresolved references de sakta hai. Naming aur search rules toolchain conventions hain.

5. Shared libraries deployment relationship add karti hain

Shared library usually separate binary dependency rehti hai. Binding linking, program loading ya later execution mein ho sakti hai, platform aur options ke according. Typical suffixes .so, .dylib aur .dll hain; koi standard C guarantee nahi. Program static aur shared dependencies mix kar sakta hai. Statically linked component se har system component embedded hona imply nahi hota.

Installed header aur library alag problems solve karte hain. Compatible binary ko right target architecture, calling conventions, data layout aur library version bhi chahiye: environment ke ABI ka part. Same-spelled symbol two function types agree hone ka proof nahi. Interface ya ABI change par dependent code rebuild karein aur library ki ownership/error rules follow karein.

Primary references aur aage ki reading

Aage badhne se pehle

  • Linking references ko build mein supplied definitions se connect karti hai.
  • Static archives aur shared libraries toolchain rules se components package karti hain.
  • Compatible naam akela full ABI aur ownership contract establish nahi karta.
In ideas ko alag rakhein
Library available / Library correctly used
Library milne ke baad bhi compatible interfaces, suitable link options aur required runtime environment chahiye.
Apne words mein samjhaayein

Missing definition, incompatible declaration aur unavailable shared dependency ko kaun-sa evidence alag karega?

Optional: bolkar samjhein ya note rakhein. Tayyar hon toh aage badh sakte hain.

Apni understanding check karein

Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.

Library declaration dikhne aur uski definition supply hone mein kya farq hai?
Har choice ki explanation padhein
  1. Declaration type checking mein help karti hai; build ko required implementation phir bhi chahiye.

    ✓ Sahi reasoning. Toolchain library definitions kaise supply karti hai, yeh header inclusion se alag hai.

  2. Header include karna computer ki har library build karta hai.

    Header inclusion source declarations deta hai, universal library-build operation nahi.

  3. Har C implementation same library command-line flags require karti hai.

    Toolchain flags implementation-specific interfaces hain.

C17

Agla idea padhne ke liye tayyar?

Mark this chapter as read whenever you feel ready.

CHAPTER 43 / 73

Is chapter mein

Linking aur libraries

Search all 73 chapters in both languages.EN + HG

Try “pointer”, “why int”, or “undefined behavior”.

Concepts connect. Follow your curiosity.↑ ↓ to explore · Enter to open
MAKE YOURSELF COMFORTABLE

Your reading space

Appearance

A clear canvas with balanced contrast.

Text size

100%
AA

Reading tools

Your data stays in this browser

Export a backup before changing browsers or replacing an older version of the reader.

YOUR PERSONAL MARGINS

My notebook

Saved on this device
A LITTLE CLARITY

The glossary

A starting meaning, then a chapter to go deeper.

A QUICK DEFINITION

A little clarity

Read the full explanation →

A thought worth keeping