怎么用项目中的替换默认和声文件

您可以向项目添加您的版本并删除它们。但是每次运行MHC，你都必须再次做。有些人写了一些东西叫麦克帕彻。你可以看看这是否有助于张贴在某个地方。



      以下为原文

    You can add your version to the project and delete theirs. But then you will have to do it again every time you run MHC.
Some wrote something call mcPatcher. You can see if that would help it is posted here somewhere.

V2.0xCube作为一个独立的项目。所有的和声文件都被复制到App文件夹结构中。如果/再运行MHC，你将显示出每个文件的差异。



      以下为原文

    V2.0x
Create as a standalone project. All the harmony files are copied into the app folder structure.
Then if/when you run MHC again you will be shown a diff for each file with changes.

有趣。如果我曾经设法迁移到V2.xx，我需要看看。目前，我仍然与大部分废弃的1.XX版本。



      以下为原文

    Interesting.
I will need to look at that if I ever manage to migrate to V2.XX.
For the moment I am still with the mostly abandoned 1.XX version.

是的，我希望他们把这样的特性添加到2.0x！这将使一个项目作为一个Git回购更容易控制！维克斯



      以下为原文

    Yay, I was hoping they added a feature like that to 2.0X! That will make controlling a project as a Git Repo much easier!
 
John Vickers

我在2.01B中尝试过，但是在我的项目中有一些丢失的文件，所以我提出了一张票。我不知道它是否已经修好了，还没有收到票的通知。



      以下为原文

   
I tried that in 2.01b but there were some missing files in my project so I raised a ticket.  I donj't know if it's fixed yet, haven't had notification from the ticket.

我也使用独立的选项。可能是最干净的解决方案，如果你必须对框架进行修改。但你是对的，这个独立的机制有几个错误，忘记复制文件，或者将文件复制到错误的位置。然而，通常这是很容易修复的。一种方法是找出它忘记复制的文件，在原始的和声框架目录中搜索它，并将它复制到你的项目目录中可能是的地方。通常它在同一个文件夹路径中，但有时文件需要向上移动一些目录。如果请求一个去激活模块的头文件，那么您也可以尝试启用该模块，生成代码以使文件被复制，然后再次禁用该模块。这个文件不会被删除。V2.00的一些bug在这个线程中被描述：HTTP://www. McCHIP.COM/FUMMS/FUNDSPE/954



      以下为原文

    I'm also using the standalone option. Probably the cleanest solution, if you have to make modifications to the framework. But you are right, this standalone mechanism has several bugs and forgets to copy files, or is copying them to the wrong location. However, usually this is very easy to fix.
 
One way is to just find out which file it has forgotten to copy, search for it in the original Harmony framework directory and copy it to the place in your project directory where it is probably supposed to be. Usually it is in the same folder path, but sometimes the files need to move a few directories up.
 
If a header file for a deactivated module is requested, then you can also try to enable the module, generate code to make the file getting copied, and then disable the module again. The file won't get deleted.
 
Some of the bugs for v2.00b are described in this thread: http://www.microchip.com/forums/FindPost/954278