完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
经过一些搜索和实验,我想我会问如何连接MPLABX 4.1和现有的Git存储库。我能找到的唯一的选择是创建一个新的。必须有一种方法,否则,任何人都可以共享源代码。
以上来自于百度翻译 以下为原文 Hi After some searching and experimenting I thought I'd ask how to connect MPLABX 4.1 to and existing git repository. The only option I can find is to create a new one. There must be a way otherwise how can anyone share source code. Any one managed this. Thanks Andy |
|
相关推荐
5个回答
|
|
我没有任何问题,包括当前的MPLABX 4.10。团队菜单是用所有命令填充的,并且我连接到Git而没有做任何特别的事情(至少我不记得我已经主动连接)。事实上,你没有描述你真正拥有的问题。你可能会发现你的问题反映在这里:HTTP://www. McCHIP.COM/FUMMS/M910738ASPX.MPLABX帮助(帮助/帮助内容)充满了关于版本控制的信息。
以上来自于百度翻译 以下为原文 I don't have any problems with that, including current MpLabX 4.10. The Team menu is populated with all commands and I'm connected to Git without having done any thing special (at least I don't remember that I have actively connected). Everything works as expected. Actually you do not describe which problem you really have. May be you find your problem reflected here http://www.microchip.com/forums/m910738.aspx The MpLabX help (Help/Help contents) is full of information about version control. |
|
|
|
嗨,谢谢你的回答。我没有描述这个问题,我会描述我在做什么。我有一个项目在我的C驱动器上,一个同事在桌子对面,一个服务器我们都可以看到。我的同事在一个进程上工作,在一个产品上,我在另一个工作。为了保持代码的最新,我想要我的C。OLACGE和MPLABX在服务器上查看相同的Git存储库。我在服务器上创建了存储库,所以我希望我的同事在我推过之后(如果我的术语是正确的)使用相同的代码。经过一些研究之后,我成功地从服务器克隆了这个项目。我的同事机器,现在有两个相同的项目。现在我认为我的问题是,我希望能够把MPLABXs都指向同一个库,并保持这两个项目同步,但我认为我应该把这个项目克隆到我的同事。所以错误的问题是:“这是正确的方法吗?”“?我是新的Git,我用它来保存我自己的更新,但不分享。
以上来自于百度翻译 以下为原文 Hi, Thanks for your response. Instead of describing the problem I'll describe what I'm after. I have a project on my c-drive and a colleage across the desk and a sever we can both see. My colleage works on one proceessor on a product and I work on the other. To keep the code up to date I would like my colleage and my MPLABX to look at the same git repository on the server. I created the repository on the server and so would like my colleage to use the same code by pulling after I've pushed (if my terminology is correct). After some more research I've managed to clone the project from the server to my colleage machine and now have two identical projects. Now I think my issue was that I was expecting to be able point both MPLABXs to the same repository and keep both projects synced but I think I should have been cloning the project to my colleage. So the bug question is "is this the right method"? I'm new with GIT, I use it to save my own updates but not to share. Many thanks Andy |
|
|
|
是的,这听起来像是一个Git,而不是一个微芯片问题,我只有基本的知识。我使用TortoSigit(文件Explorer集成),但是你的问题很可能是独立于客户端软件,与MpLabX没有多大关系。你有你的服务器库,你有你的(两个)。本地存储库,这是一个典型的用例。如果一个第三开发者将使用它,他将使用克隆从服务器到它的本地磁盘,然后从服务器上拉取更新版本,或者提交和推动保存更改。我不认为MpLabX有什么特别的东西。MSDealStudio Studio或TurtoSigeIT。一旦你的存储库从本地磁盘上的服务器上得到,任何客户端都可以毫无问题地使用它。好吧,我想说,到目前为止,没有什么看起来是错误的。如果从服务器上的现有存储库开始,那么首先要将它克隆到本地磁盘上,没关系。当然,这只是起点。除了拉/提交/推,您还可以使用RePo浏览器的概述…
以上来自于百度翻译 以下为原文 Yes, this sounds more like a GIT than a Microchip question and I only have basic knowledge. I use TortoiseGit (File Explorer Integration), but your question likely is rather independant from the client software and has not much to do with MpLabX. You have your server repository and you have your (two) local repositories, that's a typical use case. If a third developer would use it, he would use clone to get it from the server to his local disk and later on pull to get updates version from the server, or commit and push to save changes. I don't think there is anything really specific for MpLabX, MS-Developer Studio or TortoiseGit. Once you have your repository from the server on the local disk, any client can use it without problems. Well, I would say, there is nothing which looks wrong so far. If you are starting with an existing repository on a server, then the first thing is to clone it to your local disk, that's ok. Of course that's only the starting point. Apart from pull / commit / push, you can also use the Repo-Browser for an overview ... |
|
|
|
嗨,非常感谢您的响应。虽然它主要是GIT问题,我希望通过MPLABX完全操作而不需要第三方程序,并且最初找不到方法。这就是为什么我把它看作是一个MPLABX查询。对我来说,这是信息的关键点:即克隆,而不是我最初的想法。
以上来自于百度翻译 以下为原文 Hi, Many thanks for your response. Although it is mainly a GIT issue I was looking to operate wholly through MPLABX without 3rd party programs and originally couldn't find the method. That's why I saw it as an MPLABX query. To me this is the key bit of info: ie the cloning and not pointing as I originally thought. Cheers Andy |
|
|
|
MPLAB项目有一个限制:它们必须位于包含MPLAB和谐安装的同一硬盘上。仅此限制就禁止任何“指向同一项目位置”的方法。克隆知识库是通常的方法。除了这个之外,你还应该确保你的GiTigNORE遵循http://MyCHIPCDeave.com/FAQ:72。通常您在固件目录中创建了“.git”文件夹,但我认为这不是强制性的。强调了更改的文件、插入/更改/删除行的显示和历史特征应该立即在MPLAB X中工作,并且您不需要配置任何一个。NG。也可以使用团队菜单。但要注意的是,MPLAX的内置Git客户端不是很好。也许你想把它与一个外部工具相结合,比如TurtoSigeIT,或者类似的东西。当你在办公桌上办公时,你就不会有太多的麻烦来同步开发。使用不同的分支。你也可以在因特网上搜索“Git工作流”来获取如何组织它的想法。
以上来自于百度翻译 以下为原文 There is a restriction for MPLAB projects: They must be located on the same hard drive that contains the MPLAB Harmony installation. Just this restriction alone is forbidding any approach with "pointing to the same project location". Cloning the repository is the usual way to go. In addition to that you should make sure your .gitignore follows http://microchipdeveloper.com/faq:72 . And usually you create the repository (with the ".git" folder) in the firmware directory, but I think this is not even mandatory. Highlighting of changed files, display of inserted/changed/deleted lines and the history feature should work immediately in MPLAB X and you don't need to configure anything. And also you can use the Team menu. But be aware that the built-in Git client of MPLAB X is not very good. Probably you might want to combine it with an external tool, for example TortoiseGit, or something like that. When you are working desk to desk you won't have much trouble with syncing the development. Just make sure everyone pulls the latest version before (s)he starts working with it or everyone is using different branches. You can also search the Internet for "Git workflows" to get some ideas how to organize it. |
|
|
|
只有小组成员才能发言,加入小组>>
5317 浏览 9 评论
2072 浏览 8 评论
1977 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比?
3248 浏览 3 评论
请问电源和晶体值之间有什么关系吗?PIC在正常条件下运行4MHz需要多少电压?
2285 浏览 5 评论
831浏览 1评论
724浏览 1评论
有偿咨询,关于MPLAB X IPE烧录PIC32MX所遇到的问题
670浏览 1评论
PIC Kit3出现目标设备ID(00000000)与预期的设备ID(02c20000)不匹配。是什么原因
723浏览 0评论
619浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2025-2-1 02:01 , Processed in 1.085056 second(s), Total 85, Slave 69 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号