Nigel
b07b4f0d38
Problem: As our kernel grows we need more complex datastructures and functions these would come from the standard C/C++ library with normal programs. The kernel is a freestanding programme and has no access to standard libraries. Solution: We build a mini version of the standard C/C++ library which will contain the datastructures and functions we want. This library can then be statically linked into our kernel binary. Making it a statically linked library also gives more structure to the project. Keeping these random functions and datastructures in the kernel just clutters the kernel source code with less relevant source code.
34 lines
894 B
Makefile
34 lines
894 B
Makefile
CPP = ${HOME}/opt/cross/bin/i686-elf-g++
|
|
CFLAGS = -ffreestanding -Og -ggdb -Wall -Wextra
|
|
|
|
SRC_DIR = .
|
|
BUILD_DIR = build
|
|
OBJ_FOLDER = bin
|
|
OUTPUTFILE = $(BUILD_DIR)/libCoreLib.a
|
|
|
|
OFILES = $(OBJ_FOLDER)/memory.o $(OBJ_FOLDER)/path.o $(OBJ_FOLDER)/stack.o $(OBJ_FOLDER)/string.o $(OBJ_FOLDER)/stringview.o
|
|
|
|
|
|
.phony: all
|
|
all: $(OUTPUTFILE)
|
|
cp *.h build/include/
|
|
|
|
$(OUTPUTFILE): $(OFILES)
|
|
ar -rc $(OUTPUTFILE) $(OFILES)
|
|
|
|
$(OBJ_FOLDER)/memory.o: Memory.cpp
|
|
$(CPP) -c Memory.cpp -o $(OBJ_FOLDER)/memory.o $(CFLAGS)
|
|
|
|
$(OBJ_FOLDER)/path.o: Path.cpp
|
|
$(CPP) -c Path.cpp -o $(OBJ_FOLDER)/path.o $(CFLAGS)
|
|
|
|
$(OBJ_FOLDER)/stack.o: Stack.cpp
|
|
$(CPP) -c Stack.cpp -o $(OBJ_FOLDER)/stack.o $(CFLAGS)
|
|
|
|
$(OBJ_FOLDER)/string.o: String.cpp
|
|
$(CPP) -c String.cpp -o $(OBJ_FOLDER)/string.o $(CFLAGS)
|
|
|
|
$(OBJ_FOLDER)/stringview.o: StringView.cpp
|
|
$(CPP) -c StringView.cpp -o $(OBJ_FOLDER)/stringview.o $(CFLAGS)
|
|
|