jsoncpp编译安装后报错‘PrecisionType’不是类或命名空间求助

Hey there, let's break down this issue you're hitting with jsoncpp. The PrecisionType error usually ties back to missing headers, incorrect namespace usage, or small hiccups in your installation setup. Here are the most likely fixes to try:

1. Double-check how you're referencing PrecisionType #

PrecisionType is an enum nested inside the Json::Writer class in jsoncpp—so if you're using it without the proper namespace prefix, the compiler won't recognize it. Make sure you're referencing it like this:

Json::Writer::PrecisionType

Or if you've added using namespace Json; at the top of your file, you can shorten it to:

Writer::PrecisionType

A quick scan of your code for missing namespace qualifiers here often fixes the issue right away.

2. Explicitly include <json/writer.h> #

While <json/json.h> covers most core jsoncpp functionality, some versions don't automatically pull in <json/writer.h> (where Json::Writer and PrecisionType are defined). Try adding this line before you use PrecisionType:

#include <json/writer.h>

This is a super common fix for this exact error, especially if you're working with an older jsoncpp release.

3. Verify your meson/ninja installation #

It's possible the installation didn't place all header files correctly, or you missed a configuration step. Here's how to check:

• Head to your jsoncpp installation directory (default is usually /usr/local/include/json, or the custom prefix you set with meson)
• Confirm writer.h exists in that folder
• If you used a custom prefix during meson setup (like meson setup build --prefix=/my/custom/path), make sure your compiler is looking for headers in that path. You might need to add -I/my/custom/path/include to your project's compile flags.

4. Check for version mismatches #

Newer jsoncpp versions have adjusted some type structures—for example, in recent releases, PrecisionType might be part of Json::StreamWriterBuilder instead. Double-check the version you installed and cross-reference it with the jsoncpp docs for that release to ensure you're using the correct type path.

内容的提问来源于stack exchange，提问作者Zeno