You can use eclipse linked resources for that. The article I sent did not help?

Martin Politick wrote:
> Salut Mario,
> 
> Since you've been using QNX for many years you must have a similar setup.
> How are you managing a projects that are composed of many nested binaries,
> share interfaces (.h) and libraries?
> 
> What I'm trying to achieve is
> SVN Checkout of my development tree
> Then with any new module, create an "Eclipse project" and use ENV variables to include interfaces and libraries from 
the dev. tree into my new project.
> 
> Once the "project" is done, put it back into the SVN tree at the right nested location.
> 
> Merci à l'avance,
> Martin.
> 
> _______________________________________________
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post28714

> -----Original Message-----
> From: Martin Politick [mailto:community-noreply@qnx.com]
> Sent: May-05-09 12:10 PM
> To: momentics-community
> Subject: Re: RE: RE: How to handle Projects with multiple programs and
> libraries in Eclipse / Momentics.
> 
> Salut Mario,
> 

Salut Martin ;-)

> Since you've been using QNX for many years you must have a similar
> setup.

It is similar indeed.

> How are you managing a projects that are composed of many nested
> binaries, share interfaces (.h) and libraries?
> 
> What I'm trying to achieve is
> SVN Checkout of my development tree
> Then with any new module, create an "Eclipse project" and use ENV
> variables to include interfaces and libraries from the dev. tree into
> my new project.

That is what I've given up on trying to do.

What I ended up doing is creating a Makefile file project with my own makefile system.  The root of the project contains
 a makefile that will recursively go in each directories and build whatever is in there, respecting dependencies. 

- Project
  Makefile
  Common.mk
  - bin
  - lib
  - include
    - common
    - math
  - libraries
    - common
      Makefile
    - math
      Makefile
  - tools
    - converter
      - include
      - Makefile
    - ...
  - comm
    - ...
  - ...

Common.mk is included by every makefile, so common rules are put in there.  The lib directory is where all .a/.so will 
go when being build, that makes them easy to reference, no need to know where they were build from.  When a binary is 
build it is copied in the bin directory.  The directory include is where all the headers from the various library live.

The project has a root make target to build everything and targets (lib or executable) have a make target of their own. 
 That makes for a lot of make targets ( we have over 60 executable)  when considering each has a build/clean/copy/doc/
flint target.  Upcoming CDT has means of doing copy/paste of target, but current version distributed by QNX  doesn't so 
I ended up editing the .cproject file by hand to create all these make targets.

Most of the solution proposed by QNX (using links) wouldn't work for me as one of our requirement was the ability to 
work on multiple project/product at the same time, single checkout etc.  I haven't tried it cause I've spend so much 
time making this works that Eclipse is becoming counter-productive.  Before I try any sort of other mechanism I'll wait 
till Eclipse becomes mature enough to really handle big project.  I was expecting the QNX source available via SVN ( os,
 network, filesystem, etc) to show off how to handle big projects in Eclipse and learn from that. That has not 
materialize for obvious reasons ;-)

Using a makefile has it's drawback, but I manage.

> 
> Once the "project" is done, put it back into the SVN tree at the right nested location.
> 
> Merci à l'avance,

Hope that helps.

> Martin.
> 
> _______________________________________________
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post28714