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

#1

Post by dananjaya86 » Fri, Mar 10, 2023, 2:57 PM UTC

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

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

#2

Post by jjgreen » Fri, Mar 10, 2023, 2:58 PM UTC

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

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

#3

Post by AlbertoGP » Fri, Mar 10, 2023, 5:54 PM UTC

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.

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

#4

Post by AlbertoGP » Sat, Mar 11, 2023, 10:06 AM UTC

AlbertoGP wrote: post #3

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.

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...