Home » Eclipse Projects » EGit / JGit » What is an equivalent of "Build"(project) in "Git repositories " perspective ?(git perspective )
| | | | |
Re: What is an equivalent of "Build"(project) in "Git repositories " perspectiv [message #1816683 is a reply to message #1816682] |
Mon, 04 November 2019 22:20 |
Thomas Wolf Messages: 576 Registered: August 2016 |
Senior Member |
|
|
Looks like you already have the NanoVNA project in your Eclipse. In the screenshot it says "Folder already imported".
NanoVNA is C and Python, and presuming we're talking about https://github.com/ttrftech/NanoVNA , the repository has a submodule. I'll assume you're using a C/C++ Eclipse, and that you have cloned the NanoVNA repository recursively, so that this submodule (in folder ChibiOS) is properly set up.
Things will really be simpler if you just forget about that Git perspective for now. Just switch back to the normal C/C++ perspective. You should have on the left side a view (titled "Project Explorer") showing your projects. One of these should be NanoVNA. Most probably it also shows a decoration like "[NanoVNA develop]".
The github repository does not include any setup for Eclipse so it may be necessary to configure that project manually as a C/C++ project. I cannot help you with that; I've never done C development in Eclipse. Setting up a C/C++ project will probably involve defining or selecting a compiler toolchain. You'll probably have to choose or set up your cross-compilation toolchain. Probably there's an item at the bottom of the context menu on the NanoVNA project folder that says "Configure->C/C++ project" or some such. Once that project is set up as a C/C++ project in Eclipse, it should be built automatically.
If you want to see the git repository, too, in the C/C++ perspective, just open the Git Repositories View as explained above.
When you make changes to files, the changed files should be shown in the Project Explorer prefixed with a "> ". Choose "Commit..." from the context menu and the Git "Staging View" will open, where you then can compose your commit.
But it seems to me you need someone who can help you with the details of configuring and building a C/C++ project in Eclipse. You already got as far as cloning and having the Eclipse project imported.
The git repository is not the Eclipse project. In your case it may seem so, since you will, in Eclipse, treat the whole directory tree as one project. But if you look for instance at the EGit repository itself (mirror at https://github.com/eclipse/egit ), you can see that there are many Eclipse projects: all those org.eclipse.egit... directories are Eclipse projects. Each of them has an Eclipse .project file, and even a sub-directory .settings storing Eclipse-specific configurations.
NanoVNA has neither, so you have to configure the Eclipse setup yourself. (NanoVNA does have .vscode sub-directory; that contains setup particular to Visual Studio. But that doesn't help you for Eclipse.)
As far as EGit is concerned, there's really not much more we could help you with. The people in the C/C++ Eclipse (CDT) forum probably can help you better with problems about how to build NanoVNA.
|
|
|
Re: What is an equivalent of "Build"(project) in "Git repositories " perspectiv [message #1816726 is a reply to message #1816683] |
Tue, 05 November 2019 16:44 |
Helen Keller Messages: 173 Registered: June 2019 |
Senior Member |
|
|
Thomas,
quite by accident I found that when I use "Project explorere" tab/ perspective I can eventually add new C files to my local repository.
Thru "staging" and then "push" and commit .
I had to pay attention to "commit" it defaulted to original git repository !
Close call!
Also "synchronize" perspective shows to be helpful.
All is left is to "Build" - to use C/C++ terminology.
Of course I have to figurine out how to use cloned "makefile" instead of regular "make" generated by C?C++ "Build" menu.
Thanks for helping me, I realize this mess is a combination of C and EGit so it really does not fit to neither forum.
[Updated on: Wed, 06 November 2019 14:34] Report message to a moderator
|
|
| | |
Re: Wanted Documentation for EGit "import project from file system or archive" form/ dial [message #1816782 is a reply to message #1816780] |
Wed, 06 November 2019 19:41 |
Helen Keller Messages: 173 Registered: June 2019 |
Senior Member |
|
|
Ed,
if what your are saying that the "stuff" I cloned from github , and I think I will not call it "project" - in Eclipse terminology, just stuff , needs to be reconfigured so CDT will make a "normal " Eclipse project out of it, it then make sense.
I am not sure I can figure CDT file structure myself, so it makes more sense to ditch Eclipse, in this case , and just continue using CLI.
I actually run CLI make on the original "stuff" and it completed with one easy to fix error.
Little disappointing with EGit usefulness, mainly lack of instructions / documentation.
|
|
|
Re: Wanted Documentation for EGit "import project from file system or archive" form/ dial [message #1816795 is a reply to message #1816782] |
Thu, 07 November 2019 06:01 |
Ed Merks Messages: 33216 Registered: July 2009 |
Senior Member |
|
|
Well, the general problem is of course that you're having to learn many things at once. You have to learn Eclipse, you have to learn and understand the "workspace" model for "projects, you have to learn how CDT integrates with Eclipse's workspaces to support C/C++ projects, and you have to learn how EGit works (and hopefully you already know Git, otherwise you have to learn that as well). All powerful technologies are complex, or most certainly feel that way before your learn them. There exists documentation and tutorials for all these things. Looking at the downloads page, the most recent CDT package is downloaded more that 200,000 times (and that doesn't include the ones installed by the Eclipse Installer), so a great many people are using this. No doubt a great many of them are using it in combination with EGit (like I do). But definitely you're right, a Git clone is not an Eclipse project; once cloned locally, it's just a bunch of folders and files, somewhere in which lurk your projects (or what could/should become your projects).
One important thing you will lose by sticking to the command line, which is kind of essential and in my opinion makes all the effort to learn CDT worth while, is the interactive debugger. Of course you also lose all the other nice IDE integration, such as navigation from the usage of a symbol to the definition/declaration of that symbol, not to mention the awesome features of EGit. But it's a trade-off between an investment in learning versus a return on investment in productivity. Certainly I was cursing when trying to get CDT to compile my first project; it's 100 times more complicated than setting up a Java project, so I have felt your pain.
I'm just feeling the need to point out that additional documentation is not likely to appear out of thin air. I know from experience that even if one provides documentation, people don't read it because they expect everything to be self evident. (And I"m not saying that is the case for you, I'm just saying that it just makes providing documentation less motivating knowing that you can stick in under someone's nose, and they won't read it first; and I mean that literally in a dialog with a spinning question mark button that people don't click and read). I never felt that EGit lacked documentation, but then I knew all the other aspects of Eclipse and was switching from using CVS, so it was mostly Git itself that I needed to learn, and that seemed horribly complicated at the time, so I was cursing it's "unnecessary complexity" which of course has evolved into loving it's incredibly rich set of features over time.
Personally Google is my best friend. It always answers instantly and with billions of people on the planet, someone else has likely answered this question already.
Good luck with whatever path you choose to follow.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| | | | | |
Goto Forum:
Current Time: Fri Sep 20 18:09:08 GMT 2024
Powered by FUDForum. Page generated in 0.05507 seconds
|