Question 1

How to create a new Pitchfork-compliant C++ project?

Accepted Answer

Use the experimental pf tool by building it from the repository, but note it's not fully documented. Alternatively, manually structure your project according to the layout specification in data/spec.bs.

Question 2

Pitchfork vs CMake project conventions: which is better for my team?

Accepted Answer

Pitchfork aims for a universal standard independent of build systems, while CMake has its own recommended layouts. If your team is already deep into CMake's ecosystem, sticking with CMake might be easier; Pitchfork is better for projects seeking cross-tool consistency.

Question 3

Can Pitchfork be used with existing build systems like Bazel or Make?

Accepted Answer

Yes, Pitchfork is build-system agnostic—it focuses on directory layout. You can integrate it by aligning your project's structure with the specification, though you'll need to configure build files manually.

Question 4

Is the pf tool stable enough for production use?

Accepted Answer

No, the README clearly states the pf tool is experimental and has a while to go before being useful, so it's not recommended for production environments requiring reliability.

Question 5

What are the benefits of adopting Pitchfork for open-source C++ libraries?

Accepted Answer

Adopting Pitchfork can make your library easier to integrate and contribute to, as it standardizes layout, reduces onboarding time, and improves compatibility with future tooling.

Question 6

How does Pitchfork handle dependencies and third-party code?

Accepted Answer

The specification includes guidelines for organizing dependencies, such as separating internal and external code, but actual management depends on your build system and may require additional configuration.

pitchfork

What is pitchfork?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions