>>108666688

usecase for overall inferior compiler?

>>108667406
it memory safe language

>>108666688

File: unravel-the-kike.jpg (168.8 KB)

168.8 KB JPG

>>108666688
checked

https://desuarchive.org/g/thread/108629045

File: Annotation 2026-04-24.png (36.9 KB)

36.9 KB PNG

t. makefile

File: 4e1a1856ecde1d3186e5e605dd64dd56.jpg (12.4 KB)

12.4 KB JPG

>>108669927
>-I.

File: vertical-integration.png (18.7 KB)

18.7 KB PNG

>>108669927
you can align them in a column

>>108669927
that's not a Makefile you fucking worm
is tcc even in your environment variables? I'm going to guess not because you're a mouthbreathing shitposter for one thing
why are you not using gcc or msvc?

>>108672122
safe and recommended as best practice

>>108672755
we dont need safety in a C world, this flag is put near -g flag, its intended use is to pinpoint segmentation faults or hideous memory offset issues. if coded access without those +1-1 errors, then there will be the safety. thats how the "safety" is obtained, either you do the "safety" or someone else injects the runtime in compiled binary and does the same "safety" with whistles.

File: 6mb5ml.png (18.1 KB)

18.1 KB PNG

>>108672659
>set opts=%opt% %inc%
>proceeds to add more includes

"make" is low quality slop produced to gatekeep newcomers

File: ouch.jpg (77.8 KB)

77.8 KB JPG

>>108672926
generic VS specific. but where are your examples, no-coder-sama?

>>108673014
You're right sir.
Needs to be re-written with Jenkins and Ansible and Claw. Much smaller, faster and simpler.

>>108673192
there: >>108669927

>>108673243
fake and gay, comrade, fake and gay.

>>108666688
>helpful

this is already packaged inside TCC archive.