Mutliple Search Paths

[johne53]

Let's say that I have 3 x target projects within the same workspace (an executable and 2 x libs). Is there any way either to:-

a) Apply a global set of search paths (for libs & includes) to all 3 projects (without needing to enter the paths, 3 times) - or;

b) Quickly copy multiple paths from one project to another (without having to do them all, one-by-one).

[MortenMacFly]

a) Apply a global set of search paths (for libs & includes) to all 3 projects [...]
b) Quickly copy multiple paths from one project to another [...]

Sure, both is possible:
a) apply the directories on *project level* in the build options (not on target level)
b) you should see a "copy all to..." button in various build options -> use it. ;-)
I'm not sure what version you have - you might not see these options because you are using a rather old version of C::B. Please always include such information in your reports.
With regards, Morten.

[johne53]

I must have a fundamental misunderstanding of targets. The only types I'm familiar with are 'Debug' and 'Release'. A collection of files for building a target is what I'd normally call a 'Project'. Are you saying that (within one project) I can have one set of files that builds a lib and a different set of files that builds an executable? Up until now, I'd assumed that these would usually be implemented as different projects within the same workspace. AFAIK there's no way to "Copy all" between projects - only between targets in the same project but I might be wrong about that. I'm using a build dated 20th April 2007 (svn 3976 / wx2.6.1).

[MortenMacFly]

I must have a fundamental misunderstanding of targets.

Kind of... the C::B workspace/project/target architecture is very flexible. You can think of targets as release/debug but *also* as application/lib - just as you like. C::B offers the flexibility to use both concepts (even mixed). Have a look here: http://wiki.codeblocks.org/index.php?title=The_build_process_of_Code::Blocks which describes the build process and when which "elements" are used and how.
C::B itself is a good demonstration, too. the main C::B project file includes the C::B SDK (as lib), C::B itself (as application) and some of the core plugins (as plugins). Other project files (e.g. plugin project files) use the release/debug concept as targets.
So it's finally up to you how you'd like to setup your project(s). In your case it seems feasible to have one project with several targets (libs, exe).
With regards, Morten.