![]() |
WindRiver & Git - Makefile
Hi all,
Been playing with using C++ to program the robot instead of LabVIEW and I've been using Git as my VCS. Things are working fine except for the Makefile. I haven't programmed in C++ for years so I'm not sure if this is how things are done or what. I noticed the makefile has a lot of exact paths (C:/Users/Tanner/blah/blah) which doesn't work too well in a VCS unless everyone has my computer (doubtful) and they don't want to compile. So what I'm asking is there a way to modify the Makefile so it can play a bit more nicely with Git? -Tanner |
Re: WindRiver & Git - Makefile
Why are you putting the makefiles under version control? If you are using WindRiver you don't even need to know what makefiles are.
Just put the actual code under control. |
Re: WindRiver & Git - Makefile
Quote:
Code:
C:\windriver\vxworks-6.3\host\x86-win32\bin\make.exe: *** No targets specified and no makefile found. Stop.-Tanner |
Re: WindRiver & Git - Makefile
what if you create a project on each machine that will be using the versioning to create the makefiles, then import the versioned files into the project?
|
Re: WindRiver & Git - Makefile
Quote:
|
Re: WindRiver & Git - Makefile
Quote:
I'm confused how WindRiver is going to compile fine without the makefiles. Maybe I'm importing the project wrongly into WindRiver, but I'm not seeing how it can be done otherwise. Quote:
How do people using SVN manage the makefile? -Tanner |
Re: WindRiver & Git - Makefile
Quote:
|
Re: WindRiver & Git - Makefile
Quote:
Quote:
EDIT: found EGit, a git plugin for eclipse/windriver: http://www.eclipse.org/egit/download/ I would import from the git source when it is installed |
Re: WindRiver & Git - Makefile
Quote:
Quote:
I'll have to try the EGit when I get home. Might give me better results. -Tanner |
Re: WindRiver & Git - Makefile
I don't have the computer with me right now that I use for FIRST development, so I don't know the specific instructions, but I'll try from memory.
We use SVN to host just our code. No makefiles, no project files, just .cpp & .h. Each developer then creates a project using one of the sample projects as a base, cleans out all the default code files, renames the project, etc. Then we import (I believe that's the correct menu option, but I'm not certain) the directory that contains all our SVN code. Our code is then buildable. When someone adds or removes a file, it's necessary to refresh the file browser tree. |
Re: WindRiver & Git - Makefile
I've done it on SVN with just .h and .cpp files. Here is a procedure I wrote a couple of years ago for the guys on my team (I updated it a bit, but there may be mistakes).
We use TortoiseSVN, hence the Windows Explorer right-click-menu bit. Quote:
|
Re: WindRiver & Git - Makefile
Actually, there is an option to create a project from an SVN repo. I think it's Import->SVN. It's what we use, and it works well
|
Re: WindRiver & Git - Makefile
Quote:
or you could use New>Project>SVN>Checkout Projects From SVN We used this also |
Re: WindRiver & Git - Makefile
Quote:
Thanks all. Edit: Though it doesn't work too well with branches (cause when you go back to the same branch, they won't exist anymore thus WindRiver whines). Not sure if there is a way to get git to not delete those files. -Tanner |
| All times are GMT -5. The time now is 12:23. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi