I want to create a complete new workspace with one project and git support.
I created the workspace, then the project, then clicked on "Set repository path" ... nothing.
How do I get CodeLite to make this a local git repository, that I can later push to GitHub?!
Do I have to run "git init" in the Workspace folder and add the files manually, commit and push to github first?!
If so, which CodeLite files can be ignored?!
P.S. Using V 9.1.1 on Windows 10. Since Version 9.1.1 I get the following warning when I create a new Workspace/Project (see attachment) => Building creates the missing compilation.db ... can I safely ignore this warning?
Using Git Plugin Question
-
- CodeLite Enthusiast
- Posts: 15
- Joined: Fri Sep 05, 2014 9:02 pm
- Genuine User: Yes
- IDE Question: c++
- Location: Germany
- Contact:
Using Git Plugin Question
You do not have the required permissions to view the files attached to this post.
- eranif
- CodeLite Plugin
- Posts: 6375
- Joined: Wed Feb 06, 2008 9:29 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: Using Git Plugin Question
The git plugins basically uses an existing repo..
The normal flow is:
- Clone an existing repo
- Set the repo path in CodeLite
You can ignore this message
Eran
The normal flow is:
- Clone an existing repo
- Set the repo path in CodeLite
You can ignore this message
Eran
Make sure you have read the HOW TO POST thread
-
- CodeLite Enthusiast
- Posts: 15
- Joined: Fri Sep 05, 2014 9:02 pm
- Genuine User: Yes
- IDE Question: c++
- Location: Germany
- Contact:
Re: Using Git Plugin Question
Thanks for the quick answer. Did it this way and it seems to work.
I guess I have to commit all the files inside the .codelite folder, correct? Or can it be ignored? (I am thinking about working in a team)
Edit: What is the best way to maintain dependencies like dynamic libraries that need to be copied to the debug folder to execute the program?
I though about creating a folder outside of codelite "packages" and add a Post-build event to the project that relies on this folder. Of course add this folder to GIT.
I guess I have to commit all the files inside the .codelite folder, correct? Or can it be ignored? (I am thinking about working in a team)
Edit: What is the best way to maintain dependencies like dynamic libraries that need to be copied to the debug folder to execute the program?
I though about creating a folder outside of codelite "packages" and add a Post-build event to the project that relies on this folder. Of course add this folder to GIT.
- eranif
- CodeLite Plugin
- Posts: 6375
- Joined: Wed Feb 06, 2008 9:29 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: Using Git Plugin Question
all the files inside the .codelite folder can be ignored - the files inside this folder contains data relevant to your environment onlyAkronym wrote:I guess I have to commit all the files inside the .codelite folder, correct? Or can it be ignored?
In addition, don't commit any generated makefiles produced by CodeLite (assuming that you are using CodeLite for C++)
In general, a folder with a dot prefix, can be ignored
Eran
Make sure you have read the HOW TO POST thread
-
- CodeLite Enthusiast
- Posts: 15
- Joined: Fri Sep 05, 2014 9:02 pm
- Genuine User: Yes
- IDE Question: c++
- Location: Germany
- Contact:
Re: Using Git Plugin Question
Okay thanks. I tried deleting .codelite files and makefiles and saw, that it does not really matter if they got deleted.
But I recognized that I have to change all the paths to relative paths if I want to work in a team (Linker Libs etc.)
Thank you very much!
But I recognized that I have to change all the paths to relative paths if I want to work in a team (Linker Libs etc.)
Thank you very much!