|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Connecting Eclipse to Github
I was able to figure it out. Turns out I was going about it backwards. I was trying to directly import a Git project, which in this case was last years code, and then somehow convert it to a WPIlib project. You actually need to do it the other way around. Create the WPIlib project, then under the Team section of the project, create a repository and then link that repo to github. Works like a dream now. I can give more precise instructions if anyone is interested.
|
|
#2
|
||||
|
||||
|
Re: Connecting Eclipse to Github
Quote:
|
|
#3
|
|||
|
|||
|
Re: Connecting Eclipse to Github
I have a feeling it was because of the nature of eclipse. When you import a project directly from a Git repo, it is only going to pull what was in that repo. I did not have the ability to do a reindex or anything like that to even add in the includes. I think it is intended for fully self-contained codesets that do not include any additional components on your computer, which in this case was the WPIlib 2017 code. I had to simply reverse the process and start as a wpilib codeset, then add the repo onto it to update the needed files. In this case, we don't need to include the includes as it is a needed prereq to even work with the code in the first place.
|
|
#4
|
|||
|
|||
|
Re: Connecting Eclipse to Github
Quote:
|
|
#5
|
||||
|
||||
|
Re: Connecting Eclipse to Github
Quote:
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|