🌿 Chill xv6 OSdev gardening: Clang-format, build errors, C build fundamentals, #include hygiene 🌿

2:30 Intro
4:23 clang format intro; feeling at home; garden analogy
11:35 q&a: my background, infosec, music tech
16:50 fixed initial broken build
19:10 clang-format broke the build (START HERE)
22:40 diagnosing build issue – include order
39:30 include guards explanation

===
0:20: 🌿 Exploring xv6 OS development through coding practices and troubleshooting.
9:33: ⚙️ Troubleshooting build errors and unfamiliar file formats in OS development environment setup.
17:38: 🌿 Developer faces challenges with build system, receives likes on tweet, and continues with OS development.
25:45: 🌿 Addressing missing #include errors in the xv6 OS codebase while enjoying a relaxing and straightforward debugging process.
34:08: 🌱 Addressing build errors and improving #include hygiene in xv6 OS development
43:30: 🌿 Preference for standard C/C++ types over custom non-standard types in programming.
52:53: 🌱 Efficient coding practices discussed while updating code base and fixing build errors.
1:02:04: 🌱 Exploring issues with assembly code inclusion in C headers and seeking solutions through community engagement.
1:10:31: 🌱 Engaging in productive coding session, addressing build errors, and maintaining code quality.
1:20:51: 🌱 Improving code formatting, addressing build errors, and enhancing #include organization in OS development.
1:32:05: 🌱 Resolving merge conflicts and optimizing code formatting in C programming.
Recap by Tammy AI
===

I’m am experienced systems programmer, working on chill fork of the xv6 kernel — for myself, for fun 🙂

Today my goal was to clang-format all the files to feel more at home in the codebase. This ended up breaking the build completely due to bad include hygiene in the original codebase, and I fixed it all up.

Topics covered: C programming & build system basics: headers, forward declaration, ifdefs, include guards. A bit of git conflict resolution.

—

Post stream reflections:
– It’s cool how I had very little expectations for the stream (we’d just run clang format and that’s it)

[ad_2]

source