On Wed, 2010-08-18 at 09:44 -0400, Sunil Keshava wrote:
> Hello,
> 
> I am curious to know what EXTRA_INCVPATH & EXTRA_LIBVPATH in common.mk of a project mean? What happens when a library's path is added to EXTRA_INCVPATH and what happens when the library's path is added to EXTRA_LIBVPATH?
> 
> I have seen number of projects where a particular library's path is added to EXTRA_INCVPATH & EXTRA_LIBVPATH. For example:
> 
> EXTRA_INCVPATH+=$(PROJECT_ROOT_mylibapi)
> 
> EXTRA_LIBVPATH+=$(PROJECT_ROOT_mylibapi)/$(CPU)/so
> 
> I am looking a comprehensive explanation for these. So any information would be appreciated.
> 
> Thanks
> Sunil

EXTRA_INCVPATH 
        Added to INCVPATH just before the $(USE_ROOT_INCLUDE). Default
        is none. 
        
EXTRA_LIBVPATH 
        Added to LIBVPATH just before
        $(INSTALL_ROOT_support)/$(OS)/$(CPUDIR)/lib. Default is none. 
        

You can read more about it here:
http://www.qnx.com/developers/docs/6.4.1/neutrino/prog/make_convent.html
        
---
Aleksandar

EXTRA_INCVPATH added to -I compiler option
EXTRA_LIBVPATH is added to -L linker option

see http://www.qnx.com/developers/docs/6.4.1/neutrino/prog/make_convent.html


On 18/08/10 09:44 AM, Sunil Keshava wrote:
> Hello,
> 
> I am curious to know what EXTRA_INCVPATH & EXTRA_LIBVPATH in common.mk of a project mean? What happens when a library's path is added to EXTRA_INCVPATH and what happens when the library's path is added to EXTRA_LIBVPATH?
> 
> I have seen number of projects where a particular library's path is added to EXTRA_INCVPATH & EXTRA_LIBVPATH. For example:
> 
> EXTRA_INCVPATH+=$(PROJECT_ROOT_mylibapi)
> 
> EXTRA_LIBVPATH+=$(PROJECT_ROOT_mylibapi)/$(CPU)/so
> 
> I am looking a comprehensive explanation for these. So any information would be appreciated.
> 
> Thanks
> Sunil
> 
> 
> 
> _______________________________________________
> 
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post63393
>