s3: VFS module built with specific paths to header and library (waf)

[Jeremy Allison]

On Wed, Jun 22, 2016 at 12:10:30AM +0200, Jiri Sasek - Solaris Prague wrote:
> Hi geeks,
> I apologize for my ignorance but I can not built a Samba VFS module using
> specific paths to header and library.
> In details... for instance I have:
>  - my build workspace in path: /builds/jsasek/samba
>  - ...where samba component is in: ./components/samba
>  - ...where (sparc) proto area is: ./build/proto/sparc
>  - ...where optional library is in: ./opt/SUNWsamfs/lib
>  - ...........headers are in: ./opt/SUNWsamfs/include
> 
> 
> ...so I need to pass:
>  -I/builds/jsasek/samba/components/samba/build/proto/sparc/opt/SUNWsamfs/include
> ...and:
> -L/builds/jsasek/samba/components/samba/build/proto/sparc/opt/SUNWsamfs/lib
> ...to waf build of the "samfs.c" module.
> 
> Exactly... the headers and (.so) lib do not have a fix path (do not exist)
> on the build machine but those are put only in the workspace only in
> build-time.

Symlinks ? Or could you do conf.CHECK_HEADERS('/builds/jsasek/samba/components/samba/build/proto/sparc/opt/SUNWsamfs/include/xxx.h') ?

> Many thanks in advance for your ideas,
> Jiri
>