如何在AdaCore GPR文件中配置C++头文件搜索路径及排查找不到文件问题

Let's break down why your setup isn't working and walk through actionable fixes step by step:

1. Refine Your GPR Configuration for Reliability #

Your team’s #include "Common/SomeHeader.h" directive means the compiler needs access to the parent folder of the Common directory (since it will look for a Common subfolder inside each configured include path). Your initial approach is close, but we can eliminate relative path ambiguity with GPR’s built-in attributes:

project Your_Project is
   for Languages use ("C++");
   -- Set your source/object directories to match your project structure
   for Source_Dirs use ("src");
   for Object_Dir use "obj";

   package Compiler is
      -- Anchor the relative path to your GPR file's location using Project'Project_Dir
      -- This avoids issues with GNAT Studio's default build working directory
      for Include_Path ("c++") use (Project'Project_Dir & "/../../");
      -- If you prefer using Include_Switches, ensure no extra spaces after -I
      for Include_Switches ("c++") use ("-I" & Project'Project_Dir & "/../../");
   end Compiler;
end Your_Project;

The Project'Project_Dir attribute is key here—it guarantees the ../../ path is calculated from where your GPR file lives, not from a random build directory that GNAT Studio might use.

2. Validate the Header’s Actual File Path #

Before troubleshooting further, confirm the header exists at the expected location:

• Open GNAT Studio’s terminal, navigate to your GPR file’s directory, and run:

  ls ../../Common/SomeHeader.h
  

If this command fails, your relative path is incorrect (e.g., the Common folder might be one level up instead of two, or your project is nested differently). Fix the path in your GPR file first.

3. Inspect the GprBuild Command Line #

GNAT Studio shows the exact compiler command used during builds—check this to confirm your include path is being passed correctly:

1. Trigger a build in GNAT Studio.
2. Locate the g++ command in the build log.
3. Verify that -I../../ (or the absolute path generated via Project'Project_Dir) appears in the command arguments.

If the -I flag is missing, your GPR configuration isn’t being applied. This could happen if:

• You’re using a nested project structure and the configuration is in the wrong project file.
• There’s a syntax typo in your GPR (e.g., missing semicolons, incorrect package naming).

4. Debug with an Absolute Path #

To rule out relative path confusion, temporarily replace the relative path with an absolute path to the parent of Common, like:

for Include_Path ("c++") use ("/absolute/path/to/folder-containing-Common");

If this works, the issue was definitely related to relative path resolution—switch back to Project'Project_Dir for portability.

Key Context to Remember #

For #include "X/Y.h", the compiler searches in this order:

1. The directory of the source file containing the include directive.
2. Each path specified via -I (or Include_Path in GPR).

By ensuring the parent of Common is in your include path, the compiler will find Common/SomeHeader.h exactly as your team’s规范 requires.

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