News for hackers. Stuff that matters.

A comment on How to Structure C Projects: These Best Practices Worked for Me. Parent comment

Re:How to Structure C Projects: These Best Practices Worked ... by ReleaseCandidat on Friday March 08, 2024 @09:59AM (#39641611)
> The build system situation in the C world is dire.

Meta's Buck 2 (written is Rust) would be my choice, if I would write "new" C or C++.

Examples using Vcpkg

https://github.com/Release-Candidate/Cxx-Buck2-vcpkg-Example...

And Conan

https://github.com/Release-Candidate/Cxx-Buck2-Conan-Example...

[ Parent | on HN ]
Re:How to Structure C Projects: These Best Practices Worked ... by humanrebar on Friday March 08, 2024 @01:07PM (#39643909)
If you're writing C, you might not want tools written in higher level languages required for your build environment.

This is why you still see a lot of important C project support autotools even though it's a pretty awful developer experience.

[ Parent | on HN ]
Re:How to Structure C Projects: These Best Practices Worked ... by jpc0 on Friday March 08, 2024 @01:48PM (#39644503)
Calling rust a high level language gave me a chuckle. Thank you sir and incase anyone wonders, I agree.
[ Parent | on HN ]
Re:How to Structure C Projects: These Best Practices Worked ... by maleldil on Sunday March 10, 2024 @01:29PM (#39660863)
They said high_er_. It's not controversial to think that C++ and Rust are higher-level than C.
[ Parent | on HN ]