#include“file”如何在XC8中工作？

可以在项目设置中向项目中添加其他搜索路径。



      以下为原文

    You can add additional search paths to the project, in the project settings.

手册：



      以下为原文

    From the manual:

我看到了，但是“WorkDirectory”看起来很模糊，因为我不知道它是否意味着项目、单元或文件中包含的内容。无论是哪种方式，XC8和AY都似乎存在差异，并且被认为是“工作目录”。基本上，如果你做了一个包含并提供一个路径，那么XC8将工作目录更改为该路径，并且从该文件中包含的任何文件都与该文件（已更改的工作目录）相对应。路径不必是满的，它可以是相对于当前文件的。但是，如果你做了一个包含并且不提供路径的编译器，那么编译器就可以使用“包含”路径，那么工作目录保持不变，并且包含在该文件中的“X”不会发现文件中包含的文件包含了“γ”，我不认为这是正确的行为。海湾合作委员会的行为不是这样的。甚至MPLAB X都不这样做，右键单击“包含”和“选择导航到声明”打开了我所期望的文件。为了展示这种差异，我用3种配置制作了一个简单的MPLABX项目。TestEtFuleLay引号配置显示，包含在包含语句中的路径更改工作目录，而其他2种配置表明，通过包含路径打开文件不会更改工作目录。在3种配置中，GCC工作（有一个简单的BAT文件，所有3个要测试）。在3种配置中，MPLABX IDE都用于打开正确的文件（右键单击“包含”并导航到“定义”），即使XC8本身表示无法找到。MPLABX项目可以找到AtTTPs//Delix.com……1GxM9VQZ2RFD2Z6AM9CBJA。



      以下为原文

   




I saw that, but "working directory" seemed vague because I didn't know if it meant the project, the unit, or the file doing the including.    Either way, there does seem to be a discrepancy in XC8 and #include and what is considered the "working directory".  Basically, if you do an #include and provide a path then XC8 changes the working directory to that path and any files included from that file are relative to that file (the changed working directory).  The path doesn't have to be full, it can be relative to the current file.  But if you do an #include and don't provide a path, instead having the compiler use the #include path, then the working directory stays the same and the #includes in that file won't find the files in the directory of the file doing the #including.
 
I don't feel like this is proper behavior.  GCC doesn't behave like this.  Not even MPLAB X behaves like this, right clicking on the #include and selecting navigate to the declaration opens the files I expect.
 
To showcase this discrepancy I made a simple MPLABX project with 3 configurations.  The TEST_FULL_QUOTES configuration shows that including a path in the #include statement changes the working directory, whereas the other 2 configurations show that opening a file thru an include path does not change the working directory.  In either 3 configurations GCC works (there's a simple bat file of all 3 to test).  In either 3 configurations MPLABX IDE works for opening the correct file (right click on the #include and navigate to definition), even though XC8 itself says it cannot be found.
 
The MPLABX project can be found at https://drive.google.com/...1GxM9vqZ2Rfd2Z6am9CbjA

GCC不是标准，标准说几乎所有关于文件是如何定位的都是实现的。来自XC8团队的人可能会停下脚步，释放一些光。



      以下为原文

   
 
GCC isn't the standard, and the standard says pretty much everything about how include files are located is implementation-defined.
 
Someone from the XC8 team might stop by and shed some light.

GCC不是标准，标准说几乎所有关于文件是如何定位的都是实现的。来自XC8团队的人可能会停下脚步，轻松一下。约翰，你已经完成了一项艰巨的任务。



      以下为原文

   
 
GCC isn't the standard, and the standard says pretty much everything about how include files are located is implementation-defined.
 
Someone from the XC8 team might stop by and shed some light.



You've already done a stellar job, John.
 

这是一个公平的评论。然而XC16和XC32是基于GCC的，这意味着XC8的工作方式与Microchip的其他编译器不一样。我想知道在AVR XC8中会发生什么，这也是基于GCC的。我认为MPLAB X可以找到文件和XC8这一事实不能说明XC8是错误的。



      以下为原文

   


That's a fair comment.
 
However XC16 and XC32 are GCC based, meaning that XC8 does not work the same way as Microchip's other compilers.  I wonder what will happen in AVR XC8, which is also GCC based.
 
I think the fact that MPLAB X can find the file and XC8 cannot says that XC8 is in error.

你是说你有一个包含XC8的文件，不管你提供的包含什么的指令，都不能打开。那是个错误。



      以下为原文

   
 
Are you saying you have an include file located somewhere that XC8 is unable to open regardless of the #include directive you provide?  That would be an error.