在Creator 3.0中产生一系列错误

在新的3版本中打开先前编译在2.2中的项目。
清洁和建造项目存在一系列错误，即UnTy8等类型的错误，在CyType中没有发现。
Health.h头文件有一个包含和lt；Proj.H.Gt；其中包括所有其他的调用，包括CyType。
右键单击“包含”和“项目”.H＆GT；选择“转到实现”给出以下COSIL消息：
“找不到实现”。它可能在一个没有可用源的库中。
因此，看起来新的PSoC创建者3没有在必要时找到包含文件。

以上来自于百度翻译

以下为原文
Opening a project that previously compiled in 2.2 in the new 3.0 release.
Clean and build project yeilds a bunch of errors, namely typedefs for uint8 etc. not found in cytypes.h.
device.h header file has an include for where all of the other includes are called, including cytypes.
Right clicking on the #include and selecting "Go To Implementation" gives the following cosole message:
"Unable to find implementation for . It may be in a library for which no source is available."
Thus it would appear that the new PSoC Creator 3.0 is not finding the include files as necessary.

李咏祥

2019-1-17 08:38:11

我简要地看了2to3y0.pNG和包含Debug Test.CyWrk.SaCuvi01.Zip。以下是我到目前为止发现的：
为什么你在Meal.C中的代码资源管理器中看到4个版本的“Dimy1”是因为你用相同的名字创建了变量（行18, 19，在线20中的两个）。编译时可能会产生错误（我们支持PSOC5的几个编译器，它们的错误/警告报告都有点不同）。从传统的“Dimy1”变量中看不到任何错误，因为传统编译器没有被设计为与文本编辑器集成。我们使用一个专门设计的C编译器来支持这种类型的集成。事实证明，这种特殊编译器在执行C规范时比在生成Buffic时实际构建项目时使用的命令行工具要严格得多。而不是编辑器产生过多的错误和警告，有些编译器甚至没有强制执行，我们选择了降低错误和警告级别。文本编辑器将捕获C代码中的一些（但不是全部）潜在问题。我仍然无法在2to3y0.pNG中重现这个问题。

以上来自于百度翻译

   以下为原文
  I've taken a brief look at 2to3_0.png and include_test.cywrk.Archive01.zip. Here's what I've found so far:

The reason why you see 4 versions of "dummy1" in the Code Explorer in main.c is because you created for variables with the same name (lines 18, 19, and two on line 20). The compiler will likely generate an error when you try to build (we support several compilers for PSoC5 and their error / warning reporting are all a little different).
You don't see any errors from the duplicate "dummy1" variables because traditional compilers are not designed to be integrated with text editors. We use a special C compiler that is specifically designed to support this type of integration. It also turns out that this special compiler is actually much more strict in its enforcement of the C specification than the command line tools used to actually build your project when you hit build. Rather than the editor produce an over abundance of errors and warnings, some that your compiler doesn't even enforce, we opted turn down the error and warning levels. The text editor will catch some (but not all) potential issues in your C code.
I still haven't been able to reproduce the issue in 2to3_0.png.

我简要地看了2to3y0.pNG和包含Debug Test.CyWrk.SaCuvi01.Zip。以下是我到目前为止发现的：
为什么你在Meal.C中的代码资源管理器中看到4个版本的“Dimy1”是因为你用相同的名字创建了变量（行18, 19，在线20中的两个）。编译时可能会产生错误（我们支持PSOC5的几个编译器，它们的错误/警告报告都有点不同）。从传统的“Dimy1”变量中看不到任何错误，因为传统编译器没有被设计为与文本编辑器集成。我们使用一个专门设计的C编译器来支持这种类型的集成。事实证明，这种特殊编译器在执行C规范时比在生成Buffic时实际构建项目时使用的命令行工具要严格得多。而不是编辑器产生过多的错误和警告，有些编译器甚至没有强制执行，我们选择了降低错误和警告级别。文本编辑器将捕获C代码中的一些（但不是全部）潜在问题。我仍然无法在2to3y0.pNG中重现这个问题。

以上来自于百度翻译

   以下为原文
  I've taken a brief look at 2to3_0.png and include_test.cywrk.Archive01.zip. Here's what I've found so far:

The reason why you see 4 versions of "dummy1" in the Code Explorer in main.c is because you created for variables with the same name (lines 18, 19, and two on line 20). The compiler will likely generate an error when you try to build (we support several compilers for PSoC5 and their error / warning reporting are all a little different).
You don't see any errors from the duplicate "dummy1" variables because traditional compilers are not designed to be integrated with text editors. We use a special C compiler that is specifically designed to support this type of integration. It also turns out that this special compiler is actually much more strict in its enforcement of the C specification than the command line tools used to actually build your project when you hit build. Rather than the editor produce an over abundance of errors and warnings, some that your compiler doesn't even enforce, we opted turn down the error and warning levels. The text editor will catch some (but not all) potential issues in your C code.
I still haven't been able to reproduce the issue in 2to3_0.png.