How to Structure C Projects: These Best Practices Worked for Me

Re:How to Structure C Projects: These Best Practices Worked ... by cmovq on Friday March 08, 2024 @11:10AM (#39642434)

I don’t understand why people bother with complex build systems for small C projects.

Here is a C build system:

    cat all.c
    #include "foo.c"
    #include "bar.c"
    #include "main.c"

    clang all.c

[ Parent | on HN ]

Re:How to Structure C Projects: These Best Practices Worked ... by eschneider on Friday March 08, 2024 @11:41AM (#39642811)

#include "/dev/tty0"

so you can add run-time defines.

[ Parent | on HN ]

Re:How to Structure C Projects: These Best Practices Worked ... by humanrebar on Friday March 08, 2024 @01:11PM (#39643975)

Now add an address sanitizer pass, reasonable unit tests, and wire it up to CI so you don't accidentally break things or trash memory.

[ Parent | on HN ]

Re:How to Structure C Projects: These Best Practices Worked ... by kerkeslager on Friday March 08, 2024 @03:15PM (#39645826)

Sure, trivial problems only require trivial solutions. Obviously.

But I don't want to solve trivial problems. That's not where the value is.

[ Parent | on HN ]