MPLAB X的PCLint插件怎么使用

FLUWOWIN是一个列表，我想看看PCLUT插件工作的酸性项目有几个目标（配置），这使得处理PCLint有点困难，而且，PCLIt插件缺少一些定义，我们也使用存储库，如SN和GITSU以下SUGGSES试图解决我们在遇到多个配置时遇到的问题，并且配置特定的宏${CONDNON}，${Projutdir }指的是如果您右键单击一个项目并点击“构建”来配置一个宏可见。在选项下拉列表中，应该有一个选项“配置文件文件”（没有给出路径或文件），如果选择了“生成pCurt依赖文件”，它将创建一个${PrimeDIr}/pCurt/${CuffN}}的文件。当执行“pCLinux这个项目”时，应该包括这个目录，当执行“pCLinux这个项目”时，它看起来是这样的（对于xc16编译器）${Projdidir}/pCurt/${FuNNID}/COXXC16.LNT-I $ {ProjiDIr}/PCLUNT/${CONDNON}（${ProjDeR}和${FutNeX当然是EX）。在Poad下拉列表中，应该有一个选项“SosiToopOutlook文件”（没有路径或文件），如果选择了“生成pCurt依赖文件”，那么它将创建文件${PrimeDIr}/${CutNe}}。在执行“pCLinux这个项目”时，LNT${Projdidi}/${No.LNT-CMAC.HORD，它看起来是这样的（格式为%%（%F:%L:%）%%%:%-M -宽度（0，4）”-IC//PCLUNT/PC LIT 9 /LNT/“AU-MISRA1.LNT${Projutdir}/${CONNED} O-COYXC16.LNT”${ProjDeR}/${FutNo}}包含的“Co xx16.nt”（${StudioDiR}当然扩展到绝对路径）-I.---I.SSLSRC-I.SSLH选项3在选项下拉列表中应该有一个选项“SosiToopOutlook文件”，它可能指定一个路径，它可以包括宏${CONDNOR}，${PrimeDIr}，因此指向Ry路径为“CopyOpToopFrm”可以看起来像这个${PrimeDIr}//pCurt/${CONDNON}，因此当执行“生成pCLinux依赖文件”时，它将创建文件${PrimeDIr}//pCurt/${FuNNID}/包含路径。他的项目“被执行”，它看起来是这样的（对于XC16编译器）${Projdidir}//pCurt/${NoNord}/COYXC16.LNT-I $ {ProjiDIr}//PcLtT/${FuNNID}（${Projdidir}和${CONDATE当然扩展到绝对路径）-I.\I.\sILSRC-I.SSLHB）当“生成pCLinux依赖FI”时LES“正在执行并创建包含PAtiP-PATH”。LNTIT应该包括在“文件”中，在“右击一个项目并点击”“定义一个配置”和“生成PCLUT依赖文件”时，定义为“定义公共宏”C的那些定义。创建包含PATIP-PATH.LNTIT的文件应该包含在“右击一个项目并点击编译器（例如“XC16 GCC”）-& GT；预处理和消息”中定义的“定义C宏”A.1和A.2中有硬编码的PasSA 3。这样做是很好的，可以将pCLinux特定的文件保持在一起，它们自然地包含在一个存储库中。当然，用户必须下载/复制COXX16.LNT文件并在愿望之后修改它。我个人将投票赞成A.3和B。



      以下为原文

   
The follwoing is a which list of how I would like to see how the PCLint plugin works
Our projects have several targets (configurations) which makes the handling of
PCLint a little difficult, also, the PCLint plug in is missing some defines
We also use repositories, such as SVN and Git

The following suggestions tries to address the problem we are facing when suing multiple
configurations and have configuration specific macros


${ConfName}, ${ProjectDir} refers to the macro visible if you
right click on a project and click on "Building" for a configuration.


A)
Tools -> plugin -> Embedded->PCLint


Option 1
In the Options drop down list there should be an option "ConfigurationOptionFile"
(no path or file is given)

If this is chosen then when the user do "Generate PCLint Dependency Files"
It will create a file in
${ProjectDir}/pclint/${ConfName}/include-path.lnt
${ProjectDir}/pclint/${ConfName}/lint-cmac.h

This directory should be included when doing "PCLint this project"
and when doing "PCLint this project" is executed it will look like this (for the xc16 compiler)
${ProjectDir}/pclint/${ConfName}/co_xc16.lnt
-i${ProjectDir}/pclint/${ConfName}      (${ProjectDir} and ${ConfName is of course expanded to absolute path)
-i..Include
-i..SSLsrc
-i..SSLh


Option 2
In the Options drop down list there should be an option "ConfigurationOptionFile"
(no path or file is given)

If this is chosen then when the user do "Generate PCLint Dependency Files"
It will create the files
${ProjectDir}/${ConfName}_include-path.lnt
${ProjectDir}/${ConfName}_lint-cmac.h

and when doing "PCLint this project" is executed  it will look like this (for the xc16 compiler)
-format=%(%f:%l: %)%t %n: %m
-width(0,4)
"-iC:/pclint/PC-lint 9.0/lnt/"
au-misra1.lnt
${ProjectDir}/${ConfName}_co_xc16.lnt
"${ProjectDir}/${ConfName}_co-xc16.lnt" (${ProjectDir} is of course expanded to absolute path)
-i..Include
-i..SSLsrc
-i..SSLh



Option 3
In the Options drop down list there should be an option "ConfigurationOptionFile"
And it is possibly to specify a path which can include the macros
${ConfName}, ${ProjectDir} so the directory path to "ConfigurationOptionFile" could look like this
${ProjectDir}/../pclint/${ConfName}

So when the "Generate PCLint Dependency Files" is executed it will create the files
${ProjectDir}/../pclint/${ConfName}/include-path.lnt
${ProjectDir}/../pclint/${ConfName}/lint-cmac.h

and when doing "PCLint this project" is executed it will look like this (for the xc16 compiler)
${ProjectDir}/../pclint/${ConfName}/co_xc16.lnt
-i${ProjectDir}/../pclint/${ConfName}  (${ProjectDir} and ${ConfName is of course expanded to absolute path)
-i..Include
-i..SSLsrc
-i..SSLh


B)
When "Generate PCLint Dependency Files" is executing and creating the include-path.lnt
it should include in this file those defines that is stated in
"right click on a project and click on "Building" for a configuration" and those who is defined  
on line "Define common macros"

C)
When "Generate PCLint Dependency Files" is executing and creating the include-path.lnt
it should include in this file those defines that is stated in
"right click on a project and click on compiler (such as "xc16-gcc") -> Preprocessing and messages"
in line "Define C macros"



A.1 and A.2 have hardcoded paths
A.3 is most flexible

B is really desirable
C would be nice as well


By doing this it is possible to keep PCLint specific files for configurations together and
they naturally is included in a repository.
Of course, a user have to download/copy the co-xc16.lnt file and modify it after desire.


I personally would vote for
A.3 and B