CODEWITHSUNDEEP
ceclipsearmdirectory
Tedi
Tedi

Reputation: 202

Eclipse: C project folder structure

I have an existing C project with the following folder structure:

When i launch Eclipse and create a new project the root project folder is polluted with:

Also the parent folder with:

A want to continue use Eclipse as an C IDE with a my custom makefile (or not) but I want all Eclipse related files and folders to be put inside the proj directory. I need Eclipse to debug ARM targets.

Is it possible? If not what is the next best thing?

I made a promise to myself to start a smooth transition from IDEs to vim with a custom makefile. I still need Eclipse to help me for debugging. One step at a time...

Upvotes: 0

Views: 1125

Answers (1)

howlger
howlger

Reputation: 34255

The files .project and .cproject (and the .settings folder if it exists) contains the Eclipse-specific (general and C/C++) project configuration.

The .metadata folder is a kind of cache/temp folder (to store error/warnings markers, local file history, etc.) and also used to store your workspace preferences (most of Window > Preferences).

Files in a project are tracked and can cause changes in the .metadata folder. If the .metadata folder would be located in a project, this could end in an infinite loop.

You could use the workspace folder of Eclipse (which contains the .metadata folder) as part of your overall project folder and link instead of copy all files and folder that you want to see in Eclipse or that are required by Eclipse into your Eclipse project (you can also mark some files and folders as derived to stop them from being tracked and to make them less visible in Eclipse).

Note, do not share or move the .metadata folder (and derived resources). In contrast, .project, .cproject and .settings are intended to be shared.

Upvotes: 1

Related Questions