Re: base directory for bluez

[Denis Ovsienko <denis () ovsienko info>]

 ---- On Thu, 25 Oct 2018 14:57:48 +0100 Martin Kaiser <lists () kaiser cx> wrote ---- 
> Dear all,
>
> I'm trying to cross-compile libpcap and enable bluetooth support for it.
> I've already cross-compiled bluez and installed it into a local
> directory hierarchy (not under the cross-compiler's sysroot).
>
> Unfortunately, the configure script uses an on/off switch for bluetooth
> and tries to detect bluez in the default system directories. Would it
> make sense to convert this to --with-bluetooth[=DIR]? 
>
> Or is there already a mechanism to say that the bluetooth includes are
> under $bluetooth_base/include and the libs are under
> $bluetooth-base/lib?

Hello Martin.

Existing arrangements for DAG and SNF provide additional options to specify the libs and headers paths in addition to 
the library path, if required:

  --with-dag[=DIR]        include Endace DAG support (located in directory
                          DIR, if supplied). [default=yes, if present]
  --with-dag-includes=IDIR
                          Endace DAG include directory, if not DIR/include
  --with-dag-libraries=LDIR
                          Endace DAG library directory, if not DIR/lib

  --with-snf[=DIR]        include Myricom SNF support (located in directory
                          DIR, if supplied). [default=yes, if present]
  --with-snf-includes=IDIR
                          Myricom SNF include directory, if not DIR/include
  --with-snf-libraries=LDIR
                          Myricom SNF library directory, if not DIR/lib

Do you think the same would work best for cross-compiling with bluetooth support?

On a related note, since libpcap now uses both configure and cmake, the change to the options should be made in a 
similar way in both build props.

-- 
    Denis Ovsienko


_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers