git and workspace

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

git and workspace

2,376件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by charchar on Wed Mar 04 19:22:11 MST 2015
Hi guys,
I have a workspace with 4 projects.  I use git as a source code respository.  All of the source files and .project and .cproject files for each project are in git.  In other words, my git repository looks just like my lpcxpresso workspace.  

Like me, the people I collaborate with use git but are not too familiar with lpcxpresso.  I want them to be able to clone the git repository and see/use the workspace as I have it configured.  But after cloning the repository, it seems that when you point the workspace in lpcxpresso to the directory that contains the projects, the projects don't show up in lpcxpresso. 

The only way I've found to transfer a workspace to another computer is to export the workspace as a set of projects and then import it.  But exporting and importing doesn't lend itself well to a git repository. 

There are several files in the .metadata directory.  If I include those in the repository (there are lots of files, many of them are binary) I'm pretty sure my collaborators will see the projects in the workspace as I see them.  But this just seems wrong.  Does anyone have advice for me and my collaborators?

thanks!
0 件の賞賛
返信
8 返答(返信)

2,193件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Nov 10 09:25:42 MST 2015
For the sake of clarity, LPCXpresso IDE under Windows does not use cygwin. We do use msys (which is related but not the same thing). If you are seeing cygwin messages, that would indicate that you are getting some form of clash with something else installed on your PC.

Regards,
LPCXpresso Support
0 件の賞賛
返信

2,193件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by thommaughan on Tue Nov 10 09:03:59 MST 2015
I did read the FAQ and burnt many frustrating hours and eventually installed the latest version of LPCxpresso (moved from 7.4 to 7.9.2).   I also freed up some disk space from 9GB to 30GB.   I'm wondering if some of the build tool cygwin problems were due to low disk space on Win 7.    The gdb crash persisted even after freeing up the disk space and I'm not going to spend time right now on this one.

The good news is my code compiled with no problems moving to the new version and I'm back moving forward on getting the hardware drivers written (I've got a deadline and time pressure).

I did not try the project export, that might be the important step I'm missing, thanks!    I will be setting up a server when I get past a delivery commitment and will give the eGit plugin a try.

Thanks,

Thom
0 件の賞賛
返信

2,193件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by vtw.433e on Mon Nov 09 02:07:09 MST 2015
1. For the Cygwin problem, did you read this FAQ?
https://www.lpcware.com/content/faq/lpcxpresso/virtual-alloc-pointer-null-error

2. You need to share *projects* and not workspaces.
- When using Git, SVN or any other source control system, you checkin/check-out each project. The proper way to use Git in Eclipse is to use the eGit plugin. See https://www.lpcware.com/content/faq/lpcxpresso/using-version-control-within-ide
I- f not using Git etc, you *export* a project and *import* it into the other workspace. See https://www.lpcware.com/content/faq/lpcxpresso/how-importexport-projects
0 件の賞賛
返信

2,193件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by thommaughan on Sun Nov 08 17:09:20 MST 2015
I too am not a fan of eclipse, especially after running into the problems of LPCXPRESSO on windows.   Everything has been working for months, and then suddenly I'm stopped cold.    I've got 32GB of RAM, but GDB cygwin runs out of memory.   Rebooting doesn't fix the problem and upgrading from LPCXPRESSO 7.4 to 7.9 was just a waste of time - same error.    Yes, we can probably blame windows at this point, but eclipse and it's weirdness is making matters difficult

I moved to another laptop, this with 16GB of RAM.   Now I'm struggling with copying the workspace and files from one machine to another.   Unfortunately I've not got everything pushed into git, but that might just complicate things further.    Anyone have a simple recipe for zip of an entire workspace and copy to another PC?    I'm trying Import, but not getting it.     I'm unfortunately coming from an IAR experience base.
0 件の賞賛
返信

2,193件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by charchar on Thu Mar 05 09:30:02 MST 2015
Yeah, I must admit that I'm not a fan of eclipse.  I find it to be overwhelming.  It's powerful, sure, but I get lost in it.

Running git inside eclipse doesn't appeal to me.  Running git in eclipse would be more compelling if all I did was develop firmware in lpcxpresso (but that's not the case, so I necessarily need to use another git tool).

0 件の賞賛
返信

2,193件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Thu Mar 05 08:30:54 MST 2015
I really would suggest you use eGit. It is very nicely integrated and so it becomes a natural part of your workflow. Much much easier than running git as a separate tool.
0 件の賞賛
返信

2,192件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by charchar on Thu Mar 05 08:09:05 MST 2015
Yeah, I figured out the easiest method (and I appreciate the egit suggestion, but setting up egit, and learning/usring another git tool doesn't sound like the easiest option) --- after cloning a git repository, you can import existing projects without too much fuss by going into file->import, selecting "Existing projects into workspace" under "general" and then pointing the root directory to the directory in your git tree --- the one with the projects --- and then selecting/checking all of the projects. 

It would be nice if there were a workspace file that listed the projects (so you wouldn't have to construct the workspace like I described).  And the reason this would be nice is because the process would be automated and would prevent the "I'm getting this error" because the user forgot to check the xyz project when importing.  It's common for a piece of firmware to include multiple projects with cross-dependencies. 

I suspect this is an oversight by Eclipse (nothing to do with lpcxpress), but workspaces should have an assocated .workspace descriptor file. 

0 件の賞賛
返信

2,192件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Thu Mar 05 00:23:36 MST 2015
Use the eGit eclipse plugin, which gives you gite access directly from within the LPCXpresso IDE. Then checkout the projects.
http://eclipse.org/egit/download/

Never check in the .metadata repository.
0 件の賞賛
返信