owserver is started unconditionally, but it needs the device(s) to
be specified at startup. Therefore a check for non-empty OWSERVER_ARGS
is added to the owserver start script.
owfs is started only if is built. It will connect to the owserver.
It will try to load the fuse module; if fuse is built-in or already
loaded, modprobe -q will fail silently. The filesystem will be mounted
on /dev/1wire, because it represents the 1-wire slave devices; also,
the bundled Debian init scripts mount it there. We have to create that
directory in the init script in case of devtmpfs, and we have to create
it in the rootfs for static /dev; for simplicity, just do both.
Users who want a setup without owserver need to remove the owserver
init script post-build and need to give appropriate defaults to owfs.
[Peter: fix mountpoint variable typo in S30owfs]
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Install package in staging directory, so that this package can be
linked together with other packages (for example collectd and its
onewire plugin).
Signed-off-by: Roland Franke <fli4l@franke-prem.de>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
owfs reinvents its own weird and wicked mechanism to find libfuse. It
believes that, by default, FUSE is installed in /usr/local, and forcibly
uses that path to look for headers and libs.
This is obviously wrong in cross-compilation, and triggers our check for
unsafe header/library paths.
The best option to fix that would be to use pkg-config to find FUSE, but
this is a bit involved. Instead, use config options to specify the path
to the headers and libs.
Fixes:
http://autobuild.buildroot.org/results/2c8/2c8baf6910d7ac2e3c92efa62cc3b9d3737e1fb5/http://autobuild.buildroot.org/results/1f9/1f994f53ceca434ebd1d87923f85b5ed71229d94/
and a few others...
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Arnout Vandecappelle <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
All modules are always enabled when their dependencies are satisfied.
tcl doesn't work because the tclConfig.sh installed by our tcl package
is wrong: it adds -I/usr/include.
perl doesn't work out of the box, I didn't investigate.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
