Automated way to always add specified set of include paths?

[Ridgeglider]

I tend to build projects that have 4 to 6 subdirectories in the main project directory. For the most part, the contents of these directories start the same, but then get slightly modified to meet the needs of a specific application or project. To be compiled and linked, these folders need to be mapped into the include path. I do this by selecting the project, then right clicking properties, then going to the C++/Build topic to the Tool Settings tab, to the Directories sub-item under the GNU C++ Compiler topic. Then, for most of my work, I always add these 4 to 6 additonal (and for me, standard) include paths by clicking the "Add Path" icon, and then the Workspace button and navigating thru a few more OK buttons. Once done, this works well and results in a project directory that is much more manageable. The downside is that I have to add these 4 to 6 path statements every darn time I build a new project!!! Is there a way to write a script that sets them up automatically, say for example as part of a user-defined new project template? Perhaps there a text file that can just be aded or edited somewhere in the .setting folder?

Or maybe I should put this stuff in a library or in the NB system folders although I tend to want it as part of the project? Not sure... Suggestions welcome.

On a semi-related note, where is the guts of the app-wizard? I guesss I'm asking if there's a way to configure a template for a project that is a bit more involved than the app-wizard basics? Giving users access to this would be very convienient. I do use the regular template feature quite a bit, but I don't see that the templates macros can add new directories of standard sets of oft-reused files or directories to projects, nor can they modify the include paths. Instead they seem limited to edits to within a given file.

Thanks

[rhopf1]

I've been using libraries under 2.1 but you still need to add the include paths and a path for the linker to find the libraries. The libraries have the advantage that if just a few library files need to be modified for a specific project those files can be copied to the project's directory and modified. The linker sorts out which function (library or local) to use. Linked folders won't do this.

I did try to update to 2.2 but was unable to use the library scheme as described above, in fact could not figure any way to use a library. Posted a question about it but no response so had to go back to 2.1.

... and to answer the original question haven't figured how to script or otherwise add the required paths.

Bob