BarinkOS/CoreLib/Makefile

CPP = /opt/cross/bin/i686-elf-g++
CFLAGS = -ffreestanding -Og -ggdb -Wall -Wextra

BUILD_DIR = ../build/CoreLib
OBJ_FOLDER = ../bin/CoreLib
OUTPUTFILE = $(BUILD_DIR)/libCoreLib.a

OFILES = $(OBJ_FOLDER)/ctype.o $(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_DIR)/include/CoreLib

$(OUTPUTFILE): $(OFILES)
	pwd
	ar -rc $(OUTPUTFILE) $(OFILES)

$(OBJ_FOLDER)/ctype.o: ctype.cpp
	$(CPP) -c ctype.cpp -o $(OBJ_FOLDER)/ctype.o $(CFLAGS)

$(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)
Fixup C++ compiler path in makefile of CoreLib memcpy implementation added 2023-02-25 19:04:34 +00:00			`CPP = /opt/cross/bin/i686-elf-g++`
Moving certain aspects into their own static library 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. 2023-02-19 22:38:32 +00:00			`CFLAGS = -ffreestanding -Og -ggdb -Wall -Wextra`

Improved build system Added new entries to .gitignore Moved away from source directory as central spot for all source code 2023-02-19 23:29:06 +00:00			`BUILD_DIR = ../build/CoreLib`
			`OBJ_FOLDER = ../bin/CoreLib`
Moving certain aspects into their own static library 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. 2023-02-19 22:38:32 +00:00			`OUTPUTFILE = $(BUILD_DIR)/libCoreLib.a`

Added ctype std lib functions 2023-02-25 19:41:21 +00:00			`OFILES = $(OBJ_FOLDER)/ctype.o $(OBJ_FOLDER)/memory.o $(OBJ_FOLDER)/path.o $(OBJ_FOLDER)/stack.o $(OBJ_FOLDER)/string.o $(OBJ_FOLDER)/stringview.o`
Moving certain aspects into their own static library 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. 2023-02-19 22:38:32 +00:00
			`.phony: all`
			`all: $(OUTPUTFILE)`
Improved build system Added new entries to .gitignore Moved away from source directory as central spot for all source code 2023-02-19 23:29:06 +00:00			`cp *.h $(BUILD_DIR)/include/CoreLib`
Moving certain aspects into their own static library 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. 2023-02-19 22:38:32 +00:00
			`$(OUTPUTFILE): $(OFILES)`
Fixup C++ compiler path in makefile of CoreLib memcpy implementation added 2023-02-25 19:04:34 +00:00			`pwd`
Moving certain aspects into their own static library 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. 2023-02-19 22:38:32 +00:00			`ar -rc $(OUTPUTFILE) $(OFILES)`

Added ctype std lib functions 2023-02-25 19:41:21 +00:00			`$(OBJ_FOLDER)/ctype.o: ctype.cpp`
			`$(CPP) -c ctype.cpp -o $(OBJ_FOLDER)/ctype.o $(CFLAGS)`

Moving certain aspects into their own static library 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. 2023-02-19 22:38:32 +00:00			`$(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)`