IDE prefers flat structure of the projects, and one artifact per project.
If you have makefiles to build all it is better for IDE to create 
another project and put
common makefiles there (which can go "up" then recourse down again to 
build all tree)
Some though about projects and IDE here
http://community.qnx.com/sf/wiki/do/viewPage/projects.ide/wiki/ProjectsBuildAndIDE

On 13-03-13 11:39 AM, Sayed.Shereef wrote:
>
> We have a large multi-process application that targets QNX 6.3.2 and 
> QNX 6.5.0 using a collection of custom makefiles. During the 
> development and deployment stages of this application, the "make" 
> procedure will call CVS to checkout user specified libraries from our 
> repository, which the application will link against. Our build machine 
> runs a VM of QNX 6.x which is used to generate our distribution packages.
>
> I would like to migrate away from this method, and integrate our 
> project with Momentics. I have looked into the "Makefile Project" 
> option, which is the route to take, but I'm not sure how to properly 
> leverage the IDE directly from a Makefile.
>
> Development Environment Specs.:
>
> -QNX Momentics IDE 4.7
>
> -Windows 7
>
> Here is the basic directory structure of our application:
>
> MeasurementApp/
>
>                 |
>
>                 Makefile à call CVS co lib/*; make --C app1/ ...
>
>                 |
>
>                 |---lib/*
>
>                 |
>
>                 |---app1/
>
>                 |              |
>
>                 |              Makefile à build app1
>
>                 |
>
>                 |---app2/
>
>                 |              |
>
>                 |              Makefile à build app2
>
>                 |
>
>                 ...
>
> Since I have never used Momentics in this capacity before, I'm asking 
> for any tips/suggestions/examples/tutorials that you may have that 
> will let me leverage the IDE from a custom Makefile(s).
>
> Thank you, in advance.
>
> -Shereef
>
>
> ------------------------------------------------------------------------
> The information contained in this email message is intended only for 
> the use of the individual(s) to whom it is addressed and may contain 
> information that is privileged and sensitive. If you are not the 
> intended recipient, or otherwise have received this communication in 
> error, please notify the sender immediately by email at the above 
> referenced address and note that any further dissemination, 
> distribution or copying of this communication is strictly prohibited.
>
> The U.S. Export Control Laws regulate the export and re-export of 
> technology originating in the United States. This includes the 
> electronic transmission of information and software to foreign 
> countries and to certain foreign nationals. Recipient agrees to abide 
> by these laws and their regulations -- including the U.S. Department 
> of Commerce Export Administration Regulations and the U.S. Department 
> of State International Traffic in Arms Regulations -- and not to 
> transfer, by electronic transmission or otherwise, any content derived 
> from this email to either a foreign national or a foreign destination 
> in violation of such laws.