I think you can avoid new plugins creation. Try to use MAKEFLAGS macro 
to define more libraries. You can also define environment variables or 
make command line parameters LIBS and EXTRA_LIBVPATH. Maybe the best way 
is to define all this stuff in fle that should be includd using 
MAKEFILES macro.     public IWizardPage getSpecificPage() {
         IWizardPage[] pages = MBSCustomPageManager.getPages();
         if((pages.length > 1) && (pages[1] instanceof MBSCustomPage) && 
MBSCustomPageManager.isPageVisible(((MBSCustomPage)pages[1]).getName()))
             return pages[1];
         return super.getSpecificPage();
     }
Two  more options: you can specify in preferences for QNX project by 
redefining of make command (make MKEFILES=... instead of using default) 
or as an environment varabkle. So there are tons of variants how to add 
your libraries automatically int any project user creates. Of course all 
this  work only if I unerstand our question correctly.


Andy Pekarske wrote:
> You're right, I plan on using the project wizard extension points.
>
> The QNX C++ projects I make all end up including similar files named in a different way and include different 
libraries that I have already developed.  I plan on modifying the common.mk file to automatically include those 
libraries.
>
>    
>> I don't understand the second part: what is "Generic Eclipse plugin"?
>> What does "Modify the common.mk file from a QNX project to my liking" means?
>> You can create you own project creation wizard using eclipse project
>> wizard extension points. Currently QNX API's are not documented.
>> What are trying to achieve with new wizard which current one does not do?
>>
>>      
>
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post10668
>
>