Repository navigation
Expand file tree
/
Copy pathNotes.nt
More file actions
49 lines (34 loc) · 2.88 KB
/
Copy pathNotes.nt
File metadata and controls
49 lines (34 loc) · 2.88 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
[06/20/25]
I want to practice my programming by writing a C++ package manager... in C++. What could go wrong?
Ooh, NOTE TO SELF: I could automate my Makefile setup (and kinda really want to). That could also be a prt of this project as it'll probably be invoking GNU make under the hood (altho, I could just manually call compilers and shit myself... oooh...).
Finally fucking finished the build system and the project structure. On god, this is all just validating the project's existence: ~4hrs spent on setup alone.
[07/22/25]
Coming back to this project; I think I finally have a really good solid idea for how I want to structure my Makefiles. At least 90%. I might change how the "selection" process works, but the main idea for this "build system" program is that I don't want to have to use the program to build my projects, I just want it to generate Makefiles for me.
I want to have options for:
- compiler choice
- cross compatibility
- building as a library
- colored output
- versioning
- running other, user-created Makefiles
- 'clean' variations (like a dirty clean)
- various flag-related options
- common debug flags
- architecture-specific flags
- C++ vs C specific flags
- architecture-specific flags
I also want default options for all of these; the default option will be my personal preference.
I've got a prototype down that correctly generates the Makefile for this project! It's very bare bones, so it's already very close to being a good default Makefile. The only real issues with the "default" Makefile are that the source directories are hardcoded to this project, but I could fix that by asking the user for the source code directory and then doing some recursive searching to find all the relevant directories.
I got the recursive directory search done! It's a prototype but it works pretty well so far, and even returns prettified text!
[07/28/25]
I created the `getargs` library today and decided that version 2.0 of `makemake` will start off by removing all argument-handling code and replacing it with `getargs`.
[07/29/25]
I'm going to implement source directory updating for `makemake`. In under an hour.
I JUST MANAGED TO FINISH IN UNDER AN HOUR!! WOOOOO!!
[08/04/25]
I want to implement more ways of "updating" the Makefile. Specifically, I want to add a flag for changing the C/C++ standards.
Well, I didn't do that but I did update the "update source directories" functionality to not only be its own function but to also be much much MUCH better at what it does.
[08/13/25]
I want to finish my work on the overhaul and wrap this all up in a neat bow.
First off, I want to make sure that duplicate library directories are ignored. I can do that with `std::list::sort` followed by `std::list::unique`.
Welp, I finally finished! I still have lots to do, but for now I'm pretty happy with how this program has turned out.