Pitchforks: A (de facto) Standard Project Layout for C / C++ projects

Posted by dananjaya86 on Friday March 10, 2023 @09:57AM
from the github.com dept.

https://github.com/vector-of-bool/pitchforkhttps://github.com/vector-of-bool/pitchfork

( 3 comments | on HN )

Re:Pitchforks: A (de facto) Standard Project Layout for C / ... by jjgreen on Friday March 10, 2023 @09:58AM (#35095073)

Link broken, should be https://github.com/vector-of-bool/pitchfork

[ Parent | on HN ]

Re:Pitchforks: A (de facto) Standard Project Layout for C / ... by AlbertoGP on Friday March 10, 2023 @12:54PM (#35098186)

The most interesting part for me is the specification from data/spec.bs, whose rendered version is linked from the repository README.md, section “1.3. Project Directories”:

https://api.csswg.org/bikeshed/?force=1&url=https://raw.gith...

I’ve been using “libs/” for external libraries, but after reading this I’m considering “external/” for that purpose.

[ Parent | on HN ]

Re:Pitchforks: A (de facto) Standard Project Layout for C / ... by AlbertoGP on Saturday March 11, 2023 @05:06AM (#35106997)

Looking more into this, I found this document with details about the popularity of different alternative directory names: “Project Layout - Survey Results and Updates” https://vector-of-bool.github.io/2018/09/16/layout-survey.ht...

There is also a separate proposal from around the same time, dated one month later and very focused on C++ which I find less useful for C: “Canonical Project Structure” https://open-std.org/JTC1/SC22/WG21/docs/papers/2018/p1204r0...

[ Parent | on HN ]