V1.45在MCC中没有自动更新库吗？

在过去的版本中，MCC并不是向后兼容的。我不知道哪些版本与哪个版本兼容，或者未来的计划是什么。



      以下为原文

    In the past versions of MCC were not backwards compatible. I do not know what version are compatible with which, or what Microchips future plans are.

谢谢你，NKurzman。因此，当有一个新的MCC，我会注意到哪些项目是用当前的项目创建的。有人知道图书馆吗？它们假设自动更新吗？重要的是在版本窗口中尊重“核心XXX”的构建并确保库和核心匹配吗？如果它们匹配，那就意味着没有问题了吗？那么核心呢？什么是核心，它与“MCC”有什么不同？为什么不选择给定MCC版本的最新内核正在运行？



      以下为原文

    Thanks @NKurzman. So when there's a new MCC I'll note which projects were created with this current one.
 
Anyone know about the Libraries? Are they suppose to automatically update? Is it important to respect the "built from Core XXX" designation in the Versions window and ensure that Library and Core Match? And if they do match does that mean there'll be no problems?
 
And what about the Core? (What is a Core anyway and how does it differ from "MCC"?) Any reason not to choose the most recent Core for the given MCC version one is running? 

当我们发布MPLAB-X插件的新版本时，我们将最新的库捆绑在一起发布。当插件有一个新版本时，IDE可以为您更新，但是我们做的临时版本通常包括新的部分支持，而不是插件版本，这是McC8的外围库V1.55的情况。这是一个创建的库，如果你愿意的话，它可以让你升级到一个后来的版本。建议你把所有的东西都升级到最新版本，但是如果对你来说重要的是，这个工具生成的代码和以前一样，甚至几年后。然后，你可以选择粘贴工具的版本，就像上次你使用它的时候一样。我可以看到我们真的应该拿出一个文档来描述所有这一切。请让我知道如果有一些问题没有回答，我可以尝试澄清。



      以下为原文

    We bundle the latest libraries with the release when we make a new release of the MPLAB-X plugin. When there is a new version of the plug-in the IDE can update this for you, but we do interim releases usually including new part support more often than plug-in releases, this was the case with V1.55 of the peripheral libraries for MCU8.
 
The latest version of MCC will load your project with the version of the libraries which it was created with and gives you the option to upgrade to a later version if you want to.

It is recommended that you always upgrade everything to the latest version, but if it is important to you that the tool generates the same code which it did before, even years later, then you have the option of sticking with the version of the tool as it was back then when you last used it.

I can see that we really should bring out a document to describe all of this. Please let me know if this leaves some questions unanswered and I can try to clarify.

非常有帮助的。这几乎是所有答案。有一件事让我忘了，“核心”到底是什么？“图书馆”似乎是关于如何为外围设备创建代码的，并且可能是特定的。“MCC”本身是在MPLABX中运行的整体软件框架，并处理部分配置，然后通过引用“库”生成代码。如果这是正确的，那么“核心”是如何适应的呢？它是做什么的？升级后的“核心”会导致输出代码的改变，就像更新的“库”可能吗？抑或只是提高效率？（我认为升级后的MCC可能会导致MPLAB环境用户体验到软件界面的变化？）再次感谢。



      以下为原文

    Extremely helpful @cobusive.
 
That's nearly everything answered. 
 
One thing that escapes me is, what exactly is the "core"? It would seem that the "Library" informs on how to create code for peripherals and may be part-specific. That "MCC" itself is the overall software framework that runs within MPLABX and handles part configuration and then generates the code by referring to the "Libraries". If that's right, how does the "core" fit in? What does it do? Can an upgraded "core" result in changes to output-code just as an updated "library" might? Or does it just improve efficiency? (I take it that an upgraded MCC perhaps results in changes to the MPLAB environment user experience, to the software interface?)
 
Thanks again.

对的。库是可以定义MCC支持的部分、包含在这些部分中的硬件外设和基于这些定义生成的固件的内容。并非所有的库都包含设备信息；有些库只包含固件。库是内容。核心是提供服务的软件框架。它协调代码的生成，提供库之间的机制通信，帮助他们管理状态以存储到公共的.MC3文件以及撤消/重做操作，管理软件模块的生命周期，因为它们是从用户的项目中添加/移除的，等等。第三件是主机还是GUI。这将系统连接到环境。在MPLAX中，主机是插件。在MPLAB XPress中，主机是一个基于JavaFX的工具。（我们还有两个版本供内部使用。）例如，一个主要用于测试的命令行主机。因此，“MCC”实际上是三个东西的组合：核心，它定义了用于库和主机的公共服务。它是协调器。主机将内核连接到它的环境中，对库是不可知的。提供内容的库和主机不可知。当你更新MCC插件时，你实际上正在更新主机。这可能与内核的更新和一些库的更新捆绑在一起，但这不是必需的。核心不生成代码，因此它不会直接影响生成的代码。然而，它确实为图书馆提供服务，而且，由于图书馆依赖于这些服务，图书馆所产生的内容可能受到影响。例如：如果图书馆A能够与图书馆B对话，他们可能决定协调他们的固件。如果提供通信机制的核心服务不存在，则库将无法协调，因此固件将是不同的。如果库A决定这是不可接受的，它可以选择要求最小的核心版本，因此它总是能够访问该通信机制。这是版本窗口显示的兼容性信息。



      以下为原文

   
Correct. The libraries are the content that (may) define the parts that are supported by MCC, the hardware peripherals contained in those parts, and the firmware that can be generated based on those definitions. Not all libraries contain device information; some contain only firmware.
 
Libraries are content.
 

The core is the software framework that provides services. It coordinates generation of code, provides a mechanism communication between libraries, helps them manage state for storing to a common .mc3 file as well as undo/redo operations, manages the life-cycle of software modules as they are added/removed from the user's project, and so on.
 
The third piece is the host or GUI. This connects the system to the environment. In MPLAB X, the host is the plugin. In MPLAB Xpress, the host is a JavaFX-based tool. (We have a couple other versions that are for internal use. For example, a command-line host primarily used for testing.)
 
So "MCC" is actually the combination of three things:

• The core which defines the common services for libraries and the host. It is the coordinator.
  
• The host which connects the core to into its environment, and is agnostic to the libraries.
  
• The libraries which provide the content, and are agnostic to the host.
  

When you update the MCC plugin, you are actually updating the host. This likely comes bundled with an update to the core and an update to some libraries, but it's not necessary.
 

The core does not generate code, so it does not directly affect the code that is generated. However, it does provide services to libraries, and in so far as the library is dependent on those services, the content generated by the library may be affected.
For example: If library A is able to talk to library B, they may decide to coordinate their firmware. If the core service providing the communication mechanism doesn't exist, the libraries will not be able to coordinate, so the firmware will be different.
If library A decides this is unacceptable, it may choose to require a minimum core version so it always has access to that communication mechanism. This compatibility information what the versions window is displaying.

谢谢@ BurkydaviSon。现在一切都清楚了。



      以下为原文

    Thanks @burke_davison. 
 
All clear now.