Can anyone explain the difference between "Folders", "Folders from Template", and "Source Folders" within a NB managed project. Specifically, with project selected in the Project Explorer, right click, select New->Folder (or "Source Folder", or even "Folder from Template").
I often put code into nested folders, then, under Properties->C/C++ General->Paths and Symbols I need to edit the Includes tab for the C++ Source Files. All this is done with regular folders. Does using a "Source Folder" or a "Folder fromTemplate" change this? If so, I don't see the difference between these 3 folder options... Is there a way to automate the incluson of the include path when you create a folder?
Folders, ve "Source Folders" vs "Folders from Template" ??
-
- Posts: 513
- Joined: Sat Apr 26, 2008 7:14 am
Re: Folders, ve "Source Folders" vs "Folders from Template" ??
"Source folder" is a Java thing - the only code inside the source folder will be build automatically.
There are also Java's "output folder" aka "bin", "library folder" for classes and etc.
I didn't look into Eclipse CDT source code, but looks like CDT treats "source folder" same they as regular folders.
There are also Java's "output folder" aka "bin", "library folder" for classes and etc.
I didn't look into Eclipse CDT source code, but looks like CDT treats "source folder" same they as regular folders.
Hmmm. I never needed to add folders from project source code tree to "Paths and Symbols". What happens when you didn't include folder manually ?Is there a way to automate the inclusion of the include path when you create a folder?
Re: Folders, ve "Source Folders" vs "Folders from Template" ??
It shouldn't be necessary but Under your project properties check the Source Location tab of the C/C++ General ->Paths and Symbols area. Use the Add Folder button and add your /Project/src folder there. I just checked a couple of projects that use multiple nested directories. Some of them specify to the /Project/src level but not below. Others only specify to the /Project level.